Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can reduce clock precision, which has already been done to mitigate speculative execution attacks. You can delay network requests to prevent the JS from using the server as a more precise clock. In addition to random delays, you can quantize execution times by only responding in 100ms increments, for example. You can do lots of things to mitigate fingerprinting, if not completely prevent it.

But then you could also just omit features that have no reason to exist in the first place.



Or everybody can just buy the same (i)Phone :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: