Subject: Re: Can we stop defaulting to 'ident'?
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Stephen Frost <sfrost@snowman.net>
References: 
 <CAMsr+YFCuBGWh4=aM-K2LCsBEwcrqm=pphKKHEH09vHwXcspow@mail.gmail.com>
 <7761d006b5ace13a4d86ce489123e5004aaf8b6c.camel@gunduz.org>
 <20200519212710.GQ13712@tamriel.snowman.net>
 <6089d4c8e262dd6fe8a6510c283e674543a24b5c.camel@gunduz.org>
 <3869d8c9-c212-8d73-52f4-13b03abe4813@2ndquadrant.com>
 <20200520134035.GD296739@msg.df7cb.de>
 <3a7d55ed-6abb-2005-23d7-8411bb9f5651@2ndquadrant.com>
 <20200520145752.GD3418@tamriel.snowman.net>
 <32b7fe66-f0e6-42e5-3c95-7d123e7d7f6d@2ndquadrant.com>
Cc: Christoph Berg <myon@debian.org>, =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?=
 <devrim@gunduz.org>, Craig Ringer <craig@2ndquadrant.com>,
 pgsql-pkg-yum <pgsql-pkg-yum@postgresql.org>
Organization: 2ndQuadrant
Message-ID: <ca8580a5-ea7a-99f9-59f8-a99a83f463ef@2ndquadrant.com>
Date: Fri, 22 May 2020 10:52:16 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <32b7fe66-f0e6-42e5-3c95-7d123e7d7f6d@2ndquadrant.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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