To do this, Chrome checks the URL of executables you download against a whitelist of known-good URLs maintained locally on your computer and updated regularly. Chrome trusts executables that match URLs in the whitelist, and also those downloaded from the local network, or signed by a trusted authority. Other executables are presumed unsafe, and Chrome will send to Google information needed to help determine whether the download is potentially harmful, including some or all of the following: information about the full URL of the site or file download, all related referrers and redirects, code signing certificates, file hashes, and file header information. Chrome may then show a warning like the one pictured above.
If Chrome suspects that your settings have been tampered with, Chrome will report the URL of the last downloaded executable and information about the nature of the unexpected changes to the Safe Browsing service.
Where possible, Chrome aids with the detection and removal of software that changes Chrome's settings without your approval. To do so, Chrome scans your computer periodically for the sole purpose of detecting potentially unwanted software. If such software is detected, Chrome may offer you the option to use the software removal tool to remove it.
For some downloads, Chrome may ask to send the suspicious file to Google to improve the quality of download protection. Once opted-in, this data will be sent every time such a file is encountered. You can disable this opt-in at any time in the Chrome settings page.
For all Safe Browsing requests, Google logs the transferred data in its raw form for up to two weeks. Google collects standard log information in connection with Safe Browsing requests, including an IP address and one or more cookies. After at most two weeks, Safe Browsing will delete the raw logs, storing only calculated data in an anonymized form which does not include your IP addresses or cookies. Additionally, Safe Browsing requests won’t be associated with your Google Account. They are however, tied to the other Safe Browsing requests made from the same device.
To do this, Chrome checks the URL of executables you download against a whitelist of known-good URLs maintained locally on your computer and updated regularly. Chrome trusts executables that match URLs in the whitelist, and also those downloaded from the local network, or signed by a trusted authority. Other executables are presumed unsafe, and Chrome will send to Google information needed to help determine whether the download is potentially harmful, including some or all of the following: information about the full URL of the site or file download, all related referrers and redirects, code signing certificates, file hashes, and file header information. Chrome may then show a warning like the one pictured above.If Chrome suspects that your settings have been tampered with, Chrome will report the URL of the last downloaded executable and information about the nature of the unexpected changes to the Safe Browsing service.Where possible, Chrome aids with the detection and removal of software that changes Chrome's settings without your approval. To do so, Chrome scans your computer periodically for the sole purpose of detecting potentially unwanted software. If such software is detected, Chrome may offer you the option to use the software removal tool to remove it.For some downloads, Chrome may ask to send the suspicious file to Google to improve the quality of download protection. Once opted-in, this data will be sent every time such a file is encountered. You can disable this opt-in at any time in the Chrome settings page.For all Safe Browsing requests, Google logs the transferred data in its raw form for up to two weeks. Google collects standard log information in connection with Safe Browsing requests, including an IP address and one or more cookies. After at most two weeks, Safe Browsing will delete the raw logs, storing only calculated data in an anonymized form which does not include your IP addresses or cookies. Additionally, Safe Browsing requests won’t be associated with your Google Account. They are however, tied to the other Safe Browsing requests made from the same device.
正在翻譯中..