Re: Handling better supported channel binding types for SSL implementations

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Handling better supported channel binding types for SSL implementations
Date: 2018-03-08 19:19:55
Message-ID: 055904f6-3e61-be44-5179-7986941ed2e3@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/23/18 21:27, Michael Paquier wrote:
> On Tue, Jan 23, 2018 at 12:08:37PM -0500, Peter Eisentraut wrote:
>> On 1/22/18 02:29, Michael Paquier wrote:
>>> However there is as well the argument that this list's contents are not
>>> directly used now, and based on what I saw from the MacOS SSL and GnuTLS
>>> patches that would not be the case after either.
>>
>> Right, there is no facility for negotiating the channel binding type, so
>> a boolean result should be enough.
>
> I am not completely convinced either that we need to complicate the code
> to handle channel binding type negotiation.
>
>> In which case we wouldn't actually need this for GnuTLS yet.
>
> Sure. This depends mainly on how the patch for Mac's Secure Transport
> moves forward.

Moved to next CF along with those other two patches.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2018-03-08 19:23:07 Re: disable SSL compression?
Previous Message Andres Freund 2018-03-08 19:19:12 Re: [HACKERS] Restrict concurrent update/delete with UPDATE of partition key