Your message dated Sat, 20 Jun 2015 21:39:08 -0400 with message-id <CANTw=MOeo0aJKWkq-gzzWs57GMzPe7ArnWLe=uN3AaO3C=w...@mail.gmail.com> and subject line re: Should not disable "safe browsing" mechanism has caused the Debian Bug report #783999, regarding Should not disable "safe browsing" mechanism to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 783999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783999 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: chromium Version: 42.0.2311.135-1 Severity: important >From the changelog: [ Shawn Landden ] * Supress first run welcome page. * Turn off safebrowsing. * Turn off pinging Google on 404 and other HTTP errors. Judging by the changes it was grouped with, I'm guessing that this change was made for privacy reasons. However, to the best of my knowledge, the mechanism used to implement safe browsing does *not* check individual URLs against a server (at Google or elsewhere); instead, it downloads a filter and checks URLs against that. - Josh Triplett -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii libasound2 1.0.28-1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libcap2 1:2.24-8 ii libcups2 1.7.5-11 ii libdbus-1-3 1.8.16-1 ii libexpat1 2.1.0-6+b3 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgnome-keyring0 3.12.0-1+b1 ii libgtk2.0-0 2.24.25-3 ii libharfbuzz0b 0.9.35-2 ii libjpeg62-turbo 1:1.3.1-12 ii libnspr4 2:4.10.8-1 ii libnspr4-0d 2:4.10.8-1 ii libnss3 2:3.17.2-1.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpci3 1:3.2.1-3 ii libspeechd2 0.8-7 ii libspeex1 1.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1.1 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.4-1+b2 ii libxml2 2.9.2+dfsg1-3 ii libxrandr2 2:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxslt1.1 1.1.28-2+b2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1+b1 ii x11-utils 7.7+2 ii xdg-utils 1.1.0~rc1+git20111210-7.4 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n <none> -- no debconf information
--- End Message ---
--- Begin Message --->>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. Best wishes, Mike
--- End Message ---
