Re: Proposal: Support custom authentication methods using hooks - Mailing list pgsql-hackers

From Joshua Brindle
Subject Re: Proposal: Support custom authentication methods using hooks
Date
Msg-id CAGB+Vh4UrjYOmEAF7VV+cXgBhA24C+MG1iDX-bRUbhf6T26CyA@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Support custom authentication methods using hooks  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Thu, Mar 3, 2022 at 4:45 AM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
>
> On 02.03.22 16:45, Jonathan S. Katz wrote:
> > By that argument, we should have kept "password" (plain) as an
> > authentication method.
>
> For comparison, the time between adding md5 and removing password was 16
> years.  It has been 5 years since scram was added.

It's been 7 years since this thread:
https://www.postgresql.org/message-id/54DBCBCF.9000600@vmware.com

As Jonathan and Stephen and others have said, anyone who wishes to
continue using MD5 or other plaintext methods can keep doing that for
5 more years with a supported version of PG. There is no excuse to
leave well known, flawed mechanisms in PG16.



pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: casting operand to proper type in BlockIdGetBlockNumber
Next
From: Dilip Kumar
Date:
Subject: Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints