Skip to content
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

FYI: A comparison of web privacy protection techniques #316

Closed
Thorin-Oakenpants opened this issue Dec 23, 2017 · 6 comments
Closed

FYI: A comparison of web privacy protection techniques #316

Thorin-Oakenpants opened this issue Dec 23, 2017 · 6 comments
Labels

Comments

@Thorin-Oakenpants
Copy link
Contributor

Thorin-Oakenpants commented Dec 23, 2017

snip

@Atavic
Copy link

Atavic commented Dec 23, 2017

👍 Good find!

@Atavic
Copy link

Atavic commented Dec 23, 2017

That figure just compares the numbers of blocked requests and domains, with the common ones into the green square. The diagonal has the items blocked exclusively by a specific addon.

...it's on prev page, right side.

@Atavic
Copy link

Atavic commented Dec 23, 2017

Seems like Ghostery has specific blocks of the same script, while Gorhill has neutered it:
gorhill/uBlock#902 (comment)

@gorhill
Copy link

gorhill commented Dec 25, 2017

Sorry I didn't have time yet to read all the details of the papers, I just quickly scanned it.

Table1 lists the version as 1.6 which doesn't exist yet - maybe they meant 1.06?

Version 1.6 was released on Feb. 10, 2016.

Not too long after 1.6 came out I started to make more use of uBO's ability to redirect to local neutered resources, to foil widely used 3rd parties, for example googletagservices.com -- not blocked by EasyPrivacy. So nowadays the authors would find much better results for uBO.

Its a shame uM wasn't included

Or even just uBO's medium mode, given they have covered NoScript and RequestPolicyContinued. I would say it's even weird given that uMatrix has a larger user base than RPC. But anyways, it's questionable to include default-deny extensions in such test, of course they will always have the upper hand when it comes to foil 3rd parties, at the cost of web page breakage, that sort of extensions can never be meaningfully compared to install-and-forget blockers.

@earthlng
Copy link
Contributor

uBo can control XSS on a per domain basis

just FYI, XSS is a term used for a common vulnerability, and I think what you mean is XHR.

@Atavic
Copy link

Atavic commented Dec 28, 2017

It's under notifications where 5 options are enabled:

  • blocked scripts
  • XSS
  • blocked META redirections
  • ABE
  • ClearClick Warning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants