Re: Proposal: Support custom authentication methods using hooks

From: Joshua Brindle <joshua(dot)brindle(at)crunchydata(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, samay sharma <smilingsamay(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Proposal: Support custom authentication methods using hooks
Date: 2022-03-03 16:12:17
Message-ID: CAGB+Vh4UrjYOmEAF7VV+cXgBhA24C+MG1iDX-bRUbhf6T26CyA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 3, 2022 at 4:45 AM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2022-03-03 16:22:37 Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Previous Message Zhihong Yu 2022-03-03 15:57:27 Re: casting operand to proper type in BlockIdGetBlockNumber