-
Notifications
You must be signed in to change notification settings - Fork 263
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.
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
TorBrowser finger printing does not complete #74
Comments
Thank you so much for your bug. |
Same result with BFilter locally installed. By looking at BFilter Request Log I see the various JS loaded, but fps.js doesn't pass through BFilter. |
@Atavic Thank you so much for your comment. During the research period, "fps.js" is used for measure the performance of computer (mostly Graphic card). Based on our collected data, we found that fps is not a good feature so we deleted it. Maybe it's the problem that causes this bug. I'll fix this and have a try. |
Nice project, @Song-Li I'll re-check and report here. |
I was curious about this too! In my case, the test did not complete with Tor Browser, it showed:
This was on the 'Low' Security Slider setting. |
I'm experiencing the same issue with the test(s) not completing with our Firefox hardening. The hardening completely disables WebGL, but I understood that Unique Machine should have other methods also. |
@Song-Li @Atavic fps.js is required in http://uniquemachine.org/fingerprint/index.html now, so I supposed to restore it, or maybe it's better to delete both fingerprint/three/fps.coffee and a call for fps.js in fingerprint/index.html |
@Maxlive-Dev Yeap your are right. I tried to remove the fps.js. We dont need that anymore. I wanted to use fps to get the performance of GPU, but the result is really unstable. I'll just delete the fps part. Thank you! |
I'm curious about UniqueMachine's ability to work on TorBrowser. TorBrowser does protect the user with some things requiring opt-in (e.g. run js, read from canvas).
I allowed these to run on the site and refreshed. It still could not complete the finger print generation. Gets stuck here:
Here are the console logs:
https://gist.github.com/kumavis/30084558c2008c5dd6989645b42ae8ee
Thanks - this is really interesting work.
The text was updated successfully, but these errors were encountered: