From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Stephen Frost <sfrost@snowman.net>
To: Andres Freund <andres@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: PQgetssl() and alternative SSL implementations
Date: Tue, 19 Aug 2014 19:29:50 +0300
Message-ID: <53F37B7E.30300@vmware.com> (raw)
In-Reply-To: <20140819155237.GE16422@tamriel.snowman.net>
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: hlinnakangas@vmware.com, sfrost@snowman.net, andres@2ndquadrant.com
Subject: Re: PQgetssl() and alternative SSL implementations
In-Reply-To: <53F37B7E.30300@vmware.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox