Date: Tue, 1 Mar 2022 15:26:23 +0900
From: Michael Paquier <michael@paquier.xyz>
To: Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jeff Davis <pgsql@j-davis.com>,
	samay sharma <smilingsamay@gmail.com>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: Proposal: Support custom authentication methods using hooks
Message-ID: <Yh28j5PoG+mtAnSH@paquier.xyz>
References: <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>
 <9004b18218eae293f1ee888e49d13d8a6b02810d.camel@j-davis.com>
 <20220228204634.GM10577@tamriel.snowman.net>
 <2738622.1646083128@sss.pgh.pa.us>
 <20220228214255.GO10577@tamriel.snowman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="cWOXOFUHp1knkrMx"
Content-Disposition: inline
In-Reply-To: <20220228214255.GO10577@tamriel.snowman.net>
Archived-At: <https://www.postgresql.org/message-id/Yh28j5PoG%2BmtAnSH%40paquier.xyz>
Precedence: bulk


--cWOXOFUHp1knkrMx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Feb 28, 2022 at 04:42:55PM -0500, Stephen Frost wrote:
> Keeping it around will just push out the point at which everyone will
> finally be done with it, as there's really only two groups: those who
> have already moved to scram, and those who won't move until they want to
> upgrade to a release that doesn't have md5.

FWIW, I am not sure if we are at this point yet.  An extra reason to
remove it would be that it is a support burden, but I don't have seen
in recent memory any problems related to it that required any deep
changes in the way to use it, and its code paths are independent.

The last time I played with this area is the recent error handling
improvement with cryptohashes but MD5 has actually helped here in
detecting the problem as a patched OpenSSL would complain if trying to
use MD5 as hash function when FIPS is enabled.
--
Michael

--cWOXOFUHp1knkrMx
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmIdvI8ACgkQnvQgOdby
QH3L+xAAmnMGF6fgrqdqfRXr6lT2en+Pxjiu0Wi+nHotRqMNywlESXexloMS/4Hw
fhc9p5dd06Jh3lTp0aiJlH+r6/7egkU5WsUUbj1XzlNYg7wXYN7dxihqMDPyxUfW
xdW4GhOL4YTBqEIu4JxyV37MnDprazMDdOKiT60xBOd9QNDBcKX43chNRYokOjuL
xnkJGjlWBwZDFqYgrRpjQsDdEMIEgHNHtsCaBGZYc9pZh7aos+sJdVwbej/Ne0iT
coJkpobiXZyDvJtWroQJqn/LqZswME4maCimxLJnNlrRiw4672HJ37KyxjUjNNIT
Hk7KHcB23cgyhfBAd2+QE7GPEHjujtIzeaU/mZQcn69Q/YUIfyB6g2Ac2mZc5S+9
798Lp86iV+GfKEFEwUa8pWQkoEQGdYCvbj52mfUg0RdlMEhqwbBo77IT1KKMhJor
oGn06L3T9PCfTP//vAkEF4WT9Lamhg9H7AXyeYNeDoqZwQyiuEskr3X0vu+oqN9w
4fhxgaT+Klki+ZLalBrdat3SxNSd/Hzr0LW8To2/cfTisCm46FdqxYOqRbUuMhzz
gowqa+8dlPEUwCKaNL4RqHQsbquSmFZpb7ve4fstN8Lt3acbqmeWyZrx8Je/Yq0Z
rHIrRaFAkhlPZ8+GeBxcOS+m2D7+XBfrmwo9Lvb+KrPczN9Kr0c=
=o+ZE
-----END PGP SIGNATURE-----

--cWOXOFUHp1knkrMx--