Re:An advanced browser fingerprint calculator aimed mainly a...
by mirimir on Wednesday March 22, 2017 @12:58AM
(#13928573)
It's complicated. Javascript is enabled, but NoScript is installed. But NoScript by default allows all "honest" scripts, although it does block some stuff. But that's in the default "low security" mode. The goal is having websites work, so users won't give up on Tor, while providing some security. Users can increase security, but there are only three options (low, medium and high). That's to keep user profiles in fewer bins. In the "high security" mode, all scripts are blocked.
[ Parent
| on HN ]
Re:An advanced browser fingerprint calculator aimed mainly a...
by cookiecaper on Wednesday March 22, 2017 @01:07PM
(#13932695)
I used NoScript roughly ten years ago and it was a lot of work to manually enable JavaScripts all over the place. I used it for a couple of years solid, but eventually gave up on it, since I was practically just enabling JavaScripts on every site anyway. Everyone I tried to introduce it to gave up on it after a few weeks at most.
To NoScript's credit, it did block a phishing site that I otherwise would've fallen for once.
That was before the era of single-page apps. Like it or not, JavaScript is mandatory for even basic functionality on the modern web.
Telling users to introduce 4 clicks to load every new domain and potentially experience some significant breakages (e.g., I remember some checkout processes failing because they'd bounce the request around between scripts from processors, fraud prevention, etc.) just on the remote chance that they'll encounter malicious JavaScript is simply a non-starter. Something like Ghostery that mostly-transparently blocks things is a better proposition for ordinary adoption.