<?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: Reliably Detecting The WordPress Version</title>
	<atom:link href="http://w-shadow.com/blog/2009/12/02/detect-wordpress-version/feed/" rel="self" type="application/rss+xml" />
	<link>http://w-shadow.com/blog/2009/12/02/detect-wordpress-version/</link>
	<description>Slightly Advanced Computer Stuff (and some magic)</description>
	<lastBuildDate>Fri, 10 Sep 2010 12:00:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Kawamonkey</title>
		<link>http://w-shadow.com/blog/2009/12/02/detect-wordpress-version/comment-page-1/#comment-33719</link>
		<dc:creator>Kawamonkey</dc:creator>
		<pubDate>Tue, 16 Feb 2010 11:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1519#comment-33719</guid>
		<description>Just with regards to CSS version data checking, this is coincidentally removed when using WP-Minify or other script compressors, and I&#039;ve also personally written a plugin to remove version strings in normal situations. Still not common though :)

Interesting to see about the version-specific files technique, I never really considered that one and it&#039;s the only vulnerability I know my blog has now, which more annoyingly is extremely difficult to cover. Ah well...</description>
		<content:encoded><![CDATA[<p>Just with regards to CSS version data checking, this is coincidentally removed when using WP-Minify or other script compressors, and I&#8217;ve also personally written a plugin to remove version strings in normal situations. Still not common though <img src='http://w-shadow.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Interesting to see about the version-specific files technique, I never really considered that one and it&#8217;s the only vulnerability I know my blog has now, which more annoyingly is extremely difficult to cover. Ah well&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
