<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: X-FRAME-OPTIONS in Firefox</title>
	<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/</link>
	<description>Giorgio Maone's answers to the Web, the Universe, and Everything</description>
	<pubDate>Wed, 08 Feb 2012 11:52:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Mike</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-20007</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 27 Jan 2010 00:31:02 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-20007</guid>
		<description>I've implemented X-Frame-Options on my website using some simple Apache config. See https://secure.grepular.com/ClickJacking_and_SSL_Protection_in_Apache for information on how to do it.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve implemented X-Frame-Options on my website using some simple Apache config. See <a href="https://secure.grepular.com/ClickJacking_and_SSL_Protection_in_Apache" rel="nofollow">https://secure.grepular.com/ClickJacking_and_SSL_Protection_in_Apache</a> for information on how to do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackademix.net » Google Talk Badges vs X-Frame-Options</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-16480</link>
		<dc:creator>hackademix.net » Google Talk Badges vs X-Frame-Options</dc:creator>
		<pubDate>Wed, 02 Dec 2009 20:14:47 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-16480</guid>
		<description>[...] frame) — or a blank one if you’re on Chrome — because Google is sending down a X-Frame-Option HTTP header with value SAMEORIGIN, allowing only pages served from www.google.com to embed this [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] frame) — or a blank one if you’re on Chrome — because Google is sending down a X-Frame-Option HTTP header with value SAMEORIGIN, allowing only pages served from <a href="http://www.google.com" rel="nofollow">www.google.com</a> to embed this [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Modern-Day Frame Busting With X-FRAME-OPTIONS And &#34;This content cannot be displayed in a frame&#34; Warnings</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-15641</link>
		<dc:creator>Modern-Day Frame Busting With X-FRAME-OPTIONS And &#34;This content cannot be displayed in a frame&#34; Warnings</dc:creator>
		<pubDate>Fri, 30 Oct 2009 01:25:37 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-15641</guid>
		<description>[...] useful discussion on the issue can also be found in this post on [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] useful discussion on the issue can also be found in this post on [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Open Source Firefox Extension NoScript Updated &#124; Infosecurity.US</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-11385</link>
		<dc:creator>Open Source Firefox Extension NoScript Updated &#124; Infosecurity.US</dc:creator>
		<pubDate>Fri, 13 Mar 2009 16:10:24 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-11385</guid>
		<description>[...] incident reporting tool. Improved script blocking and scriptless pages management. Improved X-FRAME-OPTIONS compatibility support. New exclusive protection against JSON and E4X hijacking. Anti-XSS filters performance [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] incident reporting tool. Improved script blocking and scriptless pages management. Improved X-FRAME-OPTIONS compatibility support. New exclusive protection against JSON and E4X hijacking. Anti-XSS filters performance [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackademix.net » Browser Plugins, Add-Ons and Security Advisers</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10819</link>
		<dc:creator>hackademix.net » Browser Plugins, Add-Ons and Security Advisers</dc:creator>
		<pubDate>Sat, 07 Feb 2009 17:02:41 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10819</guid>
		<description>[...] send Roger an email, sparking a pretty intense exchange (in the meanwhile, I was implementing PoC X-Frame-Options compatibility for Firefox with my left [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] send Roger an email, sparking a pretty intense exchange (in the meanwhile, I was implementing PoC X-Frame-Options compatibility for Firefox with my left [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Giorgio</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10741</link>
		<dc:creator>Giorgio</dc:creator>
		<pubDate>Mon, 02 Feb 2009 00:27:51 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10741</guid>
		<description>@&lt;b&gt;MacOtaku&lt;/b&gt;:
"Traditional" frame busting emulation is controlled by the &lt;b&gt;noscript.emulateFrameBreak&lt;/b&gt; about:config preference.
I can add a similar preference for X-FRAME-OPTIONS in next release (it was already planned, anyway).</description>
		<content:encoded><![CDATA[<p>@<b>MacOtaku</b>:<br />
&#8220;Traditional&#8221; frame busting emulation is controlled by the <b>noscript.emulateFrameBreak</b> about:config preference.<br />
I can add a similar preference for X-FRAME-OPTIONS in next release (it was already planned, anyway).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MacOtaku</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10740</link>
		<dc:creator>MacOtaku</dc:creator>
		<pubDate>Sun, 01 Feb 2009 23:50:34 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10740</guid>
		<description>I know it's a small issue, but this feature should allow the user to override it, so it isn't misused. Unfortunately, unlike JS frame busting, there is presently no practical means for the user to override this feature when it is abused by web publishers. For example, if a page doesn't want to be framed, not for security, but as part of yet another obnoxious, paranoid, and ineffective &#34;copy-protection&#34; scheme (like those &#34;clever&#34; scripts that set onselectstart, etc to function(){return false}), and I land on said page framed as a Google image search result, I can stop it from frame-busting by denying its JS. (Actually, can I -- or does NoScript prevent me from stopping it by emulating frame-busting without consulting the user?) Now, if the HTTP header is honoured without giving the user a means to override it, how then do I prevent the page messing up a legitimate framing (such as an images.google result, or a Facebook posted item)?</description>
		<content:encoded><![CDATA[<p>I know it&#8217;s a small issue, but this feature should allow the user to override it, so it isn&#8217;t misused. Unfortunately, unlike JS frame busting, there is presently no practical means for the user to override this feature when it is abused by web publishers. For example, if a page doesn&#8217;t want to be framed, not for security, but as part of yet another obnoxious, paranoid, and ineffective &quot;copy-protection&quot; scheme (like those &quot;clever&quot; scripts that set onselectstart, etc to function(){return false}), and I land on said page framed as a Google image search result, I can stop it from frame-busting by denying its JS. (Actually, can I &#8212; or does NoScript prevent me from stopping it by emulating frame-busting without consulting the user?) Now, if the HTTP header is honoured without giving the user a means to override it, how then do I prevent the page messing up a legitimate framing (such as an images.google result, or a Facebook posted item)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Giorgio</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10730</link>
		<dc:creator>Giorgio</dc:creator>
		<pubDate>Sun, 01 Feb 2009 19:13:06 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10730</guid>
		<description>@&lt;b&gt;Joris&lt;/b&gt;:
Fixed in &lt;a href="http://noscript.net/getit#devel" rel="nofollow"&gt;1.9.0.2&lt;/a&gt;, thanks.
Notice that you won't get an error message for OBJECT elements, but the request gets blocked anyway.</description>
		<content:encoded><![CDATA[<p>@<b>Joris</b>:<br />
Fixed in <a href="http://noscript.net/getit#devel" rel="nofollow">1.9.0.2</a>, thanks.<br />
Notice that you won&#8217;t get an error message for OBJECT elements, but the request gets blocked anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joris van der Wel</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10723</link>
		<dc:creator>Joris van der Wel</dc:creator>
		<pubDate>Sun, 01 Feb 2009 12:16:43 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10723</guid>
		<description>Just did some tests and it appears that &#34;X-IFRAME-OPTIONS&#34; does not work with &#60;object data=&#34;http://evil.hackademix.net/frameopts/?o=2&#34;&#62;&#60;/object&#62;. 

Also, I have noticed that sometimes the link &#34;Click here to open this content in a new window&#34; will open the chrome url of the error message instead of the page. Unfortunately I am not sure how to properly recreate this.

Also, awesome extension

Gr. Joris</description>
		<content:encoded><![CDATA[<p>Just did some tests and it appears that &quot;X-IFRAME-OPTIONS&quot; does not work with &lt;object data=&quot;http://evil.hackademix.net/frameopts/?o=2&quot;&gt;&lt;/object&gt;. </p>
<p>Also, I have noticed that sometimes the link &quot;Click here to open this content in a new window&quot; will open the chrome url of the error message instead of the page. Unfortunately I am not sure how to properly recreate this.</p>
<p>Also, awesome extension</p>
<p>Gr. Joris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackademix.net » All That ClickJazz...</title>
		<link>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10708</link>
		<dc:creator>hackademix.net » All That ClickJazz...</dc:creator>
		<pubDate>Sat, 31 Jan 2009 21:07:54 +0000</pubDate>
		<guid>http://hackademix.net/2009/01/29/x-frame-options-in-firefox/#comment-10708</guid>
		<description>[...] protection which will work on those pages whose authors decide to adopt the new proprietary X-FRAME-OPTIONS header (now cross-browser), interest of the press about this topic has been raising again. Unluckily, Clickjacking (or more [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] protection which will work on those pages whose authors decide to adopt the new proprietary X-FRAME-OPTIONS header (now cross-browser), interest of the press about this topic has been raising again. Unluckily, Clickjacking (or more [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

