Re: Proposal: Support custom authentication methods using hooks

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-02-28 10:22:02
Message-ID: cf5d067e-bda4-d9cf-068e-62eb07f12b35@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 28.02.22 00:17, Jeff Davis wrote:
>> I also have in mind here that there has been discussion of giving
>> libpq a feature to refuse, on the client side, to send cleartext
>> passwords.
> I am generally in favor of that idea, but I'm not sure that will
> completely resolve the issue. For instance, should it also refuse MD5?

Presumably that feature could be more generally "refuse these
authentication mechanisms" rather than only one hardcoded one.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-02-28 10:26:06 Re: Proposal: Support custom authentication methods using hooks
Previous Message Peter Eisentraut 2022-02-28 10:13:23 Re: Support for grabbing multiple consecutive values with nextval()