Re: Channel binding not supported using scram-sha-256 passwords - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: Channel binding not supported using scram-sha-256 passwords
Date
Msg-id 4b0c2616-967e-356e-fff8-99f4177ff08f@2ndquadrant.com
Whole thread Raw
In response to Re: Channel binding not supported using scram-sha-256 passwords  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Channel binding not supported using scram-sha-256 passwords  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 2019-02-22 06:28, Michael Paquier wrote:
>> Is that right?  Won't we then just select nothing if the macro is not
>> defined?
> In the context of an SSL connection, the server would send both SCRAM
> and SCRAM_PLUS as valid mechanisms if it supports channel binding
> (HAVE_BE_TLS_GET_CERTIFICATE_HASH).  If the server does not support
> channel binding, then only SCRAM is sent.

After reading it again a few more times, I think your patch is correct.

I tried reproducing the issue locally, but the required OpenSSL version
is too old to be easily available.

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


pgsql-general by date:

Previous
From: Stephen Frost
Date:
Subject: Re: LDAP authenticated session terminated by signal 11: Segmentationfault, PostgresSQL server terminates other active server processes
Next
From: Tom Lane
Date:
Subject: Re: LDAP authenticated session terminated by signal 11: Segmentation fault, PostgresSQL server terminates other active server processes