Re: Removal of support for OpenSSL 0.9.8 and 1.0.0
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-12-06T06:22:42Z
Lists: pgsql-hackers
On Fri, Dec 06, 2019 at 10:33:23AM +0900, Michael Paquier wrote: > Thanks. Another argument in favor of dropping 1.0.0 and 0.9.8 is that > it is a pain to check an OpenSSL patch across that many versions, > multiplied by the number of Postgres branches in need of patching :) I have done nothing for 0003 yet. Let's wait a bit and see if others have more arguments in favor of it or not. > I have applied 0001 on HEAD for now as that's a simple cleanup (I > would not backpatch that though). For 0002, I would prefer be sure > that we reach the right conclusion. My take is to: > 1) Apply 0002 only on HEAD to remove the check for clear_options. > 2) Apply something like Daniel's patch in [1] for REL_12_STABLE and > REL_11_STABLE as we care about this routine since e3bdb2d to not mess > up with past versions of NetBSD which worked previously on our > released branches. (The patch looks fine at quick glance and I > haven't tested it yet) 0002 is now applied, and did things as described in the above paragraph. -- Michael
Commits
-
Remove support for OpenSSL 0.9.8 and 1.0.0
- 7b283d0e1d1d 13.0 landed
-
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