Google Chrome 72 Download 32-bit & 64-bit

After few betas and RCs (Release Candidates), final version of the most popular web browser, Google Chrome has finally released. Google Chrome 72 is available for Windows, Linux, Mac, and Android contains with a number of bug fixes security updates, and newer features.

Google Chrome has redesigned user interface to optimise the browser for touchscreen devices in tablet mode and added app shortcuts for Android apps that are now searchable in the launcher. In addition, Google Chrome 72 also allow files saved via Backup and Sync on Google Drive to be available in the Files app under the My Drive/Computers menu option. Here are the highlight changes for Google Chrome 72.

Google Chrome 72 changes include:

Remove HTTP-Based Public Key Pinning

HTTP-Based Public Key Pinning (HPKP) was intended to allow websites to send an HTTP header that pins one or more of the public keys present in the site’s certificate chain. Unfortunately, it has very low adoption, and although it provides security against certificate misissuance, it also creates risks of denial of service and hostile pinning. For these reasons, this feature is being removed.

Remove rendering FTP resources

FTP is a non-securable legacy protocol. When even the Linux kernel is migrating off of it, it’s time to move on. One step toward deprecation and removal is to deprecate rendering resources from FTP servers and instead download them. Chrome will still generate directory listings, but any non-directory listing will be downloaded rather than rendered in the browser.

Deprecate TLS 1.0 and TLS 1.1

TLS (Transport Layer Security) is the protocol which secures HTTPS. It has a long history stretching back to the nearly twenty-year-old TLS 1.0 and its even older predecessor, SSL. Both TLS 1.0 and 1.1 have a number of weaknesses.

• TLS 1.0 and 1.1 use MD5 and SHA-1, both weak hashes, in the transcript hash for the Finished message.
• TLS 1.0 and 1.1 use MD5 and SHA-1 in the server signature. (Note: this is not the signature in the certificate.)
• TLS 1.0 and 1.1 only support RC4 and CBC ciphers. RC4 is broken and has since been removed. TLS’s CBC mode construction is flawed and was vulnerable to attacks.
• TLS 1.0’s CBC ciphers additionally construct their initialization vectors incorrectly.
• TLS 1.0 is no longer PCI-DSS compliant.

Supporting TLS 1.2 is a prerequisite to avoiding the above problems. The TLS working group has deprecated TLS 1.0 and 1.1. Chrome has now also deprecated these protocols. Removal is expected in Chrome 81 (early 2020).

Picture-in-Picture (PiP) is now enabled by default

Picture-in-Picture (PiP) is now enabled by default in Chrome for Linux, Mac, and Windows. This allows you to watch videos in a floating window (always on top of other windows) so that you can keep an eye on what you’re watching while interacting with other sites, or applications. Note: the floating PiP window works when a web page is using the Picture-in-Picture API. For sites that doesn’t support the mentioned API, you can use the following extension.

Google Chrome 72 download links is available through Google Chrome platform, or just use the following direct download links to download setup installer of Google Chrome 72:

Google Chrome 72 32-bit

Google Chrome 72 64-bit

Google Chrome 72 supported in various languages.

You can share or follow us on Twitter, add us to your circle on Google+ or like our Facebook page to keep yourself updated on all the latest info from Microsoft, Google, Apple and the Web.