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: Joe Conway <mail@joeconway.com>, Peter Eisentraut <peter@eisentraut.org>, Tom Lane <tgl@sss.pgh.pa.us>, Jacob Champion <jacob.champion@enterprisedb.com>, Thomas Munro <thomas.munro@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Mikael Kjellström <mikael.kjellstrom@gmail.com>
Date: 2024-08-22T21:13:15Z
Lists: pgsql-hackers 
> On 22 Aug 2024, at 02:31, Michael Paquier <michael@paquier.xyz> wrote:
> 
> On Wed, Aug 21, 2024 at 10:48:38AM -0400, Joe Conway wrote:
>> On 8/21/24 09:01, Peter Eisentraut wrote:
>>> Is anything -- other than this inquiry -- preventing this patch set from
>>> getting committed?

That, and available time.

>> The overwhelming consensus seemed to be "just do it", so FWIW consider my
>> reservations withdrawn ;-)
> 
> Just do it :)

That's my plan, I wanted to wait a bit to see if anyone else chimed in with
concerns.

--
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