[Pkg-chromium-maint] Bug#783999: Should not disable "safe browsing" mechanism

Josh Triplett josh at joshtriplett.org
Sun Jun 21 01:54:17 UTC 2015


On Sat, Jun 20, 2015 at 09:39:08PM -0400, Michael Gilbert wrote:
> >>From the changelog:
> >
> >  [ Shawn Landden ]
> >    * Supress first run welcome page.
> >    * Turn off safebrowsing.
> >    * Turn off pinging Google on 404 and other HTTP errors.
> 
> That change disables the setting by default, but the user can still
> manually go into the preferences and enable it.  My opinion is that
> this is the correct default behavior.

As noted in my original mail, the safe browsing mechanism does not
consult a third-party service for every URL, but rather checks URLs
against a periodically-updated filter.  See
https://www.google.com/chrome/browser/privacy/whitepaper.html#malware
for more details.  So, again: why?  What is the purpose of disabling
this user protection mechanism by default?

- Josh Triplett



More information about the Pkg-chromium-maint mailing list