Google released Chrome version 92 with fixes for several high-severity security issues and a host of new privacy features.
First, through MacRumors, Chrome for iOS now allows users to lock their incognito tabs with Touch ID, FaceID, and a password. This can be enabled in the Settings> Privacy> Lock private browsing tabs.
Once locked, private browsing tabs will not be visible after exiting and reopening Chrome until the user authenticates.
SEE: Checklist for managing and troubleshooting Android devices (TechRepublic Premium)
Google also makes it easier to control which sites can access hardware features like microphone, location, and camera, Google noted in a blog post. To see the sites to which you have previously granted permissions, you tap the lock icon in the address bar. The panel allows you to enable or disable access to these features. In a future version, Chrome will have the option to remove the site from browsing history.
In this release, Google has also fleshed out its Chrome actions, a feature that allows you to perform tasks with fewer keystrokes. Typing “change passwords” or “delete history” provides a shortcut to these settings.
New actions include “security check” to check password security and scan for malicious extensions. Typing “manage security settings” or “manage sync” will open the appropriate controls.
As Google explained earlier, site isolation changes the architecture of Chrome to limit each rendering process to documents from a single site.
“Site Isolation will now cover a wider range of sites, as well as extensions, and all of this comes with changes that improve Chrome’s speed,” Google noted in a blog post.
Google has also boosted Chrome’s phishing protection with Image Processing, where it compares the color profile of a visited page with the color profiles of current pages.
“If the site matches a known phishing site, Chrome warns you to protect your personal information and prevent you from exposing your credentials,” Google noted in the Chromium blog.
SEE: What is a software developer? Everything you need to know about the role of the programmer and its evolution
Google has noted that this technique can place a heavy load on CPU resources, which is why they have devised methods to make it more efficient.
“On average, users will get their phishing classification results after 100 milliseconds, instead of 1.8 seconds,” he added.
Those seconds count when the goal of protection is to prevent people from entering their credentials on a phishing page.
Google’s optimizations resulted in a “nearly 1.2% reduction in total CPU time used by all Chrome rendering and utility processes,” he said. Finally, Google fixed 35 security flaws in versions of Chrome prior to version 92. Flaws corrected.