Re:Timing attack against HSTS to sniff browser history in Ch...
by desdiv on Tuesday October 27, 2015 @01:23AM
(#10456440)
The JS code sent to kentonv's browser might be safe, but you can't really meaningfully comment on hobs' situation, since you don't have a copy of the JS code that was sent to hobs' browser.
[ Parent
| on HN ]
Re:Timing attack against HSTS to sniff browser history in Ch...
by kentonv on Tuesday October 27, 2015 @01:37AM
(#10456475)
Actually I can. The author of this code is a friend of mine who works with the EFF, and the idea that she's secretly sending malicious scripts to some people but not others from her MIT web hosting space under her own name is simply not plausible.
Re:Timing attack against HSTS to sniff browser history in Ch...
by e12e on Tuesday October 27, 2015 @06:42AM
(#10457224)
Unless, she's already compromised your browser and the two previous comments are in fact placed by her!
In all seriousness, I appreciate the added context your (particularly this last clarifying comment) add to the discussion.
Re:Timing attack against HSTS to sniff browser history in Ch...
by robzyb on Tuesday October 27, 2015 @01:40AM
(#10456480)
> The JS code sent to kentonv's browser might be safe, but you can't really meaningfully comment on hobs' situation [...]
But if that's the case then you shouldn't click on anything on HN.
I would argue that it is A-OK to post this link directly on hackernews.
It just says "look at what your browser can do! imagine if blackhats took advantage of this."
Re:Timing attack against HSTS to sniff browser history in Ch...
by bcrypt on Tuesday October 27, 2015 @02:08AM
(#10456542)
In any case, I didn't minify or remove comments, so you can just view-source:http://zyan.scripts.mit.edu/sniffly/index.js