<?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>WordPress Revamp &#187; security</title>
	<atom:link href="http://www.wordpressrevamp.com/category/security/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wordpressrevamp.com</link>
	<description>Leverage the Power of WordPress for Your Business</description>
	<lastBuildDate>Wed, 05 May 2010 15:19:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<image>
<link>http://www.wordpressrevamp.com</link>
<url>http://www.dragonwyze.com/wordpressrevamp/wp-content/plugins/maxblogpress-favicon/icons/favicon.ico</url>
<title>WordPress Revamp</title>
</image>
		<item>
		<title>Two Things You Can Do to Make Your WordPress Blog More Secure</title>
		<link>http://www.wordpressrevamp.com/learningcenter/more-secure-blog</link>
		<comments>http://www.wordpressrevamp.com/learningcenter/more-secure-blog#comments</comments>
		<pubDate>Sun, 11 Jan 2009 00:54:52 +0000</pubDate>
		<dc:creator>Carma</dc:creator>
				<category><![CDATA[Learning Center]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[blog security]]></category>
		<category><![CDATA[hacker-proofing]]></category>
		<category><![CDATA[secure wordpress install]]></category>

		<guid isPermaLink="false">http://www.wordpressrevamp.com/?p=195</guid>
		<description><![CDATA[There are two things you can do that will make your self-hosted blog harder to hack into and, if you do these two steps during your initial install, they are pretty easy to do.
1. Change the database pre-fix in the configuration file.
While you&#8217;re adding in your MySQL database information in the wp-config.php file, why not [...]]]></description>
			<content:encoded><![CDATA[<p>There are two things you can do that will make your self-hosted blog harder to hack into and, if you do these two steps during your initial install, they are pretty easy to do.</p>
<h3>1. Change the database pre-fix in the configuration file.</h3>
<p>While you&#8217;re adding in your MySQL database information in the wp-config.php file, why not take one more step to make it more difficult for hackers to screw with your site?</p>
<p>Look for the line of code that says, &#8220;$table_prefix  = wp_&#8217;;&#8221;. Then, change the &#8220;wp&#8221; to something else. It can be a random selection of letters and numbers. For example, you could change it to &#8220;d83Vwp.&#8221;</p>
<p>When WordPress creates your database, it creates a bunch of tables with the &#8220;wp_&#8221; prefix. What you did with this step is change that so hackers won&#8217;t know what your database tables are called.</p>
<p>This step can also be used to install more than one WordPress website using the same MySQL database.</p>
<p><strong>What if you already installed WordPress with the standard prefix?</strong><br />
You can still go in and change the prefix, but it is a tricky operation and you should backup your database before doing it. You really should know what you&#8217;re doing, or hire someone who does.</p>
<h3>Delete the &#8220;admin&#8221; user</h3>
<p>All WordPress websites start off with the administrative user being called &#8220;admin&#8221;. So, all a hacker has to do is guess what your password is! To prevent this from happening, create a new user with administrative level permissions, log in as that user and delete the &#8220;admin&#8221; user.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wordpressrevamp.com/learningcenter/more-secure-blog/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
