Fix memory leak when rejecting bogus DH parameters.
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 20 Mar 2021 16:47:21 +0000 (12:47 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 20 Mar 2021 16:47:21 +0000 (12:47 -0400)
commite835e89a0fd267871e7fbddc39ad00ee3d0cb55c
tree23eb08c33f0d62d37f7f3a5d6aaffd7771b22706
parentf0c2a5bba6c566fad781802537eb17f2977702bc
Fix memory leak when rejecting bogus DH parameters.

While back-patching e0e569e1d, I noted that there were some other
places where we ought to be applying DH_free(); namely, where we
load some DH parameters from a file and then reject them as not
being sufficiently secure.  While it seems really unlikely that
anybody would hit these code paths in production, let alone do
so repeatedly, let's fix it for consistency.

Back-patch to v10 where this code was introduced.

Discussion: https://postgr.es/m/16160-18367e56e9a28264@postgresql.org
src/backend/libpq/be-secure-openssl.c