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.

Sign up for GitHub

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

Jump to bottom

[Desktop] FP blocking: hardwareConcurrency does not match in WorkerNavigator and Navigator interfaces #11253

Closed
abrahamjuliot opened this issue Aug 16, 2020 · 1 comment
Closed

[Desktop] FP blocking: hardwareConcurrency does not match in WorkerNavigator and Navigator interfaces #11253

abrahamjuliot opened this issue Aug 16, 2020 · 1 comment
Labels
closed/duplicate Issue has already been reported OS/Desktop

Comments

@abrahamjuliot
Copy link

In strict and standard fingerprinting modes, Window.navigator.hardwareConcurrency does not match WorkerGlobalScope.navigator.hardwareConcurrency. FP scripts can interpret mismatching results as client API tampering or bot like behavior. It would be great if these scopes matched.

Tested in Nightly 1.14.44 desktop

Standard FP blocking

image

Strict FP blocking

image

related issues: #10808
@pes10k pes10k mentioned this issue Aug 21, 2020
Closed
@pes10k
Copy link
Contributor

pes10k commented Aug 21, 2020

As per #11254 (comment), i'm going to close this

@pes10k pes10k closed this as completed Aug 21, 2020
@pes10k pes10k added the closed/duplicate Issue has already been reported label Aug 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed/duplicate Issue has already been reported OS/Desktop
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pes10k @abrahamjuliot