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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-04-03 15:29:35
Message-ID: 103258.1712158175@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> As far as I can tell, no versions of LibreSSL so far provide
> X509_get_signature_info(), so this patch is probably a bit too
> aggressive.

Another problem with cutting support is how many buildfarm members
will we lose. I scraped recent configure logs and got the attached
results. I count 3 machines running 1.0.1, 18 running some flavor
of 1.0.2, and 7 running various LibreSSL versions. We could
probably retire or update the 1.0.1 installations, but the rest
would represent a heavier lift. Notably, it seems that what macOS
is shipping is LibreSSL.

regards, tom lane

Attachment Content-Type Size
opensslversions text/plain 8.8 KB
opensslmeson text/plain 1.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Panda Developpeur 2024-04-03 15:49:41 Re: [PATCH] Modify pg_ctl to detect presence of geek user
Previous Message Tristan Partin 2024-04-03 15:16:58 Re: psql not responding to SIGINT upon db reconnection