Google released it Chrome 86 on stable channel and brought many security enhancements and new APIs for developers. With regard to safety, many of the improvements have to do with password-related upgrades.
Password-checking also comes in mobile versions
In December 2019, when Google released Chrome 79, it introduced a new feature called "Password Checkup“. This function takes the codes access of user and checks if they have leaked to Internet during violations data into a Companies.
Easy change of violated passwords
In addition, the "Safety Check" itself receives some updates to enhance security. Starting with Chrome 86, "Safety Check" will support the ".well-known / change-password" standard.
It's a W3C standard which allows websites to specify the URL that users can use to change passwords. This means that users They can simply click a button in the Chrome password settings and go directly to this page to change their password.
Authentication with biometric data in iOS
Google is also expanding its functionality "touch-to-fill”On iOS. This feature was only released for Android devices in July. The touch-to-fill was created to prevent passwords from being automatically filled in Phishing sites. In addition, it allows users to fill in passwords on login forms by simply tapping their finger, without having to look for the right credentials.
With Chrome 86, this feature will also be available on iOS, where to enhance security, users will be asked to perform biometric authentication before filling in passwords automatically. This includes using Face ID, Touch ID or their phone password as a last resort.
More safe browsing and on mobile versions
The "Enhanced Safe Browsing", A security function used for phishing and malware detection, extends to Chrome versions of mobile. This feature was released with Chrome 83 in May 2020, but only on desktop versions.
Warnings for unsafe forms
Such forms, according to Google, are those hosted on encrypted HTTPS pages, but which secretly submit data through non-encrypted HTTP functions.
Warnings for unsafe downloads
Google will also display warnings when downloading files via HTTP from pages displayed as HTTPS.
In Chrome 86, the executable and archive files are excluded by default and Chrome displays warnings for downloading office-related documents.
Start of its abolition FTP
With Chrome 86, Google will gradually begin to remove support for FTP links from Chrome:
Chrome 86: FTP is still enabled by default for most users, but is disabled for pre-released channels (Canary and Beta) and will be turned off experimentally for 1% of stable version users. In this version users will be able to activate it again.
Chrome 87: FTP support will be disabled by default for 50% of users, but can be turned on again.
Chrome 88: FTP support will be disabled.
The above are some of the most basic security enhancements offered by the stable version of Chrome 86, as we read on ZDNet.