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-23 10:52:22 |
Message-ID: | 0529d64c-2240-854b-bf9e-b6f8f04c2ab2@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12.03.21 00:22, Daniel Gustafsson wrote:
>> On 12 Mar 2021, at 00:04, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>
>> On 11.03.21 11:41, Daniel Gustafsson wrote:
>>> Then there are a few where we get padding back where we really should have
>>> ended up with the "Cipher cannot be initialized" error since DES is in the
>>> legacy provider:
>>> select decrypt_iv(decode('50735067b073bb93', 'hex'), '0123456', 'abcd', 'des');
>>> - decrypt_iv
>>> -------------
>>> - foo
>>> + decrypt_iv
>>> +----------------------------------
>>> + \177\177\177\177\177\177\177\177
>>> (1 row)
>>
>> The attached patch appears to address these cases.
>
> +1, males a lot of sense. This removes said errors when running without the
> legacy provider enabled, and all tests still pass with it enabled.
I have committed this to master. I see that the commit fest entry has
been withdrawn in the meantime. I suppose we'll come back to this,
including possible backpatching, when OpenSSL 3.0.0 is in beta.
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2021-03-23 11:01:28 | Re: New IndexAM API controlling index vacuum strategies |
Previous Message | Ajin Cherian | 2021-03-23 10:48:51 | Re: [HACKERS] logical decoding of two-phase transactions |