OpenSSL 3.0 Beta Released: New Features and Changes
OpenSSL 3.0 has entered its beta stage, treated as a release candidate, inviting users to build, test, and provide feedback, while introducing a new Apache 2.0 license, provider‑based architecture, FIPS‑validated provider, pluggable TLS 1.3 groups, new encoders/decoders, CMP support, and updated APIs, with ABI changes requiring recompilation.
OpenSSL 3.0 has released its first beta version, which the development team treats as a release candidate and encourages all users to build, test, and provide feedback.
Over the past months the team has performed extensive work, with more than 300 contributors submitting over 7,000 commits for the 3.0 release.
The main new features and changes include:
Adoption of a new open‑source license: the Apache License 2.0, replacing the previous dual OpenSSL/SSLeay license.
A new version‑control scheme (link provided in the original announcement).
A provider‑based architecture that replaces the old engine interface, offering greater flexibility and allowing third‑party authors to add new cryptographic algorithms.
An additional Provider that will be validated against the FIPS 140‑2 standard.
A fully pluggable TLS 1.3 group, enabling third‑party providers to add new TLS key‑exchange/encapsulation groups.
Support for new encoders and decoders.
A complete implementation of the Certificate Management Protocol (CMP).
New APIs for handling MAC, KDF, and random number generation (EVP_RAND).
Integration support for kernel TLS.
OpenSSL 3.0 represents a major version upgrade with ABI changes, requiring users to recompile all dependent applications, and it also introduces some minor API‑breaking changes.
Laravel Tech Community
Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.