| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2020-09-22 09:37:57 |
| Message-ID: | 80f237dd-2ce2-ae60-5e74-36098a2f3720@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-09-18 16:11, Daniel Gustafsson wrote:
> Since we support ciphers that are now deprecated, we have no other choice than
> to load the legacy provider.
Well, we could just have deprecated ciphers fail, unless the user loads
the legacy provider in the OS configuration. There might be an argument
that that is more proper.
As a more extreme analogy, what if OpenSSL remove a cipher from the
legacy provider? Are we then obliged to reimplement it manually for the
purpose of pgcrypto? Probably not.
The code you wrote to load the necessary providers is small enough that
I think it's fine, but it's worth pondering this question briefly.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2020-09-22 10:38:46 | Re: Parallel copy |
| Previous Message | vignesh C | 2020-09-22 09:14:21 | Re: Parallel copy |