From: | Robins Tharakan <tharakan(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |
Date: | 2024-12-17 02:54:49 |
Message-ID: | CAEP4nAw2cJcU7DLmj6CJc6eJAYG_Rt5VhCbUvhiN_9fFaohctQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Thu, 4 Apr 2024 at 05:42, Daniel Gustafsson <daniel(at)yesql(dot)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:
1.
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2024-12-16%2014%3A04%3A25
2.
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2024-12-16%2014%3A01%3A21
-
robins
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2024-12-17 03:11:37 | Re: Regression tests fail on OpenBSD due to low semmns value |
Previous Message | Tom Lane | 2024-12-17 02:11:05 | Re: Missing initialization steps in --check and --single modes |