From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256 |
Date: | 2017-11-28 22:08:44 |
Message-ID: | CAB7nPqQ6twidjk7PPwkgucE6eFfHfc3EAkeWyxANWFyUAj_AeQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Wed, Nov 29, 2017 at 2:41 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Nov 28, 2017 at 11:10 AM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> I also wonder whether there should be a mechanism to turn off channel
>> binding from the client. Right now, there is no way to test the
>> non-PLUS mechanism in an SSL build.
>
> I think that would be a good thing to have.
Sure. How do we shape that though? I would think about an extra option
for a scram-sha-256 entry with channel-binding=on|off|choice, choice
being what is currently on HEAD with letting the client decide to use
it or not.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-11-28 22:17:48 | Re: Skip index cleanup if autovacuum did not do any work |
Previous Message | Peter Geoghegan | 2017-11-28 22:00:39 | Re: Skip index cleanup if autovacuum did not do any work |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-11-28 22:33:10 | Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256 |
Previous Message | Robert Haas | 2017-11-28 17:41:34 | Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256 |