| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vik Fearing <vik(at)postgresfriends(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: password_encryption default |
| Date: | 2020-05-27 06:29:25 |
| Message-ID: | 94b2c23e-71ff-641a-0873-5833e18d3e03@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-05-27 08:00, Michael Paquier wrote:
> On Tue, May 26, 2020 at 10:25:25AM +0200, Peter Eisentraut wrote:
>> Yeah, I was too enthusiastic about removing that. Here is a better patch.
>
> + as an MD5 hash. (<literal>on</literal> is also accepted, as an alias
> + for <literal>md5</literal>.) The default is
> + <literal>scram-sha-256</literal>.
> Shouldn't password_encryption = on/true/1/yes be an equivalent of
> scram-sha-256 as the default gets changed?
I think these are mostly legacy options anyway, so if we wanted to make
a change, we should remove them.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-05-27 06:48:37 | Re: max_slot_wal_keep_size comment in postgresql.conf |
| Previous Message | Michael Paquier | 2020-05-27 06:11:00 | Re: max_slot_wal_keep_size comment in postgresql.conf |