Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e9AFSaJ29857 for ; Tue, 10 Oct 2000 11:28:36 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e9AFSYB19105; Tue, 10 Oct 2000 11:28:34 -0400 (EDT) To: Cedar Cox cc: pgsql-interfaces@postgresql.org Subject: Re: ODBC problem - crypt.. In-reply-to: References: Comments: In-reply-to Cedar Cox message dated "Tue, 10 Oct 2000 14:39:23 +0200" Date: Tue, 10 Oct 2000 11:28:34 -0400 Message-ID: <19102.971191714@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/72 X-Sequence-Number: 1429 Cedar Cox writes: > SSL link is established before any other data is sent (including > username/password), correct? Right. BTW, I believe the SSL support is actually broken in 7.0.* :-( (the lack of complaints doesn't say much for the number of people worried about comsec for PG). It's allegedly fixed in current sources but I haven't tried it. I'd suggest experimenting with a current snapshot. > Are there any special libraries required for > compiling PG with SSL support? Also, what about use of SSL inside/outside > the US? You need SSL which is a separate package. Beyond that I haven't a clue; you'll have to go look for info about SSL. > Now for the big question: Does the ODBC driver support SSL connections? [... grep ...] Apparently not. libpq (and therefore anything built atop libpq) does, but ODBC doesn't use libpq. ODBC needs some other updates too --- for instance, it still thinks there's a limit on query string length. Right now I don't think anyone is actively maintaining ODBC, but it badly needs someone to care for it. Any volunteers out there? regards, tom lane