Message-ID: <9004b18218eae293f1ee888e49d13d8a6b02810d.camel@j-davis.com>
Subject: Re: Proposal: Support custom authentication methods using hooks
From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: samay sharma <smilingsamay@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: Sun, 27 Feb 2022 15:17:44 -0800
In-Reply-To: <1980351.1645816239@sss.pgh.pa.us>
References: 
	<CAJxrbyxTRn5P8J-p+wHLwFahK5y56PhK28VOb55jqMO05Y-DJw@mail.gmail.com>
	 <bfc55e8045453659df26cd60035bfbb4b9530052.camel@j-davis.com>
	 <1737574.1645753674@sss.pgh.pa.us>
	 <54dc198b56a87e31e9625405383f04a8c6589b8b.camel@j-davis.com>
	 <1905579.1645810764@sss.pgh.pa.us>
	 <2718414dc095b716e59e126c03af343997d14c7b.camel@j-davis.com>
	 <1980351.1645816239@sss.pgh.pa.us>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/9004b18218eae293f1ee888e49d13d8a6b02810d.camel%40j-davis.com>
Precedence: bulk

On Fri, 2022-02-25 at 14:10 -0500, Tom Lane wrote:
> I'm happy to add support for custom auth methods if they can use
> a protocol that's safer than cleartext-password.  But if that's the
> only feasible option, then we're just encouraging people to use
> insecure methods.

FWIW, I'd like to be able to use a token in the password field, and
then authenticate that token. So I didn't intend to send an actual
password in plaintext.

Maybe we should have a new "token" connection parameter so that libpq
can allow sending a token plaintext but refuse to send a password in
plaintext?

> 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?

Regards,
	Jeff Davis