Discussion:
ITUGLIB Update: OpenSSL 1.1.1w
(too old to reply)
Randall
2023-09-11 23:13:42 UTC
Permalink
The last set of builds for the OpenSSL 1.1.1 series has been released by ITUGLIB, with the usual set of builds. There are no plans for any future patches to this series of OpenSSL.

From the OpenSSL notice:

OpenSSL version 1.1.1w released
===============================

OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/

The OpenSSL project team is pleased to announce the release of
version 1.1.1w of our open source toolkit for SSL/TLS.

This is the last public release of OpenSSL 1.1.1. Extended
support is available to premium support customers.

For details of the changes, see the release notes at:

https://www.openssl.org/news/openssl-1.1.1-notes.html

OpenSSL 1.1.1w is available for from the ITUGLIB github at https://github.com/ituglib/openssl on the ituglib_release branch.

If you need future patches to 1.1.1, please contact me directly.

Regards,
Randall Becker
On behalf of the ITUGLIB Technical Committee
Randall
2023-10-24 15:42:17 UTC
Permalink
Post by Randall
The last set of builds for the OpenSSL 1.1.1 series has been released by ITUGLIB, with the usual set of builds. There are no plans for any future patches to this series of OpenSSL.
OpenSSL version 1.1.1w released
===============================
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1w of our open source toolkit for SSL/TLS.
This is the last public release of OpenSSL 1.1.1. Extended
support is available to premium support customers.
https://www.openssl.org/news/openssl-1.1.1-notes.html
OpenSSL 1.1.1w is available for from the ITUGLIB github at https://github.com/ituglib/openssl on the ituglib_release branch.
If you need future patches to 1.1.1, please contact me directly.
Regards,
Randall Becker
On behalf of the ITUGLIB Technical Committee
There was a report that the 1.1.1w package for J-series contained L-series objects. I just tested this and it is not the case. The package runs properly on a J-series machine. Good luck.
Loading...