Horton

Re: Add "password_protocol" connection parameter to libpq

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: "Jonathan S. Katz" <jkatz@postgresql.org>, Jeff Davis <pgsql@j-davis.com>, Stephen Frost <sfrost@snowman.net>, Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@postgresql.org
Date: 2019-08-11T19:56:50Z
Lists: pgsql-hackers 
On 2019-08-11 21:46, Jonathan S. Katz wrote:
> On 8/11/19 1:00 PM, Peter Eisentraut wrote:
>> On 2019-08-09 23:56, Jeff Davis wrote:
>>> 1. Hierarchical semantics, where you specify the least-secure
>>> acceptable method:
>>>
>>>   password_protocol = {any,md5,scram-sha-256,scram-sha-256-plus}
>>
>> What would the hierarchy be if scram-sha-512 and scram-sha-512-plus are
>> added?
> 
> password_protocol =
> {any,md5,scram-sha-256,scram-sha-512,scram-sha-256-plus,scram-sha-512-plus}?
> 
> I'd put one length of digest over another, but I'd still rank a method
> that uses channel binding has more protections than one that does not.

Sure, but the opposite opinion is also possible.

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

Commits

  1. Add libpq parameter 'channel_binding'.