Add connection parameters to control SSL protocol min/max in libpq
These two new parameters, named sslminprotocolversion and
sslmaxprotocolversion, allow to respectively control the minimum and the
maximum version of the SSL protocol used for the SSL connection attempt.
The default setting is to allow any version for both the minimum and the
maximum bounds, causing libpq to rely on the bounds set by the backend
when negotiating the protocol to use for an SSL connection. The bounds
are checked when the values are set at the earliest stage possible as
this makes the checks independent of any SSL implementation.
Author: Daniel Gustafsson
Reviewed-by: Michael Paquier, Cary Huang
Discussion: https://postgr.es/m/4F246AE3-A7AE-471E-BD3D-C799D3748E03@yesql.se
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/ff8ca5fadd819155c82bd16fcc6b7231af649cf8
Modified Files
--------------
contrib/postgres_fdw/expected/postgres_fdw.out | 2 +-
doc/src/sgml/libpq.sgml | 54 ++++++++++++
src/backend/libpq/be-secure-openssl.c | 3 +
src/interfaces/libpq/fe-connect.c | 113 +++++++++++++++++++++++++
src/interfaces/libpq/fe-secure-openssl.c | 89 +++++++++++++++++++
src/interfaces/libpq/libpq-int.h | 2 +
src/test/ssl/t/001_ssltests.pl | 23 ++++-
7 files changed, 284 insertions(+), 2 deletions(-)
