Re: svn commit: r1843478 - /httpd/test/framework/trunk/t/ssl/ocsp.t
On 10/15/2018 01:25 PM, William A Rowe Jr wrote:
On Sun, Oct 14, 2018 at 4:38 PM Dennis Clarke <dclarke@xxxxxxxxxxxxx
As a red herring that illustrates how oddball the situation could get :
$ /usr/sfw/bin/openssl version 2>&1 | cut -f1 -d\(
OpenSSL 0.9.7d 17 Mar 2004
I think we can safely ignore OpenSSL 0.9.7 as the final release was over
11 years ago.
Like I was saying it is a red^H^H^Hdead herring :-\
The 0.9.8 will only be encountered on rusting RHEL 5 (mainstream EOL a
year ago in spring) and similarly ancient installations across other
1.0.0 only saw the light of day in broad adoption via
SLES 11 (mainstream EOL spring next year).
The Oracle folks pushed out 1.0.2 onto legacy Solaris a while ago :
$ which openssl
$ /usr/bin/openssl version
OpenSSL 1.0.2n 7 Dec 2017
> There are a good number of 1.0.1 installations lingering around...
> Breaking 1.0.1 support would seem unwise
A disaster is what I am thinking.
> but we probably should start
> ignoring 0.9.8 and 1.0.0 for all practical purposes.
Anything pre 1.x.y should be considered rust.