-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking protection uses the same API as Google Safe Browsing #22
Comments
From what I've understood, the tracking protection should use a blacklist, which shouldn't leak information about the sites you visit. Of course that comment implies something else, but I would like to see some more facts about this. Do you have some other references regarding this? I guess we'll just need to dive into the source code and check it from there. |
Here is a list of
|
Looks like I have found a confirmation: mozilla-release\modules\libpref\init\all.js:
mozilla-release\testing\profiles\prefs_general.js:
|
Thanks for these details. Now I think the only remaining question is, whether this is bad or not. As I said previously, my impression was that it still shouldn't leak information. At least the following links state that this is the case:
Then again, of course your IP address is one thing that is being leaked, but does getting some extra protection outweigh this or not? |
I just mean that we have to stay consistent and either enable or disable both Safe Browsing and Tracking Protection. Because if Tracking Protection doesn't leak enough information to be considered dangerous, then Safe Browsing is the same. |
Ah. Gotcha! :) |
Then again... it is not only a matter of the API that is being used, but also who provides that service. As safe browsing is provided by Google and tracking protection is from Mozilla. |
List of
|
shavar.services.mozilla.com is hosted on AmazonCDN. Although the API is the same, Mozilla modified its usage: |
Also, why on earth is HTTPS needed for downloading a list of SHA256 hashes from URLs? HTTPS is way overused in general. Particularly here it is simply not needed because the content is a list of hashes with no personal info whatsoever. |
Because otherwise your network provider could change the list that's sent to Firefox (for example, whitelisting their own trackers or blocking their competitors'). HTTPS is not just about encryption, it's also about integrity protection. |
https://github.com/pyllyukko/user.js/blob/master/user.js:
See amq/firefox-debloat#2 (comment)
The text was updated successfully, but these errors were encountered: