OpenSSL alpha adds TLS 1.3 support

Shambling corpse of ancient, shoddy, buggy, crypto shoved towards the grave

Developers working with OpenSSL can finally start to work with TLS 1.3, thanks to the alpha version of OpenSSL 1.1.1 that landed yesterday.

Getting TLS 1.3 into users hands and working with infrastructure has been a long, slow process: the first version of its Internet-Draft dates back to April 2014, it reached version 23 in January of this year, and there's still work to come.

As developer Logan Velvindron explained to us last October, so-called “middleboxes” can still break when confronted with a TLS 1.3 session. Tests conducted by the IETF working group in December 2017 showed around a 3.25 percent failure rate of TLS 1.3 client connections.

The OpenSSL developers say version 1.1.1 is binary and API compatible with the current version, 1.1.0, so it should act as a “drop in” replacement to let developers use TLS 1.3.

Is anything that simple? Of course not – this is an alpha after all. OpenSSL's announcement says that for now version 1.1.1 “should not be used for security critical purposes”.

The big change from TLS 1.2 to TLS 1.3 is that the new version will deprecate old cryptographic algorithms entirely, instead of allowing them to be configured into an operational system.

Cloudflare blogged in September 2016 (when the optimistic hope was that the spec would be finalised by December 2016), that there's an extensive list of potential holes that the new TLS version will bury forever.

As that post explained, RSA key transport (which lacks forward secrecy), CBC mode ciphers (BEAST attacks, anyone?), the insecure RC4 stream cipher and the ancient SHA-1, a Diffie-Hellman slip up, and the FREAK/Logjam bugs are all deprecated, rather than hanging around awaiting a developer's configuration error.

There's more than TLS 1.3 in the OpenSSL release. Other features highlighted by the dev team include implementing SHA3 and multi-prime RSA; support for the SipHash set of pseudorandom functions; and a “grand redesign” of the OpenSSL random number generator. ®

Similar topics

Other stories you might like

  • A peek into Gigabyte's GPU Arm for AI, HPC shops
    High-performance platform choices are going beyond the ubiquitous x86 standard

    Arm-based servers continue to gain momentum with Gigabyte Technology introducing a system based on Ampere's Altra processors paired with Nvidia A100 GPUs, aimed at demanding workloads such as AI training and high-performance compute (HPC) applications.

    The G492-PD0 runs either an Ampere Altra or Altra Max processor, the latter delivering 128 64-bit cores that are compatible with the Armv8.2 architecture.

    It supports 16 DDR4 DIMM slots, which would be enough space for up to 4TB of memory if all slots were filled with 256GB memory modules. The chassis also has space for no fewer than eight Nvidia A100 GPUs, which would make for a costly but very powerful system for those workloads that benefit from GPU acceleration.

    Continue reading
  • GitLab version 15 goes big on visibility and observability
    GitOps fans can take a spin on the free tier for pull-based deployment

    One-stop DevOps shop GitLab has announced version 15 of its platform, hot on the heels of pull-based GitOps turning up on the platform's free tier.

    Version 15.0 marks the arrival of GitLab's next major iteration and attention this time around has turned to visibility and observability – hardly surprising considering the acquisition of OpsTrace as 2021 drew to a close, as well as workflow automation, security and compliance.

    GitLab puts out monthly releases –  hitting 15.1 on June 22 –  and we spoke to the company's senior director of Product, Kenny Johnston, at the recent Kubecon EU event, about what will be added to version 15 as time goes by. During a chat with the company's senior director of Product, Kenny Johnston, at the recent Kubecon EU event, The Register was told that this was more where dollars were being invested into the product.

    Continue reading
  • To multicloud, or not: Former PayPal head engineer weighs in
    Not everyone needs it, but those who do need to consider 3 things, says Asim Razzaq

    The push is on to get every enterprise thinking they're missing out on the next big thing if they don't adopt a multicloud strategy.

    That shove in the multicloud direction appears to be working. More than 75 percent of businesses are now using multiple cloud providers, according to Gartner. That includes some big companies, like Boeing, which recently chose to spread its bets across AWS, Google Cloud and Azure as it continues to eliminate old legacy systems. 

    There are plenty of reasons to choose to go with multiple cloud providers, but Asim Razzaq, CEO and founder at cloud cost management company Yotascale, told The Register that choosing whether or not to invest in a multicloud architecture all comes down to three things: How many different compute needs a business has, budget, and the need for redundancy. 

    Continue reading

Biting the hand that feeds IT © 1998–2022