News for hackers. Stuff that matters.
Re:Matryoshka: Wrapping Overflow Leak on Frames by mcphilip on Sunday September 22, 2013 @11:53PM (#6429094)
Fascinating.

Is it correct to say that extracting information about the text in a target iframe using this attack depends on knowing the pixel widths of all the characters in the font used in an arbitrary line of text in the target iframe?

Re:Matryoshka: Wrapping Overflow Leak on Frames by Perseids on Monday September 23, 2013 @06:49AM (#6429979)
It is even more complex as the width of a text in most fonts also varies with the specific order of the characters because of kerning (VAI takes less space than VIA, because the A is placed closer to the V in former) and ligatures (for example the dot of the i in "fi" is often swallowed by the f).
Re:Matryoshka: Wrapping Overflow Leak on Frames by guruz on Monday September 23, 2013 @06:01AM (#6429853)
From the headline, i first thought about the MKV video container and video frames. :)
Re:Matryoshka: Wrapping Overflow Leak on Frames by mylorse on Sunday September 22, 2013 @11:58PM (#6429104)
Good thing I do not run Javascript, esp. when items are fetched from other domains:

http://postimg.org/image/3m9v8eyrx/

I wonder how many people are still naive, and just leave it JS on, no questions asked..

Re:Matryoshka: Wrapping Overflow Leak on Frames by rspeer on Monday September 23, 2013 @02:21AM (#6429412)
Q: How do you know when an HN user browses the Web with JavaScript turned off?

A: They'll tell you.

Re:Matryoshka: Wrapping Overflow Leak on Frames by gtani on Monday September 23, 2013 @07:31AM (#6430119)
Yahoo found in 2010: 98%+, depending on country

http://stackoverflow.com/questions/9478737/browser-statistic...

Re:Matryoshka: Wrapping Overflow Leak on Frames by rwmj on Monday September 23, 2013 @03:17AM (#6429511)
Could the browser make small fractional random changes (+/-1 px) to the requested iframe size to avoid this attack?