Re: OpenSSL 3.0.0 compatibility

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: OpenSSL 3.0.0 compatibility
Date: 2021-07-20 21:55:26
Message-ID: BC256EC9-F176-4D7F-989C-A72AAC14973D@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Jul 2021, at 09:54, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Jul 20, 2021 at 01:23:42AM +0200, Daniel Gustafsson wrote:
>> Another aspect of OpenSSL 3 compatibility is that of legacy cipher support, and
>> as we concluded upthread it's best to leave that to the user to define in
>> openssl.cnf. The attached 0002 adds alternative output files for 3.0.0
>> installations without the legacy provider loaded, as well as adds a note in the
>> pgcrypto docs to enable it in case DES is needed. It does annoy me a bit that
>> we don't load the openssl.cnf file for 1.0.1 if we start mentioning it in the
>> docs for other versions, but it's probably not worth the effort to fix it given
>> the lack of complaints so far (it needs a call to OPENSSL_config(NULL); guarded
>> to HAVE_ macros for 1.0.1).
>
> Sounds sensible as a whole.

Thanks for reviewing!

> Another thing I can notice is that
> OpenSSL 3.0.0beta1 has taken care of the issue causing diffs in the
> tests of src/test/ssl/. So once pgcrypto is addressed, it looks like
> there is nothing left for this thread.

That's a good point, I forgot to bring that up.

--
Daniel Gustafsson https://vmware.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2021-07-20 22:16:10 Re: Signed vs Unsigned (take 2) (src/backend/storage/ipc/procarray.c)
Previous Message Tomas Vondra 2021-07-20 21:41:20 Re: logical decoding and replication of sequences