Re: Replace current implementations in crypt() and gen_salt() to OpenSSL - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Replace current implementations in crypt() and gen_salt() to OpenSSL
Date
Msg-id CA+TgmoYYctDtmgbfW7XW9yA2PZd67SafF3UawJh6O8=V4WUyVA@mail.gmail.com
Whole thread Raw
In response to Re: Replace current implementations in crypt() and gen_salt() to OpenSSL  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
On Tue, Nov 19, 2024 at 12:30 PM Joe Conway <mail@joeconway.com> wrote:
> Any other opinions out there?

Why should we accept your patch (which adds a legacy_crypto_enabled
GUC) instead of adopting the approach originally proposed (i.e. use
the OpenSSL version of the functions)? It seems to me that the two
proposals accomplish the same thing, except that one of them also adds
a GUC.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: sunsetting md5 password support
Next
From: Mark Dilger
Date:
Subject: Re: Index AM API cleanup