| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| 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-11-21 19:11:24 |
| Message-ID: | 4f0b39e5-4ccb-4771-9f68-839d7d7e6014@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/20/24 12:14, Daniel Gustafsson wrote:
>> On 19 Nov 2024, at 18:30, Joe Conway <mail(at)joeconway(dot)com> wrote:
>
>> Any other opinions out there?
>
> Couldn't installations who would be satisfied with a GUC gate revoke privileges
> from the relevant functions already today and achieve almost the same result?
I think that would qualify as a "mitigation" but not "FIPS compliant".
When the OS is made FIPS compliant, for example, you run something on
the command line and then you need to reboot (RHEL at least). I believe
that is considered configuration for FIPS.
A postmaster GUC (requiring restart) would be a way to configure
Postgres to eliminate these two non-FIPS functions that could not be
undone without another restart (similar to the OS example above).
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Luzanov | 2024-11-21 19:50:41 | psql: Fix \pset by adding missed xheader_width option to the help |
| Previous Message | Joe Conway | 2024-11-21 19:06:11 | Re: Replace current implementations in crypt() and gen_salt() to OpenSSL |