Re: [PATCH] Move pgcrypto's fips_mode() function to core

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: "Koshi Shibagaki (Fujitsu)" <shibagaki(dot)koshi(at)fujitsu(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Move pgcrypto's fips_mode() function to core
Date: 2026-09-07 08:12:23
Message-ID: 69C0CFB5-8621-4F25-B120-4F88147E6732@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 7 Sep 2026, at 07:49, Koshi Shibagaki (Fujitsu) <shibagaki(dot)koshi(at)fujitsu(dot)com> wrote:

> Do you think it's a good idea to port the fips_mode() to core?

The reason for it being useful in pgcrypto is that pgcrypto always contains
built-in crypto which isn't FIPS certified. The builtin_crypto_enabled GUC and
fips_mode() were added to help users remain FIPS compliant.

When PostgreSQL is compiled with a TLS library (OpenSSL or LibreSSL) it doesn't
compile any built-in crypto at all, so all crypto operations will use OpenSSL
and thus be subject to FIPS compliance.

Due to this I'm not convinced there is a usecase for moving this to core. I
also don't want set a precedent of PostgreSQL exposing details about libraries
since there is an endless amount of similar functions which could be advocated
for.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-09-07 08:12:56 Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout
Previous Message Zhijie Hou (Fujitsu) 2026-09-07 08:10:52 RE: Follow-up review items for update_deleted