From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: sunsetting md5 password support |
Date: | 2024-10-11 21:36:27 |
Message-ID: | ZwmaW2AeUjBJGHgw@nathan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 11, 2024 at 09:47:58AM -0400, Andrew Dunstan wrote:
> On 2024-10-10 Th 6:28 PM, Tom Lane wrote:
>> On the whole I agree with Heikki's comment that we should just
>> do it (disallow MD5, full stop) whenever we feel that enough
>> time has passed. These intermediate states are mostly going to
>> add headaches. Maybe we could do something with an intermediate
>> release that just emits warnings, without any feature changes.
>
> I also agree with this.
Here is a first attempt at a patch for marking MD5 passwords as deprecated.
It's quite bare-bones at the moment, so I anticipate future revisions will
add more content. Besides sprinkling several deprecation notices
throughout the documentation, this patch teaches CREATE ROLE and ALTER ROLE
to emit warnings when setting MD5 passwords. A new GUC named
md5_password_warnings can be set to "off" to disable these warnings. I
considered adding even more warnings (e.g., when authenticating), but I
felt that would be far too noisy.
--
nathan
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Deprecate-MD5-passwords.patch | text/plain | 17.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2024-10-11 23:10:34 | Re: Statistics Import and Export |
Previous Message | Daniel Gustafsson | 2024-10-11 21:20:43 | Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions |