<?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: How to Secure Your New WordPress&#160;Installation</title>
	<atom:link href="http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/feed/" rel="self" type="application/rss+xml" />
	<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/</link>
	<description>Learn how to take your WordPress skills to the next level.</description>
	<lastBuildDate>Mon, 22 Mar 2010 13:46:20 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: site fr</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-3192</link>
		<dc:creator>site fr</dc:creator>
		<pubDate>Sun, 24 Jan 2010 17:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-3192</guid>
		<description>un tres bon article, merci pour cet info .</description>
		<content:encoded><![CDATA[<p>un tres bon article, merci pour cet info .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WPbud</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-3134</link>
		<dc:creator>WPbud</dc:creator>
		<pubDate>Fri, 15 Jan 2010 04:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-3134</guid>
		<description>Thank you for sharing. Very useful tips.
Will follow.</description>
		<content:encoded><![CDATA[<p>Thank you for sharing. Very useful tips.<br />
Will follow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Starr</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2445</link>
		<dc:creator>Jeff Starr</dc:creator>
		<pubDate>Tue, 24 Nov 2009 05:32:47 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2445</guid>
		<description>It depends on your server configuration. 400 permissions for the wp-config.php means that only the user (i.e., server) is able to read (and only read) the contents of the file. Aside from 0 (no access), a 400 setting is the most restrictive permissions level possible. Unfortunately, depending on how users are set up on the server account, it may be &lt;em&gt;too&lt;/em&gt; restrictive.</description>
		<content:encoded><![CDATA[<p>It depends on your server configuration. 400 permissions for the wp-config.php means that only the user (i.e., server) is able to read (and only read) the contents of the file. Aside from 0 (no access), a 400 setting is the most restrictive permissions level possible. Unfortunately, depending on how users are set up on the server account, it may be <em>too</em> restrictive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hoff - WP Blog Host</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2419</link>
		<dc:creator>John Hoff - WP Blog Host</dc:creator>
		<pubDate>Sat, 21 Nov 2009 20:38:14 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2419</guid>
		<description>That sounds like good advice. I haven&#039;t tried it yet though. You sure WordPress doesn&#039;t have any issues with it?</description>
		<content:encoded><![CDATA[<p>That sounds like good advice. I haven&#8217;t tried it yet though. You sure WordPress doesn&#8217;t have any issues with it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hoff - WP Blog Host</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2418</link>
		<dc:creator>John Hoff - WP Blog Host</dc:creator>
		<pubDate>Sat, 21 Nov 2009 20:36:56 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2418</guid>
		<description>I definitely disagree with that statement.

Changing your database prefix to something other than wp_ could be considered security through obscurity. 

I&#039;ve seen through email alerts I have set up that someone tried to hack into one of my blogs through SQL Injection. They tried &quot;guessing&quot; that my database prefix was wp_. 

They were wrong.

And if it were wp_, they just may of had a chance at cracking in.</description>
		<content:encoded><![CDATA[<p>I definitely disagree with that statement.</p>
<p>Changing your database prefix to something other than wp_ could be considered security through obscurity. </p>
<p>I&#8217;ve seen through email alerts I have set up that someone tried to hack into one of my blogs through SQL Injection. They tried &#8220;guessing&#8221; that my database prefix was wp_. </p>
<p>They were wrong.</p>
<p>And if it were wp_, they just may of had a chance at cracking in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hoff - WP Blog Host</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2417</link>
		<dc:creator>John Hoff - WP Blog Host</dc:creator>
		<pubDate>Sat, 21 Nov 2009 20:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2417</guid>
		<description>Urda, SEO Egghead has a very simple plugin to do this for you: http://www.seoegghead.com/software/wordpress-table-rename.seo

To do it manually, you&#039;d have to export your database to your computer, open it up with a text editor, and do a find and replace for all instances of wp_ with something else.....like clRE83f_ or something.

Then head over to the wp-config file and change the wp_ value listed in there to the one you changed it in.

Upload your new database and you&#039;re done.

Always always always back up your database first. In fact, make a copy of the back up so you have a backup of the backup! LOL</description>
		<content:encoded><![CDATA[<p>Urda, SEO Egghead has a very simple plugin to do this for you: <a href="http://www.seoegghead.com/software/wordpress-table-rename.seo" rel="nofollow">http://www.seoegghead.com/software/wordpress-table-rename.seo</a></p>
<p>To do it manually, you&#8217;d have to export your database to your computer, open it up with a text editor, and do a find and replace for all instances of wp_ with something else&#8230;..like clRE83f_ or something.</p>
<p>Then head over to the wp-config file and change the wp_ value listed in there to the one you changed it in.</p>
<p>Upload your new database and you&#8217;re done.</p>
<p>Always always always back up your database first. In fact, make a copy of the back up so you have a backup of the backup! LOL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deb Phillips</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2357</link>
		<dc:creator>Deb Phillips</dc:creator>
		<pubDate>Sat, 14 Nov 2009 08:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2357</guid>
		<description>I have a quick question regarding protecting the &lt;code&gt;wp-admin&lt;/code&gt; directory.

Since I&#039;m not a coding expert, would someone mind clarifying how the &quot;&lt;code&gt;/full/path/.htaccess&lt;/code&gt;&quot; should be modified if I&#039;ve placed the recommended .htaccess file above the &lt;code&gt;public_html&lt;/code&gt; folder?

My blog is in a directory immediately below the &lt;code&gt;public_html&lt;/code&gt; folder. The &lt;code&gt;public_html&lt;/code&gt; directory is in the root of the website. I hope I&#039;m being clear enough!

Thanks for your patience and help!

Deb</description>
		<content:encoded><![CDATA[<p>I have a quick question regarding protecting the <code>wp-admin</code> directory.</p>
<p>Since I&#8217;m not a coding expert, would someone mind clarifying how the &#8220;<code>/full/path/.htaccess</code>&#8221; should be modified if I&#8217;ve placed the recommended .htaccess file above the <code>public_html</code> folder?</p>
<p>My blog is in a directory immediately below the <code>public_html</code> folder. The <code>public_html</code> directory is in the root of the website. I hope I&#8217;m being clear enough!</p>
<p>Thanks for your patience and help!</p>
<p>Deb</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: silvers</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2339</link>
		<dc:creator>silvers</dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:55:07 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2339</guid>
		<description>wow just realised that it&#039;s Jeff that posted it. 

sorry jeff, you deserve the praise and maybe i&#039;ve just found a new webguy hero to worship!

nice one mate!</description>
		<content:encoded><![CDATA[<p>wow just realised that it&#8217;s Jeff that posted it. </p>
<p>sorry jeff, you deserve the praise and maybe i&#8217;ve just found a new webguy hero to worship!</p>
<p>nice one mate!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: silvers</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2338</link>
		<dc:creator>silvers</dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2338</guid>
		<description>totally fucking sweet!!!

really really helpful stuff here. i didn&#039;t really used to bother with protecting my sites cos i am new to it all and was just happy to get it up online. but now that i have got in to it all, this will be really useful if/when i end up making a wordpress site for a company, or in fact one for myself now that i am not such a noob.

another awesome post. you&#039;re like superman or something. clarke coyier? chris kent?</description>
		<content:encoded><![CDATA[<p>totally fucking sweet!!!</p>
<p>really really helpful stuff here. i didn&#8217;t really used to bother with protecting my sites cos i am new to it all and was just happy to get it up online. but now that i have got in to it all, this will be really useful if/when i end up making a wordpress site for a company, or in fact one for myself now that i am not such a noob.</p>
<p>another awesome post. you&#8217;re like superman or something. clarke coyier? chris kent?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://digwp.com/2009/11/how-to-secure-your-new-wordpress-installation/#comment-2337</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=903#comment-2337</guid>
		<description>Nice tips! We also listed some small security tips on our blog at http://wpengineer.com/small-security-tipps-for-your-wordpress-install/ a week ago.

Some vary from this list but some are the same. Funny that we had the same idea within a week. :)</description>
		<content:encoded><![CDATA[<p>Nice tips! We also listed some small security tips on our blog at <a href="http://wpengineer.com/small-security-tipps-for-your-wordpress-install/" rel="nofollow">http://wpengineer.com/small-security-tipps-for-your-wordpress-install/</a> a week ago.</p>
<p>Some vary from this list but some are the same. Funny that we had the same idea within a week. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
