On 01/08/2018 11:01 AM, Tom Lane wrote:
> Simon Riggs writes:
>> On 4 January 2018 at 21:02, Tom Lane wrote:
>>> Peter Eisentraut writes:
Implement channel binding tls-server-end-point for SCRAM
>>> Buildfarm doesn't like this one bit.
>> Can't we automate these messages?
> It's not that
Simon Riggs writes:
> On 4 January 2018 at 21:02, Tom Lane wrote:
>> Peter Eisentraut writes:
>>> Implement channel binding tls-server-end-point for SCRAM
>> Buildfarm doesn't like this one bit.
> Can't we automate these messages?
It's not that easy. First, the buildfarm gets random failures
On 4 January 2018 at 21:02, Tom Lane wrote:
> Peter Eisentraut writes:
>> Implement channel binding tls-server-end-point for SCRAM
>
> Buildfarm doesn't like this one bit.
Can't we automate these messages? Seems strange to send manual emails
every time. We do know who the commits are coming from
On Fri, Jan 5, 2018 at 9:36 AM, Peter Eisentraut wrote:
> Implement channel binding tls-server-end-point for SCRAM
FYI some BF animals are saying:
libpq/be-secure-openssl.o: In function `be_tls_get_certificate_hash':
/home/pgbuildfarm/buildroot-termite/HEAD/pgsql.build/../pgsql/src/backend/libpq
Peter Eisentraut writes:
> Implement channel binding tls-server-end-point for SCRAM
Buildfarm doesn't like this one bit.
regards, tom lane
Implement channel binding tls-server-end-point for SCRAM
This adds a second standard channel binding type for SCRAM. It is
mainly intended for third-party clients that cannot implement
tls-unique, for example JDBC.
Author: Michael Paquier
Branch
--
master
Details
---
https://git.postg
