Put back ssl_renegotiation_limit parameter, but only allow 0.
Per a report from Shay Rojansky, Npgsql sends ssl_renegotiation_limit=0
in the startup packet because it does not support renegotiation; other
clients which have not attempted to support renegotiation might well
behave similarly. The recent removal of this parameter forces them to
break compatibility with either current PostgreSQL versions, or
previous ones. Per discussion, the best solution is to accept the
parameter but only allow a value of 0.
Shay Rojansky, edited a little by me.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/84ef9c596e0ef7476cd995349767204022610466
Modified Files
--------------
src/backend/utils/misc/guc.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)