public inbox for [email protected]
help / color / mirror / Atom feedFrom: Stephen Frost <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Christoph Berg <[email protected]>
Cc: Devrim Gündüz <[email protected]>
Cc: Craig Ringer <[email protected]>
Cc: pgsql-pkg-yum <[email protected]>
Subject: Re: Can we stop defaulting to 'md5'?
Date: Thu, 28 May 2020 16:08:10 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
Greetings,
* Peter Eisentraut ([email protected]) wrote:
> On 2020-05-28 18:38, Christoph Berg wrote:
> >Why do I have to decide*in pg_hba.conf* which hash algorithm is used?
> >Why can't that just be "password"?
> >
> >The password_encryption GUC should be the only place concerned with
> >that, and it should only be used for new passwords. Existing passwords
> >should just continue to work.*That* would allow seamless upgrades.
>
> You get that if you set the authentication method to "md5". (Clearly not a
> very clear name, but it exists.)
Yeah, the way that was done really wasn't terribly good.
Having 'password' or such, as Chritoph suggest, and then options for
"require=scram" / "require=scram,md5" / nothing (to allow whatever..)
would likely have been better, but that's not what we've got today so
there isn't much point in debating it here.
Thanks,
Stephen
Attachments:
[application/pgp-signature] signature.asc (819B, 2-signature.asc)
download
view thread (54+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Can we stop defaulting to 'md5'?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox