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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix memory leak in libpq when using sslmode=verify-full
Date: 2020-04-21 22:28:45
Message-ID: E1jR1Nl-0001Le-DP@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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_5_STABLE

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

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

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2020-04-21 22:38:15 pgsql: psql \d: Display table where trigger is defined, if inherited
Previous Message Alvaro Herrera 2020-04-21 21:17:44 pgsql: Document partitiong tables ancillary object handling some more