News for hackers. Stuff that matters.
Re:HTML5 Sandbox - a bad idea by chickopozo on Friday April 05, 2013 @11:41PM (#5502542)
TL;DR Author is wrong about clickjacking and sandboxing is a good thing.
Re:HTML5 Sandbox - a bad idea by kevingadd on Friday April 05, 2013 @11:42PM (#5502545)
You failed to address his realistic criticism that many websites are not yet using X-Frame-Options. Browsers that introduce the sandbox feature have now broken those sites' security.
Re:HTML5 Sandbox - a bad idea by shardling on Friday April 05, 2013 @11:53PM (#5502567)
I'm not sure what you mean -- how can the browser possibly break the sites security?

I understand that English is not everyone's first language, but I honestly had a hard time parsing the linked post.

Re:HTML5 Sandbox - a bad idea by moonboots on Saturday April 06, 2013 @12:07AM (#5502593)
Sandbox iframes allow disabling javascript in a frame, which disables framebusting protection [1] used by sites like vk.com. The better way to framebust is to add the header 'x-frame-options: deny', which isn't broken by html5 sandboxes.

[1] http://en.wikipedia.org/wiki/Framekiller

Re:HTML5 Sandbox - a bad idea by homakov on Friday April 05, 2013 @11:58PM (#5502574)
Obviously he meant turning of JS made clickjacking feasible again for many websites. Why u pretend to not understand that? Are u kind of html5 moralist?
Re:HTML5 Sandbox - a bad idea by homakov on Saturday April 06, 2013 @12:02AM (#5502581)
how can i be wrong about clickjacking? I use XFO. I pointed out obvious thing - not everyone uses XFO.

Sandbox COULD be a good thing. Eventually it's evil