Re: Update minimum SSL version
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>
Cc: Magnus Hagander <magnus@hagander.net>, Daniel Gustafsson
<daniel@yesql.se>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-02T10:56:25Z
Lists: pgsql-hackers
On 2019-11-30 04:06, Tom Lane wrote: > I think the real question we have to answer is this: are we intent on > making people upgrade ancient openssl installations? If so, shouldn't > we be doing something even more aggressive than this? If not, wouldn't > the patch need to try to autoconfigure the minimum TLS version? As > proposed, the patch seems to be somewhere in a passive-aggressive middle > ground of being annoying without really enforcing anything. So I don't > quite see the point. The trade-off is that this makes the defaults better for the vast majority of users and gives users of really old systems a nudge that they are no longer in compliance with industry best practices. You need manual steps to set up SSL anyway, so this doesn't introduce an entirely new kind of requirement for the latter group of users. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix handling of OpenSSL's SSL_clear_options
- 7ad544fd8e45 11.7 landed
- 902276ff1309 12.2 landed
- 7d0bcb047717 13.0 landed
-
Remove configure check for OpenSSL's SSL_get_current_compression()
- 28f4bba66b57 13.0 landed
-
Update minimum SSL version
- b1abfec82547 13.0 landed