Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Fingerprinting and window.navigator.hardwareConcurrency vs dom.maxHardwareConcurrency

  • 1 (رد واحد)
  • 1 has this problem
  • 24 views
  • آخر ردّ كتبه philipp

Miles_
Miles_
more options

Hello,

enabling privacy.resistFingerprinting sets window.navigator.hardwareConcurrency to 2 but dom.maxHardwareConcurrency stays at 16. Doesn't that undermine the first change?

Greetings

Miles

Hello, enabling privacy.resistFingerprinting sets window.navigator.hardwareConcurrency to 2 but dom.maxHardwareConcurrency stays at 16. Doesn't that undermine the first change? Greetings Miles

الحل المُختار

hi, websites can query window.navigator.hardwareConcurrency, which will return the value of 2 if fingerprinting resistance is active.

the other value is an about:config preference that can't be read by websites and sets the maximum value that might be reported to websites if fingerprinting resistance is off and your system had more than X (16) cores...

Read this answer in context 👍 2

All Replies (1)

philipp
philipp
  • Moderator
more options

الحل المُختار

hi, websites can query window.navigator.hardwareConcurrency, which will return the value of 2 if fingerprinting resistance is active.

the other value is an about:config preference that can't be read by websites and sets the maximum value that might be reported to websites if fingerprinting resistance is off and your system had more than X (16) cores...