On Tue, Oct 10, 2017 at 10:12 PM, Michael Paquier <michael.paqu...@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
0001-Refactor-routine-to-test-connection-to-SSL-server.patch
Description: Binary data
0002-Support-channel-binding-tls-unique-in-SCRAM.patch
Description: Binary data
0003-Add-connection-parameters-saslname-and-saslchannelbi.patch
Description: Binary data
0004-Implement-channel-binding-tls-server-end-point-for-S.patch
Description: Binary data
