News for hackers. Stuff that matters.

A comment on Block Fingerprinting with Firefox. Parent comment

Re:Block Fingerprinting with Firefox by kevin_thibedeau on Thursday May 30, 2019 @06:20PM (#20056524)
The numbers don't make much sense to me. On FF I get 14.05 with NoScript active. Curiously the headers increase from 1.68 bits to 3.47 when NoScript is running.
[ Parent | on HN ]
Re:Block Fingerprinting with Firefox by floatingatoll on Thursday May 30, 2019 @06:42PM (#20056673)
NoScript is likely a valuable fingerprinting indicator, given that the vast majority of browsers have JavaScript enabled but you don’t.
[ Parent | on HN ]
Re:Block Fingerprinting with Firefox by zucker42 on Thursday May 30, 2019 @06:44PM (#20056679)
Of course no script increases the entropy. Most people don't run NoScript, so you are more identifiable when you run it.
[ Parent | on HN ]
Re:Block Fingerprinting with Firefox by kevin_thibedeau on Thursday May 30, 2019 @07:52PM (#20057066)
It increases the entropy for the JavaScript tests as would be expected. It shouldn't affect the HTTP_ACCEPT header.
[ Parent | on HN ]
Re:Block Fingerprinting with Firefox by rjf72 on Friday May 31, 2019 @02:06AM (#20058595)
I'm curious about the difference between things like NoScript and native Brave script blocking.

In particular I was going to make a snarky comment that the site seems to, appropriately, not work when script blocking is enabled on Brave. I do get the site to do the refresh business a couple of times, but no results are ever displayed.

[ Parent | on HN ]