| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | 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-09-10 08:11:25 |
| Message-ID: | 1A2530CF-9CC0-450C-8039-94E9E25D61DB@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 10 Sep 2024, at 10:01, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>> And pushed. All BF owners with animals using 1.0.2 have been notified but not
>> all have been updated (or modified to skip SSL) so there will be some failing.
>
> A small follow-up for this: With the current minimum OpenSSL version being 1.1.0, we can remove an unconstify() call; see attached patch.
Nice catch.
> See this OpenSSL commit: <https://github.com/openssl/openssl/commit/8ab31975ba>. The analogous LibreSSL change is here: <https://cvsweb.openbsd.org/src/lib/libcrypto/bio/bss_mem.c?rev=1.17&content-type=text/x-cvsweb-markup>.
> I don't know if we have a concrete minimum LibreSSL version, but the change is about as old as the OpenSSL change.
We've never documented the minimum LibreSSL version we support, but given that
we regularly test LibreSSL and fix breakage in our support I think we should.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2024-09-10 08:19:37 | Re: Pgoutput not capturing the generated columns |
| Previous Message | Zhijie Hou (Fujitsu) | 2024-09-10 08:10:33 | RE: Conflict detection for update_deleted in logical replication |