Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id B39A09FB432 for ; Fri, 23 Mar 2007 15:16:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 88214-02 for ; Fri, 23 Mar 2007 15:16:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by postgresql.org (Postfix) with ESMTP id 89F8A9FB3E6 for ; Fri, 23 Mar 2007 15:16:27 -0300 (ADT) Received: by locust.cns.vt.edu (Postfix, from userid 986) id 18E17118A1F; Fri, 23 Mar 2007 14:16:26 -0400 (EDT) Date: Fri, 23 Mar 2007 14:16:26 -0400 From: Ray Stell To: pgsql-admin@postgresql.org Subject: no verification of client certificate? Message-ID: <20070323181626.GA16092@cns.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/173 X-Sequence-Number: 24997 8.2.3 I was hoping to not have to support client certs. I want encryption and to verify the server, but no to verify the client. Does this work and I've got the config wrong? I get ssl connections if I add in the .postgresql/postgresql.crt+key. Results seem similar to this report: http://archives.postgresql.org/pgsql-general/2006-11/msg01148.php