You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i set the value with uBlock Origin with abrahamjuliot.github.io##+js(set, navigator.deviceMemory, 1) on Firefox the site doesn’t detect this fake and also clears my visits.
Good catch. It's detected in console.log(Fingerprint.navigator.lied) but not shown in the top section. There exist several similar inline detections that can be displayed with a message. I believe we used the iframe mismatch detection to capture it, but your suggestion is better and straightforward.
You should get two different fingerprints, one clean and one wrong. The invalid one should not change if you rotate the memory via JS.
Yes 2 fingerprints and no change when i rotate. But a fake memory on a browser which don’t even support this should be just throwed away without affecting the final fingerprint or not?
It's better to preserve the additional entropy if we can keep it stable. The existing lie is better entropy than a restored result. Maybe there are some use cases for restoring the original, but they will be limited to what we can restore.
abrahamjuliot
changed the title
fake navigator.deviceMemory doesn’t getting detected on firefox
Fake deviceMemory not detected on Firefox
Jul 31, 2024
When i set the value with uBlock Origin with
abrahamjuliot.github.io##+js(set, navigator.deviceMemory, 1)
on Firefox the site doesn’t detect this fake and also clears my visits.Firefox doesn’t support
navigator.deviceMemory
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/deviceMemoryThe text was updated successfully, but these errors were encountered: