Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? - Mailing list pgsql-hackers

From Robins Tharakan
Subject Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Date
Msg-id CAEP4nAw2cJcU7DLmj6CJc6eJAYG_Rt5VhCbUvhiN_9fFaohctQ@mail.gmail.com
Whole thread Raw
In response to Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
List pgsql-hackers
Hi,

On Thu, 4 Apr 2024 at 05:42, Daniel Gustafsson <daniel@yesql.se> wrote:

massasauga and snakefly run the ssl_passphrase_callback-check test but none of
these run the ssl-check tests AFAICT, so we have very low coverage as is.  The
fact that very few animals run the ssl tests is a pet peeve of mine, it would
be nice if we could get broader coverage there.


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)

This machine has OpenSSL v1.0.2k so I am not expecting it to work on v17+,
but I was assuming at least the older versions should still be working. Also despite
adding --without-openssl the older versions still fail [2].

Is upgrading OpenSSL the only way to get snakefly back to green?

Reference:

-
robins

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Missing initialization steps in --check and --single modes
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Conflict detection for update_deleted in logical replication