| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Koshi Shibagaki (Fujitsu)" <shibagaki(dot)koshi(at)fujitsu(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Replace current implementations in crypt() and gen_salt() to OpenSSL |
| Date: | 2024-10-29 09:57:28 |
| Message-ID: | 8CA10735-00C2-4F11-95FC-5F081CD7AF99@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 26 Oct 2024, at 20:10, Joe Conway <mail(at)joeconway(dot)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.
I'm not very enthusiastic about adding a GUC to match a system property like
that for the same reason why we avoid GUCs with transitive dependencies.
Re-reading the thread and thinking about I think the best solution would be to
split these functions off into their own extension.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Кириллов Вячеслав | 2024-10-29 10:21:49 | Re: Question about VACUUM behavior with sub-transactions in stored procedures |
| Previous Message | vignesh C | 2024-10-29 09:48:16 | Re: Pgoutput not capturing the generated columns |