| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2020-09-23 08:19:55 |
| Message-ID: | 20200923081955.GD7405@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 22, 2020 at 02:01:18PM +0200, Daniel Gustafsson wrote:
> Another option would be to follow OpenSSL's deprecations and mark these ciphers
> as deprecated such that we can remove them in case they indeed get removed from
> libcypto. That would give users a heads-up that they should have a migration
> plan for if that time comes.
Does that mean a deprecation note in the docs as well as a WARNING
when attempting to use those ciphers in pgcryto with the version of
OpenSSL marking such ciphers as deprecated? I would assume that we
should do both, rather than only one of them to bring more visibility
to the user.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2020-09-23 08:44:20 | Re: OpenSSL 3.0.0 compatibility |
| Previous Message | Katsuragi Yuta | 2020-09-23 08:17:04 | Re: [PATCH] Add features to pg_stat_statements |