OpenSSL announces final release of OpenSSL 3.2.0 #22806
Replies: 2 comments 7 replies
-
|
Congratulations on the release! Is it correct that OpenSSL 3.2 is binary compatible with 3.1 so it should be a drop in replacement and just work with Apache httpd, curl, ... without recompiling those |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it is backwards binary compatible with 3.1, and 3.0. So if you compile with 3.0 you should be able to run with 3.2. Not the other way around as there can be API additions that will be obviously missing on older versions. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed — we have a strict API/ABI compatibility policy. Only major releases (i.e. 4.x) will be potentially incompatible. You can find more information in our versioning policy. When considering an upgrade to a new minor release (3.2) it is recommended to check the release notes for the release. This lists the potentially breaking changes at the top. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the fast replies and the good news :) Yeah I've already checked out those pages 👍 |
Beta Was this translation helpful? Give feedback.
-
|
So happy to see this release. Congratulations! I don't see anything in the announcement or the Release Strategy page on the intended support lifetime for 3.2. I see the next feature release will be 3.3 in April but that seems orthogonal to how long 3.2 is intended to be supported. Did I miss that somewhere? Sorry if I missed something obvious. |
Beta Was this translation helpful? Give feedback.
-
|
Unless 3.2 is later declared to be an LTS release (which is unlikely) it will be supported for 2 years - i.e., the support ends on 23 Nov 2025. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm. We should update the release strategy page. The download page has already been updated with this information. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Thank you folks. That's what I assumed but didn't want to assume. I should have thought about looking at the download page. Doh! |
Beta Was this translation helpful? Give feedback.
-
We are pleased to announce the immediate availability of OpenSSL 3.2.0. OpenSSL 3.2.0 is the first General Availability release of the OpenSSL 3.2 release line, and incorporates a number of new features, including:
and Brotli
A complete summary of the major new features and significant changes in OpenSSL 3.2 can be found in the NEWS file; a more detailed list of changes in OpenSSL 3.2 can be found in the CHANGES file on GitHub.
Users interested in using the new QUIC functionality are encouraged to read the README file for QUIC, which provides links to relevant documentation and example code.
OpenSSL 3.2.0 can be downloaded as a source tarball here or obtained from our release tag on GitHub. Checksums and release signatures may be found on the Downloads page.
The next feature release after OpenSSL 3.2 will be OpenSSL 3.3, which will be released no later than 30 April 2024. This release is expected to include QUIC server support. The determination of what other features will be shipped in OpenSSL 3.3 is ongoing and will be decided by our recently announced Release Steering Committee.
We would like to thank all of our users and communities for their continued use and support of OpenSSL. OpenSSL 3.2.0 represents the product of over two years of development work, comprising over 4,000 commits and contributions from over 300 different authors. This release would not be possible without the innumerable bug reports, pull requests, code reviews and feedback we continue to receive from our community.
We would also like to extend our thanks to all of the organisations who have supported the development of OpenSSL 3.2 financially, whether by holding a support contract with us or by sponsoring OpenSSL. These organisations provide a sustainable income source for the project, and continue to enable us to fund consultants to work full time for the OpenSSL project. Over 60% of commits in the past year were funded by the OpenSSL project itself, thanks to our support customers and sponsors.
As always, bug reports and issues relating to OpenSSL can be filed on our issue tracker, and questions about using OpenSSL 3.2 can be posted on GitHub Discussions.
Comments on this release are also welcomed below, or via email to feedback@openssl.org.
View blogpost
Beta Was this translation helpful? Give feedback.
All reactions