Horton

Re: OpenSSL 3.0.0 compatibility

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-07-19T14:29:54Z
Lists: pgsql-hackers 
On 2020-07-16 13:45, Michael Paquier wrote:
> On Thu, Jul 16, 2020 at 10:58:58AM +0200, Peter Eisentraut wrote:
>>   if test "$with_openssl" = yes ; then
>>     dnl Order matters!
>> +  AC_DEFINE(OPENSSL_API_COMPAT, [10001],
>> +            [Define to the OpenSSL API version in use. This avoids
>>     deprecation warnings from newer OpenSSL versions.])
>>     if test "$PORTNAME" != "win32"; then
> 
> I think that you should additionally mention the version number
> directly in the description, so as when support for 1.0.1 gets removed
> it is possible to grep for it, and then adjust the number and the
> description.

Good point.  I have committed it with that adjustment.  Also, I had the 
format of the version number wrong, so I changed that, too.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Define OPENSSL_API_COMPAT

  2. Add alternative output for OpenSSL 3 without legacy loaded

  3. Disable OpenSSL EVP digest padding in pgcrypto

  4. pgcrypto: Check for error return of px_cipher_decrypt()

  5. OpenSSL 3.0.0 compatibility in tests

  6. Make ssl certificate for ssl_passphrase_callback test via Makefile

  7. Provide a TLS init hook