Re: Automatic upgrade of passwords from md5 to scram-sha256 - Mailing list pgsql-general

From Ron Johnson
Subject Re: Automatic upgrade of passwords from md5 to scram-sha256
Date
Msg-id CANzqJaDxwg_zS3LKZPq1Yj_sJV-T_qWT=mCF-ptEOcDHUJ+nzQ@mail.gmail.com
Whole thread Raw
In response to Re: Automatic upgrade of passwords from md5 to scram-sha256  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Sun, Jan 12, 2025 at 5:59 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
 [snip]
I think this idea is a nonstarter, TLS or not.  We're generally moving
in the direction of never letting the server see cleartext passwords.
It's already possible to configure libpq to refuse such requests
(see require_auth parameter), although that hasn't been made the
default.

ALTER ROLE xxx WITH PASSWORD accepts hashed values, so a client with the SCRAM-SHA algorithm could:
1. remember the password that was just used to log in,
2. generate the new hash, 
3. send that as an ALTER ROLE statement.

Anything which shows up in the logs would be no different than when someone types ALTER ROLE ... WITH PASSWORD from the psql prompt.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: Automatic upgrade of passwords from md5 to scram-sha256
Next
From: Adrian Klaver
Date:
Subject: Re: Intermittent errors when fetching cursor rows on PostgreSQL 16