<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>My Thoughts &#187; Securing</title>
	<atom:link href="http://blog.avirtualhome.com/tag/securing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.avirtualhome.com</link>
	<description>Just my thoughts about things</description>
	<lastBuildDate>Wed, 01 Feb 2012 12:59:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Securing WordPress &#8211; Part 2 addendum</title>
		<link>http://blog.avirtualhome.com/2008/01/22/securing-wordpress-part-2-addendum/</link>
		<comments>http://blog.avirtualhome.com/2008/01/22/securing-wordpress-part-2-addendum/#comments</comments>
		<pubDate>Tue, 22 Jan 2008 19:40:31 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[htaccess file]]></category>
		<category><![CDATA[Securing]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blog.avirtualhome.com/2008/01/22/securing-wordpress-part-2-addendum/</guid>
		<description><![CDATA[On January 17th I posted a new way to enhance security for WordPress. I discovered a small problem with the final htaccess file and WordPress updating the file. I wrote the final htaccess file would look like this: Options All -Indexes # BEGIN WordPress &#60;IfModule mod_rewrite.c&#62; RewriteEngine On RewriteBase / RewriteCond %{THE_REQUEST} /(wp-includes&#124;wp-content)/.*\ HTTP/ RewriteCond [...]]]></description>
		<wfw:commentRss>http://blog.avirtualhome.com/2008/01/22/securing-wordpress-part-2-addendum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Securing WordPress &#8211; Part 2</title>
		<link>http://blog.avirtualhome.com/2008/01/17/securing-wordpress-part-2/</link>
		<comments>http://blog.avirtualhome.com/2008/01/17/securing-wordpress-part-2/#comments</comments>
		<pubDate>Thu, 17 Jan 2008 17:40:30 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[htaccess file]]></category>
		<category><![CDATA[Securing]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blog.avirtualhome.com/2008/01/17/securing-wordpress-part-2/</guid>
		<description><![CDATA[After talking about the article on blogsecurity.net about securing WordPress and giving you some errata on the article I spend a little more time to enhance the security. htaccess enhancements Blogsecurity suggest to put in the directories /wp-content/ and /wp-includes/ a htaccess file with the following content: Order Allow,Deny Deny from all &#60;Files ~ ".(css&#124;jpe?g&#124;png&#124;gif&#124;js)$"&#62; [...]]]></description>
		<wfw:commentRss>http://blog.avirtualhome.com/2008/01/17/securing-wordpress-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Securing WordPress</title>
		<link>http://blog.avirtualhome.com/2008/01/15/securing-wordpress/</link>
		<comments>http://blog.avirtualhome.com/2008/01/15/securing-wordpress/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 03:06:19 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[Securing]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blog.avirtualhome.com/2008/01/15/securing-wordpress/</guid>
		<description><![CDATA[If you host your own WordPress blog and not use a blogging site like WordPress.com it is important you secure your installation. On blogsecurity.net there&#8217;s an article on how to secure WordPress. It&#8217;s very well documented but I ran into one difference. They say: Now you need to replace two other values in this table: [...]]]></description>
		<wfw:commentRss>http://blog.avirtualhome.com/2008/01/15/securing-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

