Horton
Menu

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robins Tharakan <tharakan@gmail.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, Jacob Champion <jacob.champion@enterprisedb.com>, Thomas Munro <thomas.munro@gmail.com>, Michael Paquier <michael@paquier.xyz>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-12-17T04:17:17Z
Lists: pgsql-hackers 
Robins Tharakan <tharakan@gmail.com> writes:
> I am quite late to this discussion, but I am unable to get snakefly up and
> running,
> i.e. I see that all versions failed today (most on
> ssl_passphrase_callback-check
> test [2], but v15/v16 on sslCheck [1] too)

The failures all seem to be in "checkprep", ie the test setup
stage not the test proper.  The log output from that isn't being
captured, making it hard to diagnose.  Could we prevail on you
to install a more up-to-date buildfarm client script on that
machine?  It looks to be running v11, which is rather old.

			regards, tom lane

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