Google released Chrome 72 stable version for Windows, Mac, and Linux. The Chrome 72.0.3626.81 comes with the fix for 58 security bugs and includes a number of improvements.

The release includes some major updates that includes Deprecate of the TLS 1.0 and 1.1 protocols and HTTP-Based Public Key Pinning.

Depreciation of TLS 1.0, TLS 1.1 and HPKP

Starting from Google Chrome 72, the chrome has taken the first step in removing the support for TLS 1.0 and TLS 1.1 protocols. During the depreciation period if any sites using TLS 1.0 and 1.1 shows a warning in browser devtools.

After the depreciation period, in 2020, if any sites using TLS 1.0 and 1.1 will fail to connect with the and the website administrators need to upgraded with TLS 1.2.

HPKP support was removed, it is a security feature that prevents the misissuance of the certificate but the adoption rate is very low.

Chrome to remove the support for rendering resources from FTP servers and instead allows users to download them directly.

Popups during page unload are blocked, “the popup blocker already prohibited this, but now it is prohibited whether or not the popup blocker is enabled.”

Chrome Web Authentication API which adds support for communicating with external devices over BLE, including a UI to guide users in pairing and using their devices for two-factor authentication.

Chrome 72 comes with a fix for 58 security bugs that identified from internal audits, fuzzing and other initiatives such as AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

Firefox 65.0 released few hours before the Chrome update, the Firefox updates fixes several security vulnerabilities along with various new futures including video streaming experience, updated language preference etc.

GBHackers on security is a Cyber Security platform that covers daily Cyber Security News, Hacking News, Technology updates and Kali Linux tutorials. Our mission is to keep the community up to date with happenings in the Cyber World.