Re: OpenSSL 3.0.0 compatibility

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: OpenSSL 3.0.0 compatibility
Date: 2021-03-12 07:51:39
Message-ID: 7550f110-28d1-5049-62da-17a4a280bd95@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-03-12 08:03:40 Re: Enhance traceability of wal_level changes for backup management
Previous Message Justin Pryzby 2021-03-12 07:45:47 Re: Different compression methods for FPI