Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\))
Subject: Re: PostgreSQL and OpenSSL 4.0.0
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <af2ODKxUkLzFIiuX@paquier.xyz>
Date: Fri, 8 May 2026 09:21:25 +0200
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <95045A62-9A81-4AD8-BA25-D8648BD68499@yesql.se>
References: <066B07BB-85FA-487C-BE8C-40F791CFC3C4@yesql.se>
 <aeKrQfeyDLVE3cmw@paquier.xyz>
 <65C5DC15-DE27-4D36-8AEE-A854C23B3834@yesql.se>
 <af0OcVKUaAMW1RaR@paquier.xyz> <898414.1778192534@sss.pgh.pa.us>
 <1A5104C0-E9EF-4D90-9627-23D3D909104B@yesql.se>
 <af2ODKxUkLzFIiuX@paquier.xyz>
To: Michael Paquier <michael@paquier.xyz>
Archived-At: 
 <https://www.postgresql.org/message-id/95045A62-9A81-4AD8-BA25-D8648BD68499%40yesql.se>
Precedence: bulk

> On 8 May 2026, at 09:17, Michael Paquier <michael@paquier.xyz> wrote:
>=20
> On Fri, May 08, 2026 at 09:07:41AM +0200, Daniel Gustafsson wrote:
>> Not sure I follow, anyone still building with a X years out of =
support OpenSSL
>> will most likely keep doing so regardless of what CVE's are =
published.  It
>> could of course make backpatching trickier if thats what you mean?
>=20
> Argh.  I've misread you here, reading a "lowest" rather than
> "highest".   Documenting that 3.6 is the highest version support on=20
> 14-stable would also work here.  My apologies for the confusion.

Ah, now it makes more sense =3D)

> If the patches for REL_14_STABLE to add support for 4.0 prove to be
> low-risk while messing with 1.0.1, that would the best course of
> action, of course.

I think the changes are straightforward enough that we can go ahead with =
them.
I'll re-test and re-post a new patchset for all branches once the minors =
ship.

--
Daniel Gustafsson