Re: Update minimum SSL version
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Michael Paquier <michael@paquier.xyz>,
Magnus Hagander <magnus@hagander.net>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-05T14:50:50Z
Lists: pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes: >> On 5 Dec 2019, at 02:48, Michael Paquier <michael@paquier.xyz> wrote: >> So it seems to me that we are able to correctly >> detect the presence of this function in the configure checks if >> building with 1.1.0~, but not other versions. > Yes, we can't use AC_CHECK_FUNCS but would need to use AC_COMPILE_IFELSE (or a > similar check) in order to detect the macro. configure already has a similar issue for isinf(). (I thought there were more cases, actually, but I don't see another right now.) We could just duplicate that logic, or maybe it's time to wrap it up in an autoconf macro? > Yes, if we're dropping older versions such that all supported versions have the > function, then keeping the autoconf check would be quite pointless. True as far as HEAD goes. What I'd like to know is whether not realizing that SSL_clear_options is present causes any functional issues that would justify back-patching a fix. regards, tom lane
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