| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2020-05-29 06:06:30 |
| Message-ID: | 1c5e12775af688bcd086a1976902f01996bba526.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2020-05-29 at 00:16 +0200, Daniel Gustafsson wrote:
> Since OpenSSL is now releasing 3.0.0-alpha versions, I took a look at using it
> with postgres to see what awaits us. As it is now shipping in releases (with
> GA planned for Q4), users will probably soon start to test against it so I
> wanted to be prepared.
>
> Regarding the deprecations, we can either set preprocessor directives or use
> compiler flags to silence the warning and do nothing (for now), or we could
> update to the new API. We probably want to different things for master vs
> back-branches, but as an illustration of what the latter could look like I've
> implemented this in 0001.
An important question will be: if we convert to functions that are not deprecated,
what is the earliest OpenSSL version we can support?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | matsumura.ryo@fujitsu.com | 2020-05-29 06:41:40 | RE: archive status ".ready" files may be created too early |
| Previous Message | Masahiko Sawada | 2020-05-29 05:49:54 | Re: Internal key management system |