1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix check for conflicting SSL min/max protocol settings

Browse Source 
Commit 79dfa8a has introduced a check to catch when the minimum protocol
version was set higher than the maximum version, however an error was
getting generated when both bounds are set even if they are able to
work, causing a backend to not use a new SSL context but keep the old
one.

Author: Daniel Gustafsson
Discussion: https://postgr.es/m/14BFD060-8C9D-43B4-897D-D5D9AA6FC92B@yesql.se
This commit is contained in:
Michael Paquier 2020-04-30 08:14:02 +09:00
parent 1816a1c6ff
commit e30b0b5cfa
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/libpq/be-secure-openssl.c
View File

@ -226,12 +226,14 @@ be_tls_init(bool isServerStart)
* as the code above would have already generated an error.
*/
if (ssl_ver_min > ssl_ver_max)
{
ereport(isServerStart ? FATAL : LOG,
(errmsg("could not set SSL protocol version range"),
errdetail("\"%s\" cannot be higher than \"%s\"",
"ssl_min_protocol_version",
"ssl_max_protocol_version")));
goto error;
goto error;
}
}
/* disallow SSL session tickets */