5 ms·

I can't believe on HN of all places people are using Chrome its malware-detecting-capabilities. Friendly reminder that EVERY REQUEST you make with it enabled, w

I can't believe on HN of all places people are using Chrome its malware-detecting-capabilities. Friendly reminder that EVERY REQUEST you make with it enabled, will be passed through Google its filters. You should turn all Google networking activities in your browser off. By default, there are at least five or so enabled which will happily send every request you make to Google. Some services even go as far as logging every keystroke you make.

korzun 13y ago
Don't forget your tinfoil hat on the way out.
maxerickson 13y ago
The majority of safe browsing checks happen client side (when a page matches the client side list, more info is retrieved from Google). It's covered in the appropriate section here: https://www.google.com/intl/en/chrome/browser/privacy/ https://www.google.com/intl/en/chrome/browser/privacy/ If you don't trust what they are saying there, you shouldn't be using Chrome at all.
nullymcnull 13y ago
> Friendly reminder that EVERY REQUEST you make with it enabled, will be passed through Google its filters. Perhaps you should actually fact-check such assumptions before passing them along as "friendly reminders"?
bla2 13y ago
That's not true. Safe browsing checks are done locally.
Matt_Cutts 13y ago
pearjuice, this simply isn't true. The way that Chrome does this is periodically downloads a file from Google. The file consists of hashes of known-dangerous web pages. When you visit a new URL, the URL is hashed locally and checked against the client-side list of hashes of known-bad pages. If there's no match, Chrome proceeds normally. Only if there is a hash collision does Chrome do more checking to see if the URL is safe. Here's more information in case you want to read more: https://code.google.com/p/google-safe-browsing/wiki/SafeBrowsingDesign https://code.google.com/p/google-safe-browsing/wiki/SafeBrow...
- pearjuice 13y ago
  It still holds regarding all the other Google activities in Chrome.

korzun 13y ago

Don't forget your tinfoil hat on the way out.

maxerickson 13y ago

The majority of safe browsing checks happen client side (when a page matches the client side list, more info is retrieved from Google). It's covered in the appropriate section here: https://www.google.com/intl/en/chrome/browser/privacy/ https://www.google.com/intl/en/chrome/browser/privacy/ If you don't trust what they are saying there, you shouldn't be using Chrome at all.

nullymcnull 13y ago

> Friendly reminder that EVERY REQUEST you make with it enabled, will be passed through Google its filters. Perhaps you should actually fact-check such assumptions before passing them along as "friendly reminders"?

bla2 13y ago

That's not true. Safe browsing checks are done locally.

Matt_Cutts 13y ago

pearjuice, this simply isn't true. The way that Chrome does this is periodically downloads a file from Google. The file consists of hashes of known-dangerous web pages. When you visit a new URL, the URL is hashed locally and checked against the client-side list of hashes of known-bad pages. If there's no match, Chrome proceeds normally. Only if there is a hash collision does Chrome do more checking to see if the URL is safe. Here's more information in case you want to read more: https://code.google.com/p/google-safe-browsing/wiki/SafeBrowsingDesign https://code.google.com/p/google-safe-browsing/wiki/SafeBrow...

pearjuice 13y ago
It still holds regarding all the other Google activities in Chrome.