Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XJmIc-00039D-8U for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Aug 2014 16:30:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XJmIb-0003CD-JQ for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Aug 2014 16:30:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XJmIa-0003Bc-4B for pgsql-hackers@postgreSQL.org; Tue, 19 Aug 2014 16:30:16 +0000 Received: from smtp-outbound-2.vmware.com ([208.91.2.13]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XJmIV-0005vK-UN for pgsql-hackers@postgreSQL.org; Tue, 19 Aug 2014 16:30:15 +0000 Received: from sc9-mailhost3.vmware.com (sc9-mailhost3.vmware.com [10.113.161.73]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 6F59929E86; Tue, 19 Aug 2014 09:30:08 -0700 (PDT) Received: from EX13-CAS-012.vmware.com (EX13-CAS-012.vmware.com [10.113.191.64]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id 63F62419F0; Tue, 19 Aug 2014 09:30:08 -0700 (PDT) Received: from EX13-MBX-024.vmware.com (10.113.191.44) by EX13-MBX-005.vmware.com (10.113.191.25) with Microsoft SMTP Server (TLS) id 15.0.775.38; Tue, 19 Aug 2014 09:29:55 -0700 Received: from [192.168.1.90] (10.113.160.246) by EX13-MBX-024.vmware.com (10.113.191.44) with Microsoft SMTP Server (TLS) id 15.0.775.38; Tue, 19 Aug 2014 09:29:54 -0700 Message-ID: <53F37B7E.30300@vmware.com> Date: Tue, 19 Aug 2014 19:29:50 +0300 From: Heikki Linnakangas Organization: VMware User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0 MIME-Version: 1.0 To: Stephen Frost , Andres Freund CC: PostgreSQL-development Subject: Re: PQgetssl() and alternative SSL implementations References: <53F1E989.8020609@vmware.com> <20140819144841.GA16422@tamriel.snowman.net> <20140819145547.GB30525@awork2.anarazel.de> <20140819150507.GB16422@tamriel.snowman.net> <20140819152613.GC30525@awork2.anarazel.de> <20140819155237.GE16422@tamriel.snowman.net> In-Reply-To: <20140819155237.GE16422@tamriel.snowman.net> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.113.160.246] X-ClientProxiedBy: EX13-CAS-013.vmware.com (10.113.191.65) To EX13-MBX-024.vmware.com (10.113.191.44) X-Pg-Spam-Score: -7.6 (-------) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 08/19/2014 06:52 PM, Stephen Frost wrote: > * Andres Freund (andres@2ndquadrant.com) wrote: >> No. We should build something that's suitable for postgres, not >> something general. We'll fail otherwise. For anything fancy the user has >> to look at the certificate themselves. We should make it easy to get at >> the whole certificate chain in a consistent manner. > > I don't buy this argument at all. > >>> Telling users they simply can't have this information isn't >>> acceptable. >> >> Meh. Why? Most of that isn't something a normal libpq user is going to >> need. > > I'm not interested in SSL support for users who don't use or care about > SSL (which would be 'normal libpq users', really). I've *long* been > frustrated by our poor support of SSL and at how painful it is to get > proper SSL working- and it's been a real problem getting PG to pass the > security compliance requirements because of that poor support. Let's > stop the rhetoric that PG doesn't need anything but the most basic > SSL/auditing/security capabilities. I think you just packed up the goalposts for a one-way trip to Mars, but I wonder: What would you consider "proper SSL support"? What exactly are we missing? - Heikki -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers