Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

Fingerprinting and window.navigator.hardwareConcurrency vs dom.maxHardwareConcurrency

  • 1 ответ
  • 1 имеет эту проблему
  • 28 просмотров
  • Последний ответ от philipp

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...

Прочитайте этот ответ в контексте 👍 2

Все ответы (1)

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...