Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256 - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256
Date
Msg-id CAB7nPqQbxmAB1_1twHHnEYfvdCvFetb=A+MSJvpjrCL-56jycA@mail.gmail.com
Whole thread Raw
In response to Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Tue, Oct 10, 2017 at 10:12 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Attached is a new patch set with the comments from above. On top of
> that, I have changed a couple of things:
> - 0001 is unchanged, still the same refactoring for the SSL tests.
> - 0002 implements tls-unique, now including tests using the default
> channel binding tls-unique with something in the SSL test suite. This
> patch also now introduces all the infrastructure to plug in correctly
> new libpq parameters and more channel binding types.
> - 0003 is shorter, and introduces a set of libpq parameters useful for
> tests, taking advantage of 0002. Another case where the connection
> parameter saslname is useful is to enforce not using channel binding
> when connecting to a v10 server using a SSL context with a v11 libpq.
> - 0004 introduces tls-server-end-point.
> This has required some work to get it shaped as wanted, I am adding it
> to the next CF, as version 2.

Documentation in protocol.sgml has rotten again as markups need proper
handling. So rebased.
-- 
Michael

Attachment

pgsql-hackers by date:

Previous
From: Pavel Golub
Date:
Subject: Re: Migration to PGLister - After
Next
From: "Moon Insung"
Date:
Subject: [PATCH]pg_buffercache add a buffer state column, Add fuction to decode buffer state