public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joe Conway <[email protected]>
To: Tom Lane <[email protected]>
To: Daniel Gustafsson <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: BUG #19457: RE: pgp_sym_encrypt silently accepts non-FIPS ciphers (bf, cast5, 3des) when OpenSSL is in FIPS mod
Date: Fri, 24 Apr 2026 11:18:28 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 4/24/26 10:38, Tom Lane wrote:
> Daniel Gustafsson <[email protected]> writes:
>>> On 24 Apr 2026, at 06:20, Michael Paquier <[email protected]> wrote:
>>> I am interesting in getting that fixed for the next point release, so
>>> I have given it a try, finishing with the attached.  This would cause
>>> pgp_sym_encrypt() and pgp_sym_decrypt() to complain when the builtin
>>> mode is disabled, making things more consistent with the surroundings.
> 
>> I'm not convinced this is material for a minor release, the feature works as
>> documented and it was never documented to cover PGP.  Re-reading the thread PGP
>> was never discussed, and while that admittedly seem like an oversight doing
>> this in a minor release will alter documented behaviour which is generally not
>> what we want to do.
> 
> I sympathize with that argument, but ... people who are running in
> FIPS mode are probably doing so because they have contractual or legal
> obligations to meet that standard.  A person who could be in hot water
> if they are accidentally running disallowed crypto would see this as a
> dangerous bug.  A person who does not care should not be using FIPS
> mode.


+1 I think we should consider this as a backpatchable bug.

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: BUG #19457: RE: pgp_sym_encrypt silently accepts non-FIPS ciphers (bf, cast5, 3des) when OpenSSL is in FIPS mod
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox