pgsql: Fix memory leak in libpq when using sslmode=verify-full - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Fix memory leak in libpq when using sslmode=verify-full
Date
Msg-id E1jR1Nl-0001Lb-D1@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix memory leak in libpq when using sslmode=verify-full

Checking if Subject Alternative Names (SANs) from a certificate match
with the hostname connected to leaked memory after each lookup done.

This is broken since acd08d7 that added support for SANs in SSL
certificates, so backpatch down to 9.5.

Author: Roman Peshkurov
Reviewed-by: Hamid Akhtar, Michael Paquier, David Steele
Discussion: https://postgr.es/m/CALLDf-pZ-E3mjxd5=bnHsDu9zHEOnpgPgdnO84E2RuwMCjjyPw@mail.gmail.com
Backpatch-through: 9.5

Branch
------
REL9_6_STABLE

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

Modified Files
--------------
src/interfaces/libpq/fe-secure-openssl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: pgsql: Document partitiong tables ancillary object handling some more
Next
From: Alvaro Herrera
Date:
Subject: pgsql: psql \d: Display table where trigger is defined, if inherited