Re: password_encryption default

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, "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>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: password_encryption default
Date: 2020-05-27 12:56:34
Message-ID: CABUevEzWvXq76oA=cA5huLHTs2s5xNJE-+YOq0ZCBtmcJ_unxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 27, 2020 at 8:29 AM Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:

> 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.
>

Seems like the better choice yeah. Since we're changing the default anyway,
maybe now is the time to do that? Or if not, maybe have it log an explicit
deprecation warning when it loads a config with it?

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-05-27 13:13:35 Re: password_encryption default
Previous Message Ashutosh Bapat 2020-05-27 12:11:16 Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table.