Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Security Management //

Encryption

8/15/2018
11:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

IETF Makes Transport Layer Security Version 1.3 Official

TLS 1.3 is now the industry standard for secure Internet connections via HTTPS.

The Internet Engineering Task Force (IETF) made version 1.3 of Transport Layer Security official on August 10. This is now the industry standard for secure Internet connections via HTTPS. After heated discussions for the last two years, TLS 1.3 is now finally supported in both the Chrome and Firefox browsers, and in Facebook.

The length of the discussion time for the changes made to the decades-old TLS 1.2 was most likely due to all the members involved trying to avoid problems that would haunt them at a later date. The Heartbleed attack, for example, was a problem in TLS 1.2 that arose from the design choices that went into its creation.

The crypto schemes used in TLS were drawn from what was good in the 90s, but we have learned much since then.

Financial and banking stakeholders are accustomed to being able to monitor TLS 1.2 communications as an anti-fraud measure. The structure of the changes in 1.3 would put an end to that visibility. The financial side advocated for a backdoor to be put into the protocol so that its members could continue such monitoring. In the end, they were outvoted.

Another area of contention was 0-RTT Resumption. This allows two parties that have previously established a TLS handshake to resume a session using older, previously established keys. If attackers got this information in some way they could spoof a connection. However, it was eventually agreed that any attacker would need physical access to a target in order to pull it off. This condition was thought sufficient to assure security, though only the future will truly tell if this conclusion is justified.

Connections will still fall back to TLS 1.2 if one end is not TLS 1.3-capable. But if an attacker attempts to force this kind of fallback, TLS 1.3 will detect it so that appropriate responses can be made.

What advantages will TLS 1.3 give the average user?

First, the kind of encryption to be used in the session is no longer a mishmash of encryption schemes that are potentially crackable due to sketchy implementation. There are only a few crypto choices allowed. The server provides an encryption key, the client provides a session key and, boom, the two go on to converse.

This scenario also means that a client can't trick a server into using an older, less secure means of encryption, which was possible under TLS 1.2. Since the overhead of handshaking needed to establish a connection goes way down, even on initial contact, the time to first display of content is reduced. Therefore, the overall latency of the system (and especially mobile systems) is greatly reduced.

Because there have been multiple intermediate versions of TLS 1.3; IE, Microsoft Edge, Opera and Safari do not yet fully support the protocol. That is sure to change rapidly now that it has been finalized.

HTTPS needed this upgrade to happen. It will only encourage a wider use of secured connections and provide security for the average user.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15106
PUBLISHED: 2020-08-05
In etcd before versions 3.3.23 and 3.4.10, a large slice causes panic in decodeRecord method. The size of a record is stored in the length field of a WAL file and no additional validation is done on this data. Therefore, it is possible to forge an extremely large frame size that can unintentionally ...
CVE-2020-16192
PUBLISHED: 2020-08-05
LimeSurvey 4.3.2 allows reflected XSS because application/controllers/LSBaseController.php lacks code to validate parameters.
CVE-2020-17364
PUBLISHED: 2020-08-05
USVN (aka User-friendly SVN) before 1.0.9 allows XSS via SVN logs.
CVE-2020-4481
PUBLISHED: 2020-08-05
IBM UrbanCode Deploy (UCD) 6.2.7.3, 6.2.7.4, 7.0.3.0, and 7.0.4.0 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 181848.
CVE-2020-5608
PUBLISHED: 2020-08-05
CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Basic) R4.01.00 to R6.07.00, B/M9000CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01 allows a remote unauthenticated attacker to bypass authentication and send altered c...