Horton
Menu

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

Robins Tharakan <tharakan@gmail.com>

View thread
From: Robins Tharakan <tharakan@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>, Jacob Champion <jacob.champion@enterprisedb.com>, Thomas Munro <thomas.munro@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-12-17T11:50:43Z
Lists: pgsql-hackers 
On Tue, 17 Dec 2024 at 16:59, Michael Paquier <michael@paquier.xyz> wrote:

> +1.  Robins, feel free to ping me directly if you need help with this
> host.
>

Much appreciated Michael. Thankfully the new client worked without much
hiccup
(once it got the correct config file).

This is an old instance and IIRC gcc 7.3.1 gave me trouble sometime back. So
like alligator, I upgraded gcc recently. That (along with what feels like
cron config)
needs some attention and I should be able to stabilize the results soon.

-
robins

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