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

From Daniel Gustafsson
Subject Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Date
Msg-id C6987F7E-7B5B-4E52-9CA8-F1F1724E6DE3@yesql.se
Whole thread Raw
In response to Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
List pgsql-hackers
> On 19 Apr 2024, at 10:06, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> On 19.04.24 07:37, Michael Paquier wrote:
>> On Thu, Apr 18, 2024 at 12:53:43PM +0200, Peter Eisentraut wrote:
>>> If everything is addressed, I agree that 0001, 0003, and 0004 can go into
>>> PG17, the rest later.
>> About the PG17 bits, would you agree about a backpatch?  Or perhaps
>> you disagree?
>
> I don't think any of these need to be backpatched, at least right now.
>
> 0001 is just a cosmetic documentation tweak, has no reason to be backpatched.
>
> 0003 adds new functionality for LibreSSL.  While the code looks straightforward, we have little knowledge about how
itworks in practice.  How is the buildfarm coverage of LibreSSL (with SSL tests enabled!)?  If people are keen on this,
itmight be better to get it into PG17 and at least let to go through a few months of beta testing. 
>
> 0004 effectively just enhances an error message for LibreSSL; there is little reason to backpatch this.

Hearing no objections to this plan (and the posted v10), I'll go ahead with
0001, 0003 and 0004 into v17 tomorrow.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Why does pgindent's README say to download typedefs.list from the buildfarm?
Next
From: Heikki Linnakangas
Date:
Subject: Re: Direct SSL connection with ALPN and HBA rules