Re: OpenSSL 3.0.0 compatibility

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
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-11 23:22:45
Message-ID: AE50EA80-7260-4A69-AFE3-E1BF7AB2B5FF@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Nancarrow 2021-03-11 23:26:03 Re: Parallel INSERT (INTO ... SELECT ...)
Previous Message Peter Eisentraut 2021-03-11 23:04:12 Re: OpenSSL 3.0.0 compatibility