| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, "Koshi Shibagaki (Fujitsu)" <shibagaki(dot)koshi(at)fujitsu(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(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: | 2025-01-21 21:05:09 |
| Message-ID: | 7F08DCF4-3B4D-4599-A650-0DC8DA763F21@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 21 Jan 2025, at 21:59, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> (If we end up inventing a FIPS-mode flag, I would fully expect
> interested vendors to patch our code to force it on when the
> OS-level flag is set, which is exactly what they will have done
> to OpenSSL. We should design our behavior with that in mind.)
This patch is essentially a FIPS-mode flag as it's designed to block the
built-in non-certified code in pgcrypto which ensures that OpenSSL is used for
all crypto operations. When setting this GUC to "fips" it will match the
OpenSSL setting, disable built-in crypto when OpenSSL has FIPS enabled and
allow it when OpenSSL has FIPS disabled. Setting it to off will disable
built-in crypto regardless of FIPS mode in OpenSSL.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-01-21 21:06:14 | Re: Allow NOT VALID foreign key constraints on partitioned tables. |
| Previous Message | Tom Lane | 2025-01-21 20:59:19 | Re: Replace current implementations in crypt() and gen_salt() to OpenSSL |