Skip to content
This repository was archived by the owner on Nov 17, 2017. It is now read-only.
This repository was archived by the owner on Nov 17, 2017. It is now read-only.

How does Privacy Badger prevent making the user more fingerprintable? #809

Description

@TheLastProject

From what I see, Privacy Badger seems to decide what sites to block or allow based on browsing behaviour, which would seem to generate an unique list of sites to block based on what sites the user visits.

Couldn't malicious sites simply use JavaScript to load data from third-party sites and check if the requests are blocked or not to fingerprint the user?

Does Privacy Badger have any mechanisms to prevent creating an additional metric that can be used to fingerprint, thus making the browser more fingerprintable?

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions