<?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: Hotlinks and Persistent CSRF</title>
	<atom:link href="http://michaeldaw.org/papers/hotlink_persistent_csrf/feed" rel="self" type="application/rss+xml" />
	<link>http://michaeldaw.org/papers/hotlink_persistent_csrf</link>
	<description>Weekly humour</description>
	<lastBuildDate>Thu, 07 May 2009 20:09:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeremiah Blatz</title>
		<link>http://michaeldaw.org/papers/hotlink_persistent_csrf/comment-page-1#comment-20597</link>
		<dc:creator>Jeremiah Blatz</dc:creator>
		<pubDate>Tue, 17 Apr 2007 13:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/hotlink_persistent_csrf/#comment-20597</guid>
		<description>The cool thing is that you can be arbitrarily sneaky with this. Back in the day, I posted a little article about how to swap an image based on request parameters on AntiOnline (shame). Basically, you show one image to users with no referrer or an authorized referrer, and another one to everyone else. If you want to be super-sneaky, you can try to figure out the ip address/range of the linker, and show them the &quot;authorized&quot; pic, too. 

Since the visitors are none the wiser, they presumably won&#039;t be forging their referrer, so you shouldn&#039;t need to worry about that.

http://antionline.com/showthread.php?t=238136&amp;page=2</description>
		<content:encoded><![CDATA[<p>The cool thing is that you can be arbitrarily sneaky with this. Back in the day, I posted a little article about how to swap an image based on request parameters on AntiOnline (shame). Basically, you show one image to users with no referrer or an authorized referrer, and another one to everyone else. If you want to be super-sneaky, you can try to figure out the ip address/range of the linker, and show them the &#8220;authorized&#8221; pic, too. </p>
<p>Since the visitors are none the wiser, they presumably won&#8217;t be forging their referrer, so you shouldn&#8217;t need to worry about that.</p>
<p><a href="http://antionline.com/showthread.php?t=238136&amp;page=2" rel="nofollow">http://antionline.com/showthread.php?t=238136&amp;page=2</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GNUCITIZEN &#187; Persistent CSRF and The Hotlink Hell</title>
		<link>http://michaeldaw.org/papers/hotlink_persistent_csrf/comment-page-1#comment-20501</link>
		<dc:creator>GNUCITIZEN &#187; Persistent CSRF and The Hotlink Hell</dc:creator>
		<pubDate>Mon, 16 Apr 2007 15:05:14 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/hotlink_persistent_csrf/#comment-20501</guid>
		<description>[...] Earlier today, I and David K had a play around with these type of issues. I recommend reading his post too. poc: Google Reader Persistent CSRF Proof of Concept   &#187; trackback &#124; &#187; digg it &#124; [...]</description>
		<content:encoded><![CDATA[<p>[...] Earlier today, I and David K had a play around with these type of issues. I recommend reading his post too. poc: Google Reader Persistent CSRF Proof of Concept   &raquo; trackback | &raquo; digg it | [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
