| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2021-03-11 13:08:20 |
| Message-ID: | YEoWRC+ykZMcxoDo@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 11, 2021 at 11:41:22AM +0100, 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):
No objections from here to disable the padding and tighten a bit the
error checks on the amount of data encrypted or decrypted based on
the block size. This indeed works correctly down to OpenSSL 1.0.1 as
far as I have tested, so let's extract this part first, and figure the
rest after there is a beta.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2021-03-11 13:09:39 | Re: Disallow cancellation of waiting for synchronous replication |
| Previous Message | houzj.fnst@fujitsu.com | 2021-03-11 13:01:42 | RE: Parallel INSERT (INTO ... SELECT ...) |