Postgres Pro
Downloads
Home   >   mailing lists

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

From Jacob Champion
Subject Re: Replace current implementations in crypt() and gen_salt() to OpenSSL
Date
Msg-id CAOYmi+kMVER=0vupiy9+Rj=d6xkQMaUQOkzApticU7duk1YR6A@mail.gmail.com
Whole thread Raw
In response to Replace current implementations in crypt() and gen_salt() to OpenSSL  ("Koshi Shibagaki (Fujitsu)" <shibagaki.koshi@fujitsu.com>)
Responses Re: Replace current implementations in crypt() and gen_salt() to OpenSSL
List pgsql-hackers
Tree view 
On Sat, Oct 26, 2024 at 11:10 AM Joe Conway <mail@joeconway.com> wrote:
> Rather than depend on figuring out if we are in FIPS_mode in a portable
> way, I think the GUC is simpler and sufficient. Why not do that and just
> use a better name, e.g. legacy_crypto_enabled or something similar
> (bike-shedding welcomed) as in the attached.

While it's definitely simpler, I read the original request as "forbid
non-FIPS crypto if the system tells us to", and I don't think this
proposal does that.

--Jacob

pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: RFC: Extension Packaging & Lookup
Next
From: "David E. Wheeler"
Date:
Subject: Re: RFC: Extension Packaging & Lookup