pgsql: Use BIO_{get,set}_app_data instead of BIO_{get,set}_data. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Use BIO_{get,set}_app_data instead of BIO_{get,set}_data.
Date
Msg-id E1r81yU-007gi1-4Z@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Use BIO_{get,set}_app_data instead of BIO_{get,set}_data.

We should have done it this way all along, but we accidentally got
away with using the wrong BIO field up until OpenSSL 3.2.  There,
the library's BIO routines that we rely on use the "data" field
for their own purposes, and our conflicting use causes assorted
weird behaviors up to and including core dumps when SSL connections
are attempted.  Switch to using the approved field for the purpose,
i.e. app_data.

While at it, remove our configure probes for BIO_get_data as well
as the fallback implementation.  BIO_{get,set}_app_data have been
there since long before any OpenSSL version that we still support,
even in the back branches.

Also, update src/test/ssl/t/001_ssltests.pl to allow for a minor
change in an error message spelling that evidently came in with 3.2.

Tristan Partin and Bo Andreson.  Back-patch to all supported branches.

Discussion: https://postgr.es/m/CAN55FZ1eDDYsYaL7mv+oSLUij2h_u6hvD4Qmv-7PK7jkji0uyQ@mail.gmail.com

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/efa8f606402c3d7ca361932418cbcc2600b6c059

Modified Files
--------------
configure                                |  2 +-
configure.ac                             |  2 +-
meson.build                              |  1 -
src/backend/libpq/be-secure-openssl.c    | 11 +++--------
src/include/pg_config.h.in               |  3 ---
src/interfaces/libpq/fe-secure-openssl.c | 11 +++--------
src/test/ssl/t/001_ssltests.pl           |  6 +++---
src/tools/msvc/Solution.pm               |  2 --
8 files changed, 11 insertions(+), 27 deletions(-)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Fix comment about ressortgrouprefs being unique in setop plans.
Next
From: Tom Lane
Date:
Subject: pgsql: Clean up usage of bison precedence for non-operator keywords.