From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: markwkm@gmail.com
Subject: Re: Allow tests to pass in OpenSSL FIPS mode
Date: Sun, 14 Sep 2025 15:02:15 -0400
Message-ID: <443709.1757876535@sss.pgh.pa.us> (raw)
In-Reply-To: <2540752.1700003258@sss.pgh.pa.us>
References: <dbbd927f-ef1f-c9a1-4ec6-c759778ac852@enterprisedb.com>
<c8f11f3c-c267-1f62-f90c-619b8fae9013@enterprisedb.com>
<2818708.1696536244@sss.pgh.pa.us>
<2825088.1696539339@sss.pgh.pa.us>
<ee465e37-62e9-4577-999c-42a65753bef0@eisentraut.org>
<2540752.1700003258@sss.pgh.pa.us>
[ blast-from-the-past department ]
I wrote:
> Peter Eisentraut <peter@eisentraut.org> writes:
>> I suggest that if there are no other concerns, we proceed with the patch
>> set as is for now.
> After thinking about it for awhile, I guess I'm okay with only
> bothering to provide expected-files for FIPS failures under OpenSSL
> 3.x (which is how your patch is set up, I believe). While there are
> certainly still LTS platforms with 1.x, we don't have to consider FIPS
> mode on them to be a supported case.
I see that Mark W. has just spun up a couple of BF animals running
FIPS mode under SLES 15 (goshawk and shoebill). Not too surprisingly,
they are failing the MD5 test:
select md5('') = 'd41d8cd98f00b204e9800998ecf8427e' AS "TRUE";
-ERROR: could not compute MD5 hash: unsupported
+ERROR: could not compute MD5 hash: disabled for FIPS
select md5('a') = '0cc175b9c0f1b6a831c399e269772661' AS "TRUE";
-ERROR: could not compute MD5 hash: unsupported
+ERROR: could not compute MD5 hash: disabled for FIPS
(etc etc)
Should we revisit the decision to not support this spelling
of the error message? SLES 15 has got another decade or so
of support according to wikipedia [1], so it's hard to call it
a dead platform.
It looks like it'd be easy enough to generate the required
alternate expected-file, just s/unsupported/disabled for FIPS/g.
Happy to take care of this if there are not objections.
regards, tom lane
[1] https://en.wikipedia.org/wiki/SUSE_Linux_Enterprise#End-of-support_schedule
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter@eisentraut.org, markwkm@gmail.com
Subject: Re: Allow tests to pass in OpenSSL FIPS mode
In-Reply-To: <443709.1757876535@sss.pgh.pa.us>
References: <dbbd927f-ef1f-c9a1-4ec6-c759778ac852@enterprisedb.com> <c8f11f3c-c267-1f62-f90c-619b8fae9013@enterprisedb.com> <2818708.1696536244@sss.pgh.pa.us> <2825088.1696539339@sss.pgh.pa.us> <ee465e37-62e9-4577-999c-42a65753bef0@eisentraut.org> <2540752.1700003258@sss.pgh.pa.us> <443709.1757876535@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox