<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: CSS overlays and frame breakers</title>
	<atom:link href="http://www.thespanner.co.uk/2008/08/10/css-overlays-and-frame-breakers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thespanner.co.uk/2008/08/10/css-overlays-and-frame-breakers/</link>
	<description>A tool for designers dealing with programmers dealing with designers...</description>
	<pubDate>Fri, 10 Sep 2010 15:40:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: rvdh</title>
		<link>http://www.thespanner.co.uk/2008/08/10/css-overlays-and-frame-breakers/#comment-1283</link>
		<dc:creator>rvdh</dc:creator>
		<pubDate>Tue, 12 Aug 2008 05:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.thespanner.co.uk/?p=220#comment-1283</guid>
		<description>One problem though, the anti-csrf seems vulnerable to overwriting GLOBALS. I skimmed through the code, but I cannot find any  GLOBALS protection that prevent GLOBALS from being overwritten though REQUEST, GET, COOKIE, and SESSION.

Example: 

somescript.php?GLOBALS[foo]=bar</description>
		<content:encoded><![CDATA[<p>One problem though, the anti-csrf seems vulnerable to overwriting GLOBALS. I skimmed through the code, but I cannot find any  GLOBALS protection that prevent GLOBALS from being overwritten though REQUEST, GET, COOKIE, and SESSION.</p>
<p>Example: </p>
<p>somescript.php?GLOBALS[foo]=bar</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth Heyes</title>
		<link>http://www.thespanner.co.uk/2008/08/10/css-overlays-and-frame-breakers/#comment-1280</link>
		<dc:creator>Gareth Heyes</dc:creator>
		<pubDate>Mon, 11 Aug 2008 12:50:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.thespanner.co.uk/?p=220#comment-1280</guid>
		<description>@Evert

Interesting, could you provide a example of this? Are you saying it's possible to supply a browser security policy through http headers?</description>
		<content:encoded><![CDATA[<p>@Evert</p>
<p>Interesting, could you provide a example of this? Are you saying it&#8217;s possible to supply a browser security policy through http headers?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evert</title>
		<link>http://www.thespanner.co.uk/2008/08/10/css-overlays-and-frame-breakers/#comment-1279</link>
		<dc:creator>Evert</dc:creator>
		<pubDate>Mon, 11 Aug 2008 12:38:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.thespanner.co.uk/?p=220#comment-1279</guid>
		<description>Note that you can get around the cookie-in-frames restriction by supplying a p3p header.</description>
		<content:encoded><![CDATA[<p>Note that you can get around the cookie-in-frames restriction by supplying a p3p header.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth Heyes</title>
		<link>http://www.thespanner.co.uk/2008/08/10/css-overlays-and-frame-breakers/#comment-1278</link>
		<dc:creator>Gareth Heyes</dc:creator>
		<pubDate>Mon, 11 Aug 2008 11:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.thespanner.co.uk/?p=220#comment-1278</guid>
		<description>frames and iframes can be used to fooling you into clicking something that isn't what you think it is. Using a frame breaker can prevent this sort of attack</description>
		<content:encoded><![CDATA[<p>frames and iframes can be used to fooling you into clicking something that isn&#8217;t what you think it is. Using a frame breaker can prevent this sort of attack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johny</title>
		<link>http://www.thespanner.co.uk/2008/08/10/css-overlays-and-frame-breakers/#comment-1277</link>
		<dc:creator>Johny</dc:creator>
		<pubDate>Mon, 11 Aug 2008 10:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.thespanner.co.uk/?p=220#comment-1277</guid>
		<description>well frames are still alive? Thought i have to go to the waybackmachine if i would like to see.</description>
		<content:encoded><![CDATA[<p>well frames are still alive? Thought i have to go to the waybackmachine if i would like to see.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
