Re: Can we stop defaulting to 'ident'? - Mailing list pgsql-pkg-yum

From Peter Eisentraut
Subject Re: Can we stop defaulting to 'ident'?
Date
Msg-id ca8580a5-ea7a-99f9-59f8-a99a83f463ef@2ndquadrant.com
Whole thread Raw
In response to Re: Can we stop defaulting to 'ident'?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Can we stop defaulting to 'ident'?  (Devrim Gündüz <devrim@gunduz.org>)
List pgsql-pkg-yum
On 2020-05-20 17:03, Peter Eisentraut wrote:
> On 2020-05-20 16:57, Stephen Frost wrote:
>> Greetings,
>>
>> * Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
>>> Sorry, I should have been more clear.  The upstream default of the GUC
>>> parameter "password_encryption" is md5.
>>
>> Which, really, is pretty broken when we're going to be having our
>> packagers setting up pg_hba.conf to use scram- at the *very* least it's
>> ridiculously misleading because we're going to have SCRAM in pg_hba.conf
>> but passwords actually stored as md5 and therefore we won't be getting
>> the benefits from SCRAM auth (though it should still work, of course,
>> since the SCRAM mode will fall back to working with an md5 password).
> 
> Devrim's commit to pgrpms did include a change to the default setting of
> password_encryption, so it appears to be correct as far as it goes.

I found that if you use initdb's -A option to set the default 
authentication method, then the passsword_encryption setting is 
automatically adjusted in postgresql.conf.  So this patch probably isn't 
even necessary.

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



pgsql-pkg-yum by date:

Previous
From: Christoph Berg
Date:
Subject: Re: Removing PL/Python2 from PostgreSQL 13
Next
From: Devrim Gündüz
Date:
Subject: Re: Can we stop defaulting to 'ident'?