Shulou(Shulou.com)06/01 Report--

Hours after Mozilla released Firefox 65, Google also released the latest Chrome 72 and provided newer versions for Windows, Mac, Linux and Android users.

Note: Google Chrome has added download driver protection.

Although Google's changes in Chrome UI and UX (user interface and user interaction) have had a big impact on users in the past 3-4 versions, today's version changes have a greater impact on the browser's underlying Web APIs and protocols.

Of all the changes, Chrome 72 has three important updates that users need to know. The most important of these is the complete removal of support for the HTTP-based Public key fixed (HPKP) standard (RCF 7469).

Google announced its long-term plan for HPKP in October 2017 and abandoned HPKP for the first time in Chrome 65, which was released in March 2018.

Because it has been discarded, Chrome displays an error on the development console of the site owner. Now that it is deprecated, Chrome no longer supports websites to use HPKP and refuses to fix the public key. Fortunately, this doesn't affect too many sites, because HPKP is troublesome to implement, and only a few sites have ever used it.

Website owners who currently support HPKP should probably stop. As the most popular browser in the world, Chrome will no longer support public key fixing.

The second major change in the Chrome 72 release is that it does not render any resources loaded through the FTP protocol.

Chrome continues to display a list of FTP directories, but when a Web site loads an image or JavaScript file hosted on a FTP link instead of rendering the image or running the file, Chrome prompts the user to download it.

The third major change in Chrome 72 is that outdated TLS 1.0 and TLS 1.1 standards are no longer supported. This move is only the first step taken by Chrome 81 to withdraw support for these two standards. Chrome 81 is scheduled to be released in early 2020.

Google announced these plans last year, along with Apple, Microsoft and Mozilla. Apple, Microsoft and Mozilla say they will execute these plans on their respective browsers.

Chrome 72 no longer supports TLS 1.0 and TLS 1.1, which means that when a user visits a HTTPS site with a legacy TLS 1.0 or 1.1 certificate, Chrome displays an error in the developer console, but does not prevent the user from accessing the site. Starting with Chrome 81, user access will be blocked.

[from SSL China]

The current new version of Chrome is 72.0.3626.81. Windows, Mac, Linux, and Android users can install updates using Chrome's built-in updater. The complete Chrome 71 modification log is shown here.

In Chrome 72, Google fixed 58 security vulnerabilities. Two blog posts from the Chromium and Google Developers teams detail the developer-centric features of Chrome 72.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.