Horton

Re: Update minimum SSL version

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Magnus Hagander <magnus@hagander.net>, Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-04T15:24:01Z
Lists: pgsql-hackers 
On 2019-12-04 13:53, Tom Lane wrote:
> So, what exactly are we going to set as the new minimum version in
> each case?  I'll have to go update my trailing-edge-Johnnie buildfarm
> critters, and it'd make sense to have them continue to test the
> oldest nominally-supported versions.
> 
> For OpenSSL it seems like 1.0.1a is the target, per the above
> discussion.
> 
> For Python, I'll just observe that RHEL6 ships 2.6.6, so we can't
> bump up to 2.7.

Yes, it would be Python 2.6.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Fix handling of OpenSSL's SSL_clear_options

  2. Remove configure check for OpenSSL's SSL_get_current_compression()

  3. Update minimum SSL version