| From: | Chris Browne <cbbrowne(at)acm(dot)org> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_hba.conf |
| Date: | 2004-05-26 19:02:52 |
| Message-ID: | 604qq3c8pv.fsf@dev6.int.libertyrms.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
mike(at)thegodshalls(dot)com (mike g) writes:
> I believe I found my problem. The Cisco VPN client I use encrypts data
> at a 168 bit level. Postgres only supports up to 128 bit correct?
That ought to be entirely irrelevant, as your VPN client would encrypt
all data going across the network, encrypted or not. Indeed, if the
VPN is encrypting the data, it is redundant to have the database
server encrypt it an extra time.
That will just make things perform poorly.
And if you have some network configuration problem, adding in extra
layers of encryption is unlikely to make it easier to solve the
problem...
--
(reverse (concatenate 'string "gro.mca" "@" "enworbbc"))
http://cbbrowne.com/info/linux.html
Howe's Law:
Everyone has a scheme that will not work.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mike g | 2004-05-27 03:16:15 | Re: pg_hba.conf |
| Previous Message | Bruno Wolff III | 2004-05-26 15:51:48 | Re: table check |