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.

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

Open
kumavis opened this issue Jan 22, 2017 · 8 comments
Open

TorBrowser finger printing does not complete #74

kumavis opened this issue Jan 22, 2017 · 8 comments

Comments

@kumavis
Copy link

kumavis commented Jan 22, 2017

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:

image

Here are the console logs:
https://gist.github.com/kumavis/30084558c2008c5dd6989645b42ae8ee

Thanks - this is really interesting work.

@Song-Li
Copy link
Owner

Song-Li commented Jan 24, 2017

Thank you so much for your bug.
In fact, in our paper, we mentioned that Tor browser is our recommendation for defending our work. Sorry that I forgot the reason.
I will check Tor browser and update the work in the future. Thank you!

@Atavic
Copy link

Atavic commented Feb 15, 2017

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.

@Song-Li
Copy link
Owner

Song-Li commented Feb 17, 2017

@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.
Thank you again!

@Atavic
Copy link

Atavic commented Feb 17, 2017

Nice project, @Song-Li

I'll re-check and report here.

@tomrittervg
Copy link

I was curious about this too! In my case, the test did not complete with Tor Browser, it showed:

  • "Your graphics card does not seem to support WebGL. Find out how to get it here."
  • A NoScript box directly underneath 'Fingerprint GPU...'

This was on the 'Low' Security Slider setting.

@pyllyukko
Copy link

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.

@Maxlive-Dev
Copy link

@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

@Song-Li
Copy link
Owner

Song-Li commented Mar 3, 2017

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants