| 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-11 23:04:12 |
| Message-ID: | 9e9c431c-0adc-7a6d-9b1a-915de1ba3fe7@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Check-for-error-return-of-px_cipher_decrypt.patch | text/plain | 924 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2021-03-11 23:22:45 | Re: OpenSSL 3.0.0 compatibility |
| Previous Message | Tomas Vondra | 2021-03-11 22:50:05 | Re: Self-join optimisation |