From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SSL over Unix-domain sockets |
Date: | 2008-01-04 17:37:37 |
Message-ID: | 200801041737.m04Hbbk25708@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut wrote:
> Am Freitag, 4. Januar 2008 schrieb Bruce Momjian:
> > Peter Eisentraut wrote:
> > > Using the attached patch, SSL will act over Unix-domain sockets. AFAICT,
> > > this just works. I didn't find a way to sniff a Unix-domain socket,
> > > however.
> > >
> > > How should we proceed with this?
> >
> > I am confused by the shortness of this patch. Right now pg_hba.conf
> > has:
> >
> > # host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
> > # hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
> > # hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
> >
> > These are all for TCP connections. How do we handle 'local' SSL
> > connection specification? Do we want to provide similar functionality
> > for local connections?
>
> Yes, we might want to add that as well. That and some documentation updates
> would probably cover everything.
OK. Right now the documentation about spoofing says to use directory
permissions for the socket, and that works. I am thinking this is
something for 8.4.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-01-04 17:47:15 | Re: SSL over Unix-domain sockets |
Previous Message | Peter Eisentraut | 2008-01-04 17:35:02 | Re: SSL over Unix-domain sockets |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-01-04 17:47:15 | Re: SSL over Unix-domain sockets |
Previous Message | Peter Eisentraut | 2008-01-04 17:35:02 | Re: SSL over Unix-domain sockets |