Because it is worth making this clear from the start. This is a test version, not suitable for production, and the release date of the final 4.1 is not even set.
Five months after 4.0 comes the first alpha
The final 4.0 came out on April 14 with a major new feature: the arrival of Encrypted Client Hello (known as ECH), more post-quantum cryptography and a cleanup of old protocols, according to the project announced. It was a transition version with a near expiry date. The project will maintain it until May 14, 2027, while the veteran 3.5 remains as the long-term support (LTS) branch.
Since then, maintenance has not stopped. At the end of August came 4.0.2 with a moderate-severity patch that prevented excessive memory consumption when processing DTLS records from future epochs. Alpha 1 of 4.1 builds on that already hardened base and adds genuinely new functionality.
The official changelog confirms the menu. DTLS 1.3 support per RFC 9147, with its usage guide included. GREASE support per RFC 8701, enabled with the SSL_OP_GREASE option and with a -grease flag for the s_clienttool. And initial support for Russian Elbrus 2000 processors, plus the definitive retirement of Itanium and Windows CE on the Windows side.
Three pieces deserve a careful explanation. Let us go through them.
DTLS 1.3, encryption for an Internet that does not wait
TLS, the padlock protocol, runs over TCP, which guarantees that every packet arrives in order. But there is a whole world that does not use TCP. Video calls, voice over IP, many VPNs, online games and Internet of Things sensors speak UDP, where packets can be lost or arrive out of order. For them there is DTLS, the twin of TLS adapted to datagrams.
The problem is that this twin had been anchored in the past for years. OpenSSL supported DTLS 1.0 and 1.2, but version 1.3, published as a standard in April 2022, was still missing. Four years later, the alpha finally brings it.
FreeBSD ports AMD's ROCm software for HPC and AI on GPU
DTLS with vitamins
And it brings a lot. The initial handshake between computers on the Internet goes from two round trips to just one, so connecting is faster. Only modern ciphers with built-in authentication are allowed; everything prior remains there for compatibility until it is retired, but the default protocol is secure by design.
In addition, each session uses ephemeral keys that are destroyed when it ends, so stealing the server key tomorrow does not allow decrypting what was recorded today. And there is native room for the post-quantum cryptography that will withstand future quantum computers.
There are finer details for hostile networks. A cookie mechanism forces the client to prove its address before the server invests work, which curbs denial-of-service attacks that are so easy on UDP. Large messages are fragmented and reassembled without relying on the operating system. And sessions can be resumed with data from the first packet, the so-called 0-RTT, for minimal latency.
Security and speed, finally together. And for programmers there is an extra gift. The OpenSSL listen API now handles DTLS in addition to QUIC, separating incoming datagrams by client in an orderly way. Less handcrafted code in each server, greater security and integration in development.
GREASE, or the WD-40 of the Internet
The second piece has the most fun name in recent cryptography and its name is GREASE. This protocol responds to an almost philosophical problem: TLS is designed to evolve, with capability lists where the client offers and the server chooses, ignoring what it does not know.
But some programs have bugs and break the connection when faced with unknown values. Since everything works with current clients, the bug spreads silently. Years later, when a genuinely new capability arrives, it becomes impossible to deploy, and you have to get your hands dirty and make "fixes on top of fixes" to solve it.
And there is plenty to cut into there. In February 2017, Google enabled TLS 1.3 in Chrome 56 and thousands of machines behind Blue Coat proxies were left without Internet. The intermediate devices (the proxies) did not tolerate the new thing and cut the connection. Google had to back down, disguising TLS 1.3 so it looked like 1.2 and negotiating with each manufacturer. The worst "fixes on top of fixes" you can imagine, and it hurts, because that still has not been able to be removed.
"Either you do it right, or you do nothing"
However, the answer to this problem was standardized in January 2020 as RFC 8701, by David Benjamin. Many know the solution as "cheeky" but "fun and functional".
Why? Because the client occasionally sends meaningless random values, with the pattern 0x?A?A, in its lists of ciphers, versions and extensions. Well-made programs ignore them and move on (services do not fall, and everything continues on its way).
But if the program is badly written, then your service ends up dying and everything falls apart. Yes, the encryption protocol itself can bring down a service, if the service is badly programmed. Cloudflare summed it up with a perfect image: "GREASE is like the WD-40 of the Internet". It seems there is nothing more fun in computing than watching services die because they are badly made, a guilty pleasure.
That said, OpenSSL took a while to join that line. The request had been open since 2019 and has been closed by an external contribution that follows the model of BoringSSL, Google's library. For now it works on the client side and can already be tested by hand with openssl s_client -grease.
Faro Santander: a zero point to see how the future ages
AVX-512 at the service of the post-quantum era
The third piece looks at the processor. Modern chips include AVX-512 instructions capable of operating with giant 512-bit registers. Used well, they allow four cryptographic operations where previously only one fit. OpenSSL was already taking advantage of them in several algorithms and 4.1 expands coverage on two fronts.
The first is post-quantum cryptography. ML-DSA, the digital signature standard that NIST published in August 2024 based on the CRYSTALS-Dilithium scheme, devours operations of the SHAKE function. The alpha debuts an AVX-512 path that runs four SHAKE in parallel, in addition to accelerating the algorithm's mathematical transforms in AVX2 and bringing equivalent optimizations to PowerPC and s390x mainframes.
The second front is more down to earth. AES-CBC decryption, still omnipresent in private networks and legacy systems, also gets its share of AVX-512.
What this means for your equipment. Every secure connection negotiates keys, verifies signatures and encrypts data, and all of that costs CPU. On a server with thousands of connections per second, making those operations cheaper translates into lower latency, more connections per machine and a lower electricity bill. On your laptop, in handshakes you do not even notice, or well, perhaps a little in the temperature spike, since AVX-512 is like throwing gasoline on the fire, it makes everything explode and burn.
Time to jettison ballast
Like every major version, OpenSSL 4.1 leaves corpses. In this version, the build targets for Itanium on Windows and for Windows CE disappear, two platforms that belong in the museum of paleolithic computing wonders. The configuration options no-ecdsa and no-ecdhare removed, which in reality did not disable anything and only generated confusion. Now you have to use no-ec to do without the elliptic curve, although it is not the best idea, unless you want to give up some of the best security algorithms for the Internet.
But just as ballast is dropped, new things fall in, some of them rather exotic. The best example is initial support for Elbrus 2000, the Russian processor made for administration and defense. That is curious, because the Elbrus 2000 are made in Taiwan (by TSMC), since Russia has no capacity to produce anything more advanced than 90 nm, technology from 25 years ago.
In addition, 4.1 promises support for IKEv2 KDF, the key derivation mechanism of IPsec VPNs, plus a fix in the verification of DSA certificates with SHA-384 and SHA-512. In any case, you will have to wait for the final version to install anything, but the direction is unmistakable. The Internet also patches itself.
5 cybersecurity tools on Linux you must master