Received: from clio.trends.ca (root@clio.trends.ca [209.47.148.2]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA58348; Fri, 14 Jan 2000 00:55:16 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by clio.trends.ca (8.9.3+Sun/8.9.3) with ESMTP id AAA07720; Fri, 14 Jan 2000 00:39:30 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id AAA28372; Fri, 14 Jan 2000 00:38:54 -0500 (EST) To: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org Subject: Does SSL code still work after async-connection changes? Date: Fri, 14 Jan 2000 00:38:54 -0500 Message-ID: <28369.947828334@sss.pgh.pa.us> From: Tom Lane Can anyone who uses SSL check whether libpq current sources still work for SSL connections? It looks to me like it's completely broken --- surely trying to negotiate SSL before doing connect() isn't going to work too well? But I don't know anything about SSL, nor have it installed, so I'm not eager to touch it... regards, tom lane