From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Update minimum SSL version |
Date: | 2019-12-04 15:24:01 |
Message-ID: | e5b76e74-12be-a67a-b916-f0ae4ab2f860@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2019-12-04 15:24:37 | Re: Update minimum SSL version |
Previous Message | Alvaro Herrera | 2019-12-04 14:40:21 | adding strndup |