From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc> |
Subject: | Re: [HACKERS] SSL over Unix-domain sockets |
Date: | 2008-01-18 10:59:49 |
Message-ID: | 20080118105949.GF7353@svr2.hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Fri, Jan 18, 2008 at 11:24:09AM +0100, Peter Eisentraut wrote:
> Am Donnerstag, 17. Januar 2008 schrieb Andrew Dunstan:
> > I agree. I remain of the opinion that this is not a problem than can be
> > solved purely within the bounds of postgres.
>
> Well, the SSL patch I showed certainly solves the problem. (I am not saying
> it is the best possible solution.) Of course there also need to be prudent
> users, but that is the case for any security system.
Not that much more than moving the socket file to a secure directory. Both
rely on configuring the client properly. It's arguably a lot easier to
configure the client to connect to the correct socket, than to make sure
the client has a root certificate installed.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-01-18 11:35:40 | Re: [HACKERS] SSL over Unix-domain sockets |
Previous Message | Peter Eisentraut | 2008-01-18 10:38:23 | Re: [HACKERS] SSL over Unix-domain sockets |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-01-18 11:35:40 | Re: [HACKERS] SSL over Unix-domain sockets |
Previous Message | Peter Eisentraut | 2008-01-18 10:38:23 | Re: [HACKERS] SSL over Unix-domain sockets |