Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions
Date
Msg-id cc9f4f2c-9839-43e3-b111-1ed572cc5180@eisentraut.org
Whole thread Raw
In response to Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions  (David Benjamin <davidben@google.com>)
Responses Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions
List pgsql-hackers
On 19.05.24 20:07, David Benjamin wrote:
> On Sun, May 19, 2024 at 12:21 PM Tom Lane <tgl@sss.pgh.pa.us 
> <mailto:tgl@sss.pgh.pa.us>> wrote:
> 
>     Per the cfbot [1], this patch needs a rebase over the ALPN-related
>     commits.  It still isn't likely to get human attention before the
>     July commitfest, but you can save some time by making sure it's
>     in a reviewable state before that.
> 
> 
> Rebased version attached. (The conflict was pretty trivial. Both patches 
> add a field to some struct.)

Note that there is a concurrent plan to drop support for OpenSSL older 
than 1.1.1 [0], which would obsolete your configure test for 
BIO_get_data.  Whoever commits these should be sure to coordinate this.


[0]: https://www.postgresql.org/message-id/flat/ZG3JNursG69dz1lr@paquier.xyz




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions