| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |
| Date: | 2024-04-04 18:03:35 |
| Message-ID: | CAOYmi+=KOxuj3z91ijwya6ycdBhhc7LDBathdFVy3y8rf=Qi_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 3, 2024 at 3:27 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> The patch will also need to be adjusted to work with LibreSSL, but I know Jacob
> was looking into that so ideally we should have something to review before
> the weekend.
v3 does that by putting back checks for symbols that aren't part of
LibreSSL (tested back to 2.7, which is where the 1.1.x APIs started to
arrive). It also makes adjustments for the new OPENSSL_API_COMPAT
version, getting rid of OpenSSL_add_all_algorithms() and adding a
missing header.
This patch has a deficiency where 1.1.0 itself isn't actually rejected
at configure time; Daniel's working on an explicit check for the
OPENSSL/LIBRESSL_VERSION_NUMBER that should fix that up. There's an
open question about which version we should pin for LibreSSL, which
should ultimately come down to which versions of OpenBSD we want PG17
to support.
Thanks,
--Jacob
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Remove-support-for-OpenSSL-1.0.2-and-1.1.0.patch | application/octet-stream | 21.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-04-04 18:06:02 | Re: WIP Incremental JSON Parser |
| Previous Message | Robert Haas | 2024-04-04 18:02:42 | Re: On disable_cost |