Horton

Re: OpenSSL 3.0.0 compatibility

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-03-12T07:51:39Z
Lists: pgsql-hackers 
On 11.03.21 11:41, Daniel Gustafsson wrote:
> .. and apply the padding changes as proposed in a patch upthread like this (these
> work for all OpenSSL versions I've tested, and I'm rather more puzzled as to
> why we got away with not having them in the past):

Yes, before proceeding with this, we should probably understand why 
these changes are effective and why they haven't been required in the past.

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