<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: CSRF attacks against OAuth</title>
	<atom:link href="http://blog.cliqset.com/2008/11/02/csrf-and-oauth/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cliqset.com/2008/11/02/csrf-and-oauth/</link>
	<description>What's going on at Cliqset and around the social web.</description>
	<lastBuildDate>Sat, 13 Mar 2010 10:34:40 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: NightWalker</title>
		<link>http://blog.cliqset.com/2008/11/02/csrf-and-oauth/#comment-112</link>
		<dc:creator>NightWalker</dc:creator>
		<pubDate>Mon, 15 Feb 2010 20:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://cliqset.wordpress.com/?p=22#comment-112</guid>
		<description>Pretty cool site you&#039;ve got here. Thanks for it. I like such topics and everything connected to this matter. I definitely want to read a bit more soon.

Sincerely yours</description>
		<content:encoded><![CDATA[<p>Pretty cool site you&#8217;ve got here. Thanks for it. I like such topics and everything connected to this matter. I definitely want to read a bit more soon.</p>
<p>Sincerely yours</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On OAuth Vulnerability &#124; dv8-designs</title>
		<link>http://blog.cliqset.com/2008/11/02/csrf-and-oauth/#comment-5</link>
		<dc:creator>On OAuth Vulnerability &#124; dv8-designs</dc:creator>
		<pubDate>Fri, 12 Jun 2009 09:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://cliqset.wordpress.com/?p=22#comment-5</guid>
		<description>[...] hint of the vulnerability surfaced last November as a CSRF-attack at Clickset Social Blog which was initially diagnosed as an implementation-level issue. Well, it turned out to be a design [...]</description>
		<content:encoded><![CDATA[<p>[...] hint of the vulnerability surfaced last November as a CSRF-attack at Clickset Social Blog which was initially diagnosed as an implementation-level issue. Well, it turned out to be a design [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On OAuth Vulnerability - News ums Netz</title>
		<link>http://blog.cliqset.com/2008/11/02/csrf-and-oauth/#comment-4</link>
		<dc:creator>On OAuth Vulnerability - News ums Netz</dc:creator>
		<pubDate>Fri, 22 May 2009 15:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://cliqset.wordpress.com/?p=22#comment-4</guid>
		<description>[...] hint of the vulnerability surfaced last November as a CSRF-attack at Clickset Social Blog which was initially diagnosed as an implementation-level issue. Well, it turned out to be a design [...]</description>
		<content:encoded><![CDATA[<p>[...] hint of the vulnerability surfaced last November as a CSRF-attack at Clickset Social Blog which was initially diagnosed as an implementation-level issue. Well, it turned out to be a design [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On OAuth Vulnerability &#171; Don Park&#8217;s Daily Habit</title>
		<link>http://blog.cliqset.com/2008/11/02/csrf-and-oauth/#comment-3</link>
		<dc:creator>On OAuth Vulnerability &#171; Don Park&#8217;s Daily Habit</dc:creator>
		<pubDate>Thu, 23 Apr 2009 22:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://cliqset.wordpress.com/?p=22#comment-3</guid>
		<description>[...] hint of the vulnerability surfaced last November as a CSRF-attack at Clickset Social Blog which was initially diagnosed as an implementation-level issue. Well, it turned out to be a design [...]</description>
		<content:encoded><![CDATA[<p>[...] hint of the vulnerability surfaced last November as a CSRF-attack at Clickset Social Blog which was initially diagnosed as an implementation-level issue. Well, it turned out to be a design [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
