Social Items



The successor to SSL (Secure Socket Layer) encryption protocol, Transport layer Security (TLS) serves to secure communications between the browser and destination server so as to thwart hackers from intercepting and reading the data.

While the Internet Engineering Task Force (IETF) has recommended that older TLS versions 1.0 and 1.1 should be discontinued, given that several aspects of the architecture are neither as strong or robust to cover the security requirements of the Internet today.

And the specific problems with TLS 1.0 that require immediate action, remains that TLS 1.0 does not support modern cryptographic algorithms, which poses some risks to our valuable information, such as log-on credentials and credit card numbers.

As a result, both TLS 1.0 and 1.1 are now obsolete and to be replaced by the later newer versions 1.2 and 1.3, with TLS 1.3 as the most recent update, haven been released in August by the Internet Engineering Task Force (IETF), and the major browsers haven introduced support for the draft specification of TLS 1.3.

The four biggest browsers, Chrome, Firefox, IE or Edge and Safari have all set the timeline when they will drop support for the TLS (Transport Layer Security) 1.0 and 1.1 encryption protocols.

Google Chrome will start deprecating the protocols starting from Chrome 72, which is expected to ship in January 2019 with warnings in the DevTools console. And support for TLS 1.0 and 1.1 will eventually be dropped with Chrome 81, slated for release around March 2020.

And Firefox will disable support for TLS 1.0 and TLS 1.1 starting in March of 2020, with changes appearing in pre-release versions of Firefox (Beta, Developer Edition, and Nightly) earlier than March 2020.

Apple on its part will remove support for TLS 1.0 and 1.1 from Safari in March 2020 via updates to macOS and iOS. Also other browsers have made similar announcements, including Microsoft Edge all setting almost same timeline and plan to make the same changes.

Timeline for the major browsers ending support for TLS 1.0 and 1.1 encryption protocols



The successor to SSL (Secure Socket Layer) encryption protocol, Transport layer Security (TLS) serves to secure communications between the browser and destination server so as to thwart hackers from intercepting and reading the data.

While the Internet Engineering Task Force (IETF) has recommended that older TLS versions 1.0 and 1.1 should be discontinued, given that several aspects of the architecture are neither as strong or robust to cover the security requirements of the Internet today.

And the specific problems with TLS 1.0 that require immediate action, remains that TLS 1.0 does not support modern cryptographic algorithms, which poses some risks to our valuable information, such as log-on credentials and credit card numbers.

As a result, both TLS 1.0 and 1.1 are now obsolete and to be replaced by the later newer versions 1.2 and 1.3, with TLS 1.3 as the most recent update, haven been released in August by the Internet Engineering Task Force (IETF), and the major browsers haven introduced support for the draft specification of TLS 1.3.

The four biggest browsers, Chrome, Firefox, IE or Edge and Safari have all set the timeline when they will drop support for the TLS (Transport Layer Security) 1.0 and 1.1 encryption protocols.

Google Chrome will start deprecating the protocols starting from Chrome 72, which is expected to ship in January 2019 with warnings in the DevTools console. And support for TLS 1.0 and 1.1 will eventually be dropped with Chrome 81, slated for release around March 2020.

And Firefox will disable support for TLS 1.0 and TLS 1.1 starting in March of 2020, with changes appearing in pre-release versions of Firefox (Beta, Developer Edition, and Nightly) earlier than March 2020.

Apple on its part will remove support for TLS 1.0 and 1.1 from Safari in March 2020 via updates to macOS and iOS. Also other browsers have made similar announcements, including Microsoft Edge all setting almost same timeline and plan to make the same changes.
Internet Security

No comments

Subscribe to: Post Comments (Atom)