Should Google "Safe Browsing" be Enabled?
#60 opened on Jun 24, 2016
Description
Discussion: Currently I'm setting this configuration to be turned on by default in all Google Chrome profiles with a "recommended" level of confidence. I'd like other opinions here on whether it's more good or bad, however.
https://en.wikipedia.org/wiki/Google_Safe_Browsing
Google maintains the Safe Browsing Lookup API, which has a privacy drawback: "The URLs to be looked up are not hashed so the server knows which URLs the API users have looked up". The Safe Browsing API v3, on the other hand, compares 32-bit hash prefixes of the URL to preserve privacy.[7][8] The Firefox and Safari browsers use the latter.[9]
Safe Browsing also stores a mandatory preferences cookie on the computer[10] which the US National Security Agency allegedly uses to identify individual computers for purposes of exploitation.[11]
Google Safe Browsing "conducts client-side checks. If a website looks suspicious, it sends a subset of likely phishing and social engineering terms found on the page to Google to obtain additional information available from Google's servers on whether the website should be considered malicious". Logs, "including an IP address and one or more cookies" are kept for two weeks. They are "tied to the other Safe Browsing requests made from the same device."[12]