Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Date
Msg-id CAOYmi+=6UK8RkduV_pZrQv=TwSnrLg69jfw6mS6vMdWSgNXwrA@mail.gmail.com
Whole thread Raw
In response to Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
List pgsql-hackers
On Fri, Apr 5, 2024 at 9:59 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> Attached is a WIP patch to get more eyes on it, the Meson test for 1.1.1 fails
> on Windows in CI which I will investigate next.

The changes for SSL_OP_NO_CLIENT_RENEGOTIATION and
SSL_R_VERSION_TOO_LOW look good to me.

>     -    Remove support for OpenSSL 1.0.2 and 1.1.0
>     +    Remove support for OpenSSL 1.0.2

I modified the commit message while working on v3 and forgot to put it
back before posting, sorry.

> +++ b/src/include/pg_config.h.in
> @@ -84,9 +84,6 @@
>  /* Define to 1 if you have the <crtdefs.h> header file. */
>  #undef HAVE_CRTDEFS_H
>
> -/* Define to 1 if you have the `CRYPTO_lock' function. */
> -#undef HAVE_CRYPTO_LOCK

An autoreconf run on my machine pulls in more changes (getting rid of
the symbols we no longer check for).

--Jacob



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: fasthash32() returning uint64?
Next
From: Tom Lane
Date:
Subject: Re: IPC::Run::time[r|out] vs our TAP tests