<?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: More RSS Stuff (I&#8217;m still not convinced)</title>
	<atom:link href="http://www.securitycurve.com/wordpress/archives/426/feed" rel="self" type="application/rss+xml" />
	<link>http://www.securitycurve.com/wordpress/archives/426?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=more-rss-stuff-im-still-not-convinced</link>
	<description></description>
	<lastBuildDate>Fri, 10 Sep 2010 11:39:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ed</title>
		<link>http://www.securitycurve.com/wordpress/archives/426/comment-page-1#comment-32</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Thu, 10 Aug 2006 12:14:34 +0000</pubDate>
		<guid isPermaLink="false">http://securitycurve.com/wordpress/?p=426#comment-32</guid>
		<description>Micheal,

Well, I&#039;ll buy that.  I think there are a few factors: RSS readers are more diverse than web browsers; for example, just looking at traffic statistics, most web browsers seem to be either firefox or IE (on various platforms, but still those two), whereas there are at least 10 different RSS readers in play (SharpReader, RSS Reader, Bloglines, etc.)  So, probably at least one or two of those clients are implementing functionality that&#039;s dangerous according to the paper.

But I guess my point is that I don&#039;t think the problem is RSS itself - it could be a vector for nastiness in the way that SPI describes - but not because of an inherent problem in RSS, but because of the way it&#039;s implemented...  By analogy, the recent bugs in IE pointed out by HD Moore make browsing more risky, but because of the browser implementation, not because of an inherent problem with HTML.  I think the same is true of RSS...

Anyway, I guess this is a controversial opinion, but as always I reserve the right to be totally wrong.  :-)

-E
</description>
		<content:encoded><![CDATA[<p>Micheal,</p>
<p>Well, I&#8217;ll buy that.  I think there are a few factors: RSS readers are more diverse than web browsers; for example, just looking at traffic statistics, most web browsers seem to be either firefox or IE (on various platforms, but still those two), whereas there are at least 10 different RSS readers in play (SharpReader, RSS Reader, Bloglines, etc.)  So, probably at least one or two of those clients are implementing functionality that&#8217;s dangerous according to the paper.</p>
<p>But I guess my point is that I don&#8217;t think the problem is RSS itself &#8211; it could be a vector for nastiness in the way that SPI describes &#8211; but not because of an inherent problem in RSS, but because of the way it&#8217;s implemented&#8230;  By analogy, the recent bugs in IE pointed out by HD Moore make browsing more risky, but because of the browser implementation, not because of an inherent problem with HTML.  I think the same is true of RSS&#8230;</p>
<p>Anyway, I guess this is a controversial opinion, but as always I reserve the right to be totally wrong.  <img src='http://www.securitycurve.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>-E</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael R. Farnum</title>
		<link>http://www.securitycurve.com/wordpress/archives/426/comment-page-1#comment-31</link>
		<dc:creator>Michael R. Farnum</dc:creator>
		<pubDate>Wed, 09 Aug 2006 20:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://securitycurve.com/wordpress/?p=426#comment-31</guid>
		<description>I agree with your last paragraph except for &quot;I don&#039;t think it&#039;s likely that it&#039;ll be a common attack vector in general.&quot;  As common and popular as blogs are, I can easily see it becoming an attack vector for someone trying to create a botnet.  Many people spend a lot of time blog hopping, just looking for some cool new blogs.  The free blog services facilitate that hopping with the usual bars at the top of the screen.

With so many people who have no idea what they are doing throwing togtether blogs and not controlling comments, you may have a very easy way for bad guys to infect machines.  And you can&#039;t always depend on the blog provider to stop it for you.
</description>
		<content:encoded><![CDATA[<p>I agree with your last paragraph except for &#8220;I don&#8217;t think it&#8217;s likely that it&#8217;ll be a common attack vector in general.&#8221;  As common and popular as blogs are, I can easily see it becoming an attack vector for someone trying to create a botnet.  Many people spend a lot of time blog hopping, just looking for some cool new blogs.  The free blog services facilitate that hopping with the usual bars at the top of the screen.</p>
<p>With so many people who have no idea what they are doing throwing togtether blogs and not controlling comments, you may have a very easy way for bad guys to infect machines.  And you can&#8217;t always depend on the blog provider to stop it for you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
