Sender: lockhart@hub.org
Message-ID: <37FC9E31.38BD6C2D@alumni.caltech.edu>
Date: Thu, 07 Oct 1999 13:20:49 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
MIME-Version: 1.0
To: "Ansley, Michael" <Michael.Ansley@intec.co.za>
CC: "J. Carlos Muro" <SADACIA@santandersupernet.com>,
	PostgreSQL Interfaces Mailing List <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Questions connecting to PostgreSQL.
References: <1BF7C7482189D211B03F00805F8527F748C127@S-NATH-EXCH2>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> At the moment, although ssl is being built into libpq, which would enable
> it's use for libpq++, ODBC does not use the libpq source, which is a bit of
> a bummer.  However, I suspect that it wouldn't be too difficult to include
> it.  If you're capable of writing a sockets server, you shouldn't find it
> too difficult ;-)

Someone posted a note on how to fire up an SSL path from a client to a
server, which can then be used by the client to contact the
postmaster. In my 2 second test, it worked just fine. I didn't check
to see if subsequent connections (i.e. after the handoff to the
session backend) used SSL too. Does it, or can it? Or is this
technique only helpful to hide the initial passwords and handshaking??

                     - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California