2016-01-21 (gunnersson): several rules (all categories) #41
Conversation
|
Thank you, this helps. I will start the review with |
| {"o":{"h":"*.emp.de"},"d":{"h":"*.acfrg.com"}}, | ||
| {"o":{"h":"*.microsoft.com"},"d":{"h":"*.s-msft.com"}}, | ||
| {"o":{"h":"*.eff.org"},"d":{"h":"*.trackersimulator.org"}}, | ||
| {"o":{"h":"*.eff.org"},"d":{"h":"*.eviltracker.net"}}, |
There was a problem hiding this comment.
eviltracker.net and trackersimulator.org seem to be only required from panopticlick.eff.org. Please edit these rules. Edit: same for the rule below.
There was a problem hiding this comment.
Yes. They run special tests at panopticlick.eff.org, therefore eviltracker.net and trackersimulator.org are needed. If one don't want to run those tests or are not reliant on true(?) response, we could just delete these rules (or even blacklist them).
There was a problem hiding this comment.
I meant the rule should be
+ {"o":{"h":"panopticlick.eff.org"},"d":{"h":"*.trackersimulator.org"}},
not the wildcard *.eff.org. But yes we might want to remove these rules as this demonstrates how RP can help preventing fingerprinting.
There was a problem hiding this comment.
Oh, dude. Shame on me for the missing panopticlick before eff.org. Sry.
It just leaves the questions whether to keep or delete it. Either way PROs and CONs.
There was a problem hiding this comment.
Fingerprinting demo is a feature of panopticlick, but effectively an "attack" on the browser (with user consent unless, you link directly to https://panopticlick.eff.org/tracker...). I think the rule should be deleted.
@myrdd what you suggest looks ok to me. Should we keep the As you can see, reviewing these patches takes a lot of time, maintaining these lists centrally is an endless task. I wish RPC could be made aware of custom subscription lists (maybe @gunnersson or other users would like to publish theirs?), by entering their URLs. The RPC wiki could point to unofficial, custom user subscriptions. Or we can have an uBlock already allows using custom lists. Blocklists, but also whitelists (called unbreak lists, in case you use µB in medium/hard mode - an equivalent to RPC functionality). I think this is the way to go for RP (allowing third party subscriptions). I would be willing to work on conversion tools between ublock/hosts/RPC lists. |
| {"o":{"h":"*.eff.org"},"d":{"h":"*.do-not-tracker.org"}}, | ||
| {"o":{"h":"*.shortfil.ms"},"d":{"h":"*.eay.cc"}}, | ||
| {"o":{"h":"*.virustotal.com"},"d":{"h":"*.virustotalcloud.appspot.com"}}, | ||
| {"o":{"h":"*.upb.de"},"d":{"h":"*.pingo.cc"}}, |
There was a problem hiding this comment.
upb.de doesn't load pingo.cc
|
@nodiscc I'll fully respond to your questions next week; don't have the time right now. I can see that maintaining the lists is hard work – we should find a solution there. Maybe some kind of assertions per rule could help. An example could be:
That assertion could be checked automatically, and the rule could be removed if the assertion fails, e.g. if the site goes down. You get what I mean? — Of course, custom lists need to be supported as well. |
| {"o":{"h":"*.breakofreality.com"},"d":{"h":"*.wp.com"}}, | ||
| {"o":{"h":"*.physicsdatabase.com"},"d":{"h":"*.pinimg.com"}}, | ||
| {"o":{"h":"*.physicsdatabase.com"},"d":{"h":"*.bookmanager.com"}}, | ||
| {"o":{"h":"*.jojawendt.com"},"d":{"h":"*.server-he.de"}}, |
There was a problem hiding this comment.
origin doesn't load server-he.de for me. Site is blank.
|
@gunnersson the |
Does this answer your question?
This is what rp#736 is all about.
I think it will be rather integrated into RP itself – IMHO makes sense. The user could add his personal lists in that "other" format, such as a hosts-file. I've created issue rp#768 for that purpose. About list maintanence, see #44. |
Yep.
This is great. Support for |
|
@gunnersson Can you apply the recommended changes? |
|
Dear all, Am 12.06.2016 um 15:15 schrieb nodiscc:
Sorry I cannot help nor support any more. I don't use RPC any more. I now use just this config: Kind regards, Gunner |
|
@gunnersson Thanks for your reply, and no problem. For a comprehensive hardened configuration you might want to check the user.js file at https://github.com/pyllyukko/user.js/. |
|
:-) Am 13.06.2016 um 19:35 schrieb nodiscc:
Thank you. I have many of @pyllyukko settings included in my profile, and some of Instead of RPC I have been using:
Thank you and best wishes, Gunner |
Dear all,
I eventually set up a fork of the subscriptions repository and just added my rules. They apply to several categories: allow_functionality, allow_sameorg, deny-trackers.
Please check them and hopefully include them.
Thank you,
Gunner