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
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
4 Security Tips as the July 15 Tax-Day Extension Draws Near
Shane Buckley, President & Chief Operating Officer, Gigamon,  7/10/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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 Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15105
PUBLISHED: 2020-07-10
Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authenticati...
CVE-2020-11061
PUBLISHED: 2020-07-10
In Bareos Director less than or equal to 16.2.10, 17.2.9, 18.2.8, and 19.2.7, a heap overflow allows a malicious client to corrupt the director's memory via oversized digest strings sent during initialization of a verify job. Disabling verify jobs mitigates the problem. This issue is also patched in...
CVE-2020-4042
PUBLISHED: 2020-07-10
Bareos before version 19.2.8 and earlier allows a malicious client to communicate with the director without knowledge of the shared secret if the director allows client initiated connection and connects to the client itself. The malicious client can replay the Bareos director's cram-md5 challenge to...
CVE-2020-11081
PUBLISHED: 2020-07-10
osquery before version 4.4.0 enables a priviledge escalation vulnerability. If a Window system is configured with a PATH that contains a user-writable directory then a local user may write a zlib1.dll DLL, which osquery will attempt to load. Since osquery runs with elevated privileges this enables l...
CVE-2020-6114
PUBLISHED: 2020-07-10
An exploitable SQL injection vulnerability exists in the Admin Reports functionality of Glacies IceHRM v26.6.0.OS (Commit bb274de1751ffb9d09482fd2538f9950a94c510a) . A specially crafted HTTP request can cause SQL injection. An attacker can make an authenticated HTTP request to trigger this vulnerabi...