<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Report and Case Study on CSRF</title>
	<atom:link href="http://ajaxian.com/archives/csrf-report/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/csrf-report</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: stim</title>
		<link>http://ajaxian.com/archives/csrf-report/comment-page-1#comment-267805</link>
		<dc:creator>stim</dc:creator>
		<pubDate>Wed, 01 Oct 2008 16:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4631#comment-267805</guid>
		<description>I wonder how the provided solution will work. All I can see is that the attack is delayed a bit, the attacker needs the client to pick up the token first, before issueing the attack. That is, create two CSRF to inflict one.
This provideds no security at all. (Or am I missing something?)

The only solution I can think of (also proposed in the article about clickjacking) is to allow the pickup of the tokens only after the user proves he&#039;s not a machine. Captcha&#039;s and the like on every action. Although that will be to intrusive.</description>
		<content:encoded><![CDATA[<p>I wonder how the provided solution will work. All I can see is that the attack is delayed a bit, the attacker needs the client to pick up the token first, before issueing the attack. That is, create two CSRF to inflict one.<br />
This provideds no security at all. (Or am I missing something?)</p>
<p>The only solution I can think of (also proposed in the article about clickjacking) is to allow the pickup of the tokens only after the user proves he&#8217;s not a machine. Captcha&#8217;s and the like on every action. Although that will be to intrusive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

