Google this week released Chrome 80 to the stable channel with 56 vulnerability patches and various other improvements to user security.
To better protect from cross-site request forgery (CSRF) attacks, Chrome 80 will enforce a new secure-by-default cookie classification system, where only cookies set as SameSite=None; Secure will be available in third-party contexts, as long as they are accessed from secure connections.
The change, initially announced in May 2019, is set to enter into effect later this month, when Chrome will treat cookies that have no declared SameSite value as SameSite=Lax cookies. The changes will initially be seen by only a small set of users.
The new browser release also deprecates FTP support, since the implementation does not support secure connections or proxies, and because usage is low. Google plans to disable FTP by default in the next Chrome iteration and will completely remove support for it in Chrome 82.
Chrome 80, which comes with version 8 of the V8 JavaScript engine, autoupdates mixed audio and video resources to HTTPS and blocks them if they fail to load over a secure connection. Mixed images are still allowed to load, but the browser will display a “Not Secure” warning in the omnibox.
As Google announced in October last year, Chrome 81 will autoupdate mixed images to HTTPS, or will block them if they fail to load over a secure connection.
Google has been advocating for the adoption of HTTPS for a long time, and the autoupdating of mixed content is only one of t ..
Support the originator by clicking the read the rest link below.
