Re: Allow tests to pass in OpenSSL FIPS mode - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Allow tests to pass in OpenSSL FIPS mode
Date
Msg-id 3c36b798-fbb2-9246-fafd-4e4b2f546de8@enterprisedb.com
Whole thread Raw
In response to Re: Allow tests to pass in OpenSSL FIPS mode  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Allow tests to pass in OpenSSL FIPS mode  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: Allow tests to pass in OpenSSL FIPS mode  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On 12.10.22 03:18, Michael Paquier wrote:
> On Tue, Oct 11, 2022 at 01:51:50PM +0200, Peter Eisentraut wrote:
>> Let's make a small start on this.  The attached patch moves the tests of the
>> md5() function to a separate test file.  That would ultimately make it
>> easier to maintain a variant expected file for FIPS mode where that function
>> will fail (similar to how we have done it for the pgcrypto tests).
> 
> Makes sense to me.  This slice looks fine.

Committed.

> I think that the other md5() computations done in the main regression
> test suite could just be switched to use one of the sha*() functions
> as they just want to put their hands on text values.  It looks like a
> few of them have some expections with the output size and
> generate_series(), though, but this could be tweaked by making the
> series shorter, for example.

Right, that's the rest of my original patch.  I'll come back with an 
updated version of that.




pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Move backup-related code to xlogbackup.c/.h
Next
From: Peter Eisentraut
Date:
Subject: Re: Make finding openssl program a configure or meson option