Chrome Development team is developing new browser security policies that will seek to reduce unsafe downloads. In particular, Google is trying to try blocking high-risk files, such as executables.
The plan is to start dealing with some downloads that start in a secure context as "mixed content" and go to block them. This means that if uploading files comes from a HTTPS-based site, it means a secure context, but if the file from a site still uses HTTP, Chrome will treat it as a risk and block it.
The goal is clear and simple: reducing insecure downloads and reducing their impact on users of ROM, which is so far one of the largest operations by users who surf the web because of the dominance of the Google browser market.
The files that will be affected by this change are those files that are most often used to spread malicious software: EXE executables. In Windows, and dmg for Mac, and CRX accessories. , And many compressed file types (zip, gzip, bzip, tar, rar, and 7z).
This initiative aims to protect the user in more deceptive situations that users experience from sites that use HTTP.
The plan is to start dealing with some downloads that start in a secure context as "mixed content" and go to block them. This means that if uploading files comes from a HTTPS-based site, it means a secure context, but if the file from a site still uses HTTP, Chrome will treat it as a risk and block it.
The goal is clear and simple: reducing insecure downloads and reducing their impact on users of ROM, which is so far one of the largest operations by users who surf the web because of the dominance of the Google browser market.
The files that will be affected by this change are those files that are most often used to spread malicious software: EXE executables. In Windows, and dmg for Mac, and CRX accessories. , And many compressed file types (zip, gzip, bzip, tar, rar, and 7z).
This initiative aims to protect the user in more deceptive situations that users experience from sites that use HTTP.
0 Comments