Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
От | Jacob Champion |
---|---|
Тема | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |
Дата | |
Msg-id | CAOYmi+=6UK8RkduV_pZrQv=TwSnrLg69jfw6mS6vMdWSgNXwrA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
|
Список | 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 по дате отправления: