From: Bruno Wolff III <bruno@wolff.to>
To: LSanchez@ameritrade.com
Cc: mike@thegodshalls.com
Cc: xzilla@users.sourceforge.net
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_hba.conf
Date: Wed, 26 May 2004 10:29:36 -0500
Message-ID: <20040526152936.GA2253@wolff.to> (raw)
In-Reply-To: <2898C2526ECBEB448D434BA1F302790902E93D06@scsdcmail1.ameritrade.com>
References: <2898C2526ECBEB448D434BA1F302790902E93D06@scsdcmail1.ameritrade.com>
On Wed, May 26, 2004 at 10:27:41 -0400,
LSanchez@ameritrade.com wrote:
> Thanks Mike!
>
> Do you know if pgSQL will be supporting higher level of encryption in
> the near future? Most of us here at Ameritrade work from home via VPN.
The client can use ssl. That supports 128 bit keys which is plenty.
Any adversary that has the resources to brute force a 128bit key has
the resources to do black bag jobs for a lower cost. If there are other
weaknesses besides brute force attacks, increasing the key size alone
isn't going to magicly make things better.
What kinds of threats are you trying to protect against? If you are using
an encrypted link already, using ssl isn't going to add much security.
Just allowing people to connect to the database directly is a significant
risk. It is made worse by letting people do it home where the machines
may not be safely operated by the users, which are not physically secured
and for which maitainance is harder (or not being done by the company).
If you are worried about people stealing hardware with information on it,
you should be considering better physical security, proper procedures
for destroying old media and consider using encrypted file systems.
If you are looking for ideas for how to hide information from authroized
users of a database while letting them use it for some things, Peter Wayner's
book Translucent Databases might be of some interest.
> -----Original Message-----
> From: mike g [mailto:mike@thegodshalls.com]
> Sent: Wednesday, May 26, 2004 12:51 AM
> To: LSanchez@ameritrade.com
> Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_hba.conf
>
> Hello,
>
> 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?
>
> Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bruno@wolff.to, LSanchez@ameritrade.com, mike@thegodshalls.com, xzilla@users.sourceforge.net
Subject: Re: pg_hba.conf
In-Reply-To: <20040526152936.GA2253@wolff.to>
References: <2898C2526ECBEB448D434BA1F302790902E93D06@scsdcmail1.ameritrade.com> <20040526152936.GA2253@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox