<?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: Airtight sessions</title>
	<atom:link href="http://sparepencil.com/archives/2007/04/15/airtight-sessions/feed/" rel="self" type="application/rss+xml" />
	<link>http://sparepencil.com/archives/2007/04/15/airtight-sessions/</link>
	<description></description>
	<pubDate>Tue, 02 Dec 2008 22:16:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Kovacs</title>
		<link>http://sparepencil.com/archives/2007/04/15/airtight-sessions/#comment-1642</link>
		<dc:creator>Kovacs</dc:creator>
		<pubDate>Sun, 15 Apr 2007 23:17:06 +0000</pubDate>
		<guid isPermaLink="false">http://sparepencil.com/archives/2007/04/15/airtight-sessions/#comment-1642</guid>
		<description>Uhm... a similar exploit to this has been around for a while except to my knowledge could only be performed if the victim went from site A straight to site B. Nice article nonetheless and I'm liking the new site... could do with a little bit of design clean up though... like when your numbered lines in the code get into double digits, the former digit extrudes from within the box.</description>
		<content:encoded><![CDATA[<p>Uhm&#8230; a similar exploit to this has been around for a while except to my knowledge could only be performed if the victim went from site A straight to site B. Nice article nonetheless and I&#8217;m liking the new site&#8230; could do with a little bit of design clean up though&#8230; like when your numbered lines in the code get into double digits, the former digit extrudes from within the box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas</title>
		<link>http://sparepencil.com/archives/2007/04/15/airtight-sessions/#comment-1641</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Sun, 15 Apr 2007 09:54:59 +0000</pubDate>
		<guid isPermaLink="false">http://sparepencil.com/archives/2007/04/15/airtight-sessions/#comment-1641</guid>
		<description>Site B will be able to make an HTTP POST request, but it can not set the session ID in question because it does not have access to it.

The problem lies in the fact that site B can send a request to site A and trick the browser into sending site A's cookie, too. However, it can never read the cookie data for site A (not with this particular exploit, anyway).</description>
		<content:encoded><![CDATA[<p>Site B will be able to make an HTTP POST request, but it can not set the session ID in question because it does not have access to it.</p>
<p>The problem lies in the fact that site B can send a request to site A and trick the browser into sending site A&#8217;s cookie, too. However, it can never read the cookie data for site A (not with this particular exploit, anyway).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vincent</title>
		<link>http://sparepencil.com/archives/2007/04/15/airtight-sessions/#comment-1640</link>
		<dc:creator>Vincent</dc:creator>
		<pubDate>Sun, 15 Apr 2007 09:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://sparepencil.com/archives/2007/04/15/airtight-sessions/#comment-1640</guid>
		<description>But why wouldn't site B be able to make a HTTP POST request and send the session ID in it? How will an attack look if airtight sessions (i.e. what will happen when it fails)? How does this prevent the attack?</description>
		<content:encoded><![CDATA[<p>But why wouldn&#8217;t site B be able to make a HTTP POST request and send the session ID in it? How will an attack look if airtight sessions (i.e. what will happen when it fails)? How does this prevent the attack?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
