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

blocking third-party fingerpriting has no effect #3698

Closed
cezaraugusto opened this issue Mar 13, 2019 · 1 comment
Closed

blocking third-party fingerpriting has no effect #3698

cezaraugusto opened this issue Mar 13, 2019 · 1 comment
Labels
closed/not-actionable feature/shields/fingerprint The fingerprinting (aka: "device recognition") protection provided in Shields priority/P2 A bad problem. We might uplift this to the next planned release. QA/Yes

Comments

@cezaraugusto
Copy link
Contributor

Description

Setting Shields to block third-party scripts has no effects.

Steps to Reproduce

  1. Visit https://cezaraugusto.github.io/privacy-checks/fingerprinting/third-party/
  2. Set fingerprinting protection to block all fingerprinting
  3. Assert it works
  4. Set fingerprinting protection to block third party scripts

Actual result:

Script bypasses Shields option

Expected result:

If a fingerprinting script is hosted in a third-party domain, this Shields setting should block resouce from loading.

Reproduces how often:

Always

Brave version (brave://version info)

v0.60.23

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?
    yes

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields? no
  • Is the issue reproducible on the latest version of Chrome? n/a

Additional Information

n/a

@cezaraugusto cezaraugusto added the feature/shields/fingerprint The fingerprinting (aka: "device recognition") protection provided in Shields label Mar 13, 2019
@tildelowengrimm tildelowengrimm added the priority/P2 A bad problem. We might uplift this to the next planned release. label Apr 17, 2019
@pes10k
Copy link
Contributor

pes10k commented Apr 2, 2021

This is addressed by the move to farbling based fingerprinting protections

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/not-actionable feature/shields/fingerprint The fingerprinting (aka: "device recognition") protection provided in Shields priority/P2 A bad problem. We might uplift this to the next planned release. QA/Yes
Projects
None yet
Development

No branches or pull requests

4 participants