<?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: Securing Your WordPress Installation</title>
	<atom:link href="http://cartierconsulting.com/2010/03/securing-your-wordpress-installation/feed/" rel="self" type="application/rss+xml" />
	<link>http://cartierconsulting.com/2010/03/securing-your-wordpress-installation/</link>
	<description>computers, networking, web sites and more...</description>
	<lastBuildDate>Thu, 15 Sep 2011 22:57:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan</title>
		<link>http://cartierconsulting.com/2010/03/securing-your-wordpress-installation/comment-page-1/#comment-24</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 11 Mar 2010 17:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://cartierconsulting.com/?p=1384#comment-24</guid>
		<description>@ Steve:

Glad you liked the article.  One of the security plugins I suggested, &lt;a href=&quot;http://how-to-blog.tv/security/wp-malwatch/&quot; title=&quot;WP-MalWatch&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;&lt;strong&gt;WP-MalWatch&lt;/strong&gt;&lt;/a&gt;, can scan your &lt;strong&gt;wp-uploads&lt;/strong&gt; folder automatically.  Adding an .htaccess file with file type limitations might also help.  See each plugin&#039;s site for more details on the implementation of this...

-Dan</description>
		<content:encoded><![CDATA[<p>@ Steve:</p>
<p>Glad you liked the article.  One of the security plugins I suggested, <a href="http://how-to-blog.tv/security/wp-malwatch/" title="WP-MalWatch" target="_blank" rel="nofollow"><strong>WP-MalWatch</strong></a>, can scan your <strong>wp-uploads</strong> folder automatically.  Adding an .htaccess file with file type limitations might also help.  See each plugin&#8217;s site for more details on the implementation of this&#8230;</p>
<p>-Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Swardello</title>
		<link>http://cartierconsulting.com/2010/03/securing-your-wordpress-installation/comment-page-1/#comment-23</link>
		<dc:creator>Swardello</dc:creator>
		<pubDate>Thu, 11 Mar 2010 16:36:40 +0000</pubDate>
		<guid isPermaLink="false">http://cartierconsulting.com/?p=1384#comment-23</guid>
		<description>Great tips!  I tried using an htacess file in my wp-content directory but it broke the built-in image uploader. You didn&#039;t say to put one there, but I think that&#039;s one of the most vulnerable folders.

Thank you for the great information!
Steve</description>
		<content:encoded><![CDATA[<p>Great tips!  I tried using an htacess file in my wp-content directory but it broke the built-in image uploader. You didn&#8217;t say to put one there, but I think that&#8217;s one of the most vulnerable folders.</p>
<p>Thank you for the great information!<br />
Steve</p>
]]></content:encoded>
	</item>
</channel>
</rss>

