Horton
Menu

Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?

Daniel Gustafsson <daniel@yesql.se>

View thread
From: Daniel Gustafsson <daniel@yesql.se>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-05-26T08:09:35Z
Lists: pgsql-hackers 
> On 26 May 2023, at 04:08, Michael Paquier <michael@paquier.xyz> wrote:
> On Thu, May 25, 2023 at 10:16:27AM +0200, Daniel Gustafsson wrote:

>> The changes to the Windows buildsystem worry me a bit, but they don't move the
>> goalposts in either direction wrt to LibreSSL on Windows so for the purpose of
>> this patch we don't need to do more.  Longer term we should either make
>> LibreSSL work on Windows builds, or explicitly not support it on Windows.
> 
> Yes, I was wondering what to do about that in the long term.  With the
> argument that the MSVC scripts may be gone over meson, it is not
> really appealing to dig into that.

Yeah, let's revisit this during the v17 cycle when the future of these scripts
will become clearer.

> Something that was missing in 0001 is the bump of OPENSSL_API_COMPAT
> in meson.build.  This was in 0002.
> 
> Please find attached an updated patch only for the removal of 1.0.1.
> Thanks for the review. 

LGTM.

--
Daniel Gustafsson

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove obsolete unconstify()

  2. Only perform pg_strong_random init when required

  3. Remove support for OpenSSL older than 1.1.0

  4. Support SSL_R_VERSION_TOO_LOW when using LibreSSL

  5. Support disallowing SSL renegotiation when using LibreSSL

  6. Doc: Use past tense for things which happened in the past

  7. Remove support for OpenSSL 1.0.1

  8. Remove support for OpenSSL 0.9.8 and 1.0.0