OpenSSL 4.1.0 arrived as a feature release on October 23, bringing a mix of new protocol support, architecture-specific performance improvements, and developer tooling changes. This release is not presented as a standalone security patch; instead it expands functionality with notable additions such as DTLS 1.3 support while documenting several known issues that teams should evaluate before upgrading.
What’s new in OpenSSL 4.1.0
OpenSSL 4.1.0 adds Datagram Transport Layer Security (DTLS) 1.3 support to its SSL listener API, along with GREASE support, the IKEv2 key derivation function, and initial support for the Elbrus2000 processor architecture. The release also includes optimizations aimed at improving cryptographic performance on specific platforms and instruction sets. The project’s release notes identify these as feature enhancements rather than security-only fixes.
DTLS 1.3: why it matters
DTLS 1.3, defined in RFC 9147, extends the guarantees of TLS 1.3 to unreliable transports like UDP. It preserves confidentiality and integrity while maintaining the unordered, lossy behavior of datagram transports—making DTLS useful for latency-sensitive applications such as gaming and certain streaming scenarios. With DTLS now available in OpenSSL’s listener API, developers building UDP-based secure services can adopt the newer protocol, but must account for DTLS-specific behavior around packet ordering, replay protection, and handling of lost handshake messages.
Performance and architecture support
This release contains a range of platform- and instruction-set-specific performance improvements. On ppc64le systems, ML-DSA and ML-KEM number theoretic transform operations were improved. On x86_64, OpenSSL added optimized ML-DSA operations as well as AVX-512 SHAKE processing for ML-DSA. There are also AVX-512 and VAES improvements affecting AES-CBC decryption. The release notes do not include benchmark figures, so teams should measure impact in their own environments rather than relying on hypothetical gains.
Developer-facing changes and compatibility
Several build- and dependency-related changes will affect developers and packagers. The tsget utility now depends on Net::Curl::Easy, replacing the previously abandoned WWW::Curl::Easy dependency; teams that use tsget must install the new dependency prior to upgrading. OpenSSL dropped Windows-on-Itanium and Windows CE build targets, while adding targets that address shortcomings in MSVC 2013’s C99 support. Configuration options no-ecdsa and no-ecdh were removed because they did not actually disable those implementations; to turn off elliptic curve support, use no-ec instead.
Documented DTLS issues to review
The release notes document four known DTLS-related problems that can affect application behavior:
- A DTLS 1.3 KeyUpdate received by a listener can cause pending post-handshake records to be removed from the retransmission buffer. If the original packets were lost, those records (for example, session tickets) may not be resent. A fix is planned for a future release.
- Listener error handling has limitations: a permanent receive failure may be surfaced as SSL_ERROR_WANT_READ, which can leave applications waiting unexpectedly.
- A retryable write failure may be reported as SSL_ERROR_SYSCALL, potentially causing applications to close connections that are still usable.
- Early client acknowledgments following packet loss can trigger handshake failures.
Practical guidance for deployment
Treat OpenSSL 4.1.0 as a feature upgrade: evaluate the new capabilities (particularly DTLS 1.3) in a test environment, run application-specific scenarios that exercise packet loss and retransmission behavior, and verify build dependencies and target support for your toolchain. Pay attention to the documented DTLS issues and plan for any interim workarounds until fixes are released. Finally, confirm whether disabling elliptic-curve functionality requires the no-ec option in your builds.
Conclusion
OpenSSL 4.1.0 advances the library with DTLS 1.3 and a suite of platform optimizations that will matter most to teams using datagram transports and those targeting the newly supported architectures or instruction sets. Because the release also lists several DTLS caveats and compatibility changes, careful testing and planning will be essential for safe adoption.
Licensed under CC BY-ND 4.0 International