OpenSSL 4.0.0 Released
·2026.04.16 07:33
Key point
A major OpenSSL 4.0.0 release including ECH support and legacy removals.
Details
OpenSSL 4.0.0 has been released. This release is a major turning point including numerous new features and breaking changes.
The key changes are as follows.
- Built-in ECH (Encrypted Client Hello, RFC 9849) support means a separate implementation is no longer needed to protect TLS client privacy.
- SSLv2 Client Hello, SSLv3, and engine code have been completely removed, finalizing the break with legacy protocols.
- RFC 8998-based SM2 signatures (sm2sig_sm3), key exchange (curveSM2), and post-quantum group curveSM2MLKEM768 support have been added.
- New cryptographic features have been introduced, including cSHAKE, ML-DSA-MU digest, SNMP KDF, and SRTP KDF.
- RFC 7919-based FFDHE key exchange negotiation is now possible in TLS 1.2.
There are also significant changes on the security and operations side.
- When installing the FIPS module, the
-defer_testsoption now allows deferred execution of FIPS self-tests. - A lower bound check is now enforced when using the FIPS provider with
PKCS5_PBKDF2_HMAC. - Additional checks have been reinforced for CRL validation as well.
The API and build system have also been modernized.
constqualifiers have been added to the signatures of numerous API functions.ASN1_STRINGopacification has been carried out.- For deprecated functions such as
X509_cmp_time(), usingX509_check_certificate_times()is recommended. - A large amount of legacy functionality has been cleaned up, including deprecated custom
EVP_CIPHER,EVP_MD,EVP_PKEYmethods, fixed SSL/TLS version functions,c_rehash, andBIO_f_reliable(). - Old Apple build targets such as
darwin-i386anddarwin-ppchave also been removed. - On Windows, choosing between static/dynamic VC runtime linking is now supported.
Overall, this release marks a turning point that realigns OpenSSL around strengthened security, standards conformance, and legacy cleanup.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.