<?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>Root777 &#187; WordPress</title>
	<atom:link href="http://www.root777.com/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.root777.com</link>
	<description>Computer Security &#38; Technology</description>
	<lastBuildDate>Tue, 27 Jul 2010 02:25:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<image>
  <link>http://www.root777.com</link>
  <url>http://www.root777.com/favicon.ico</url>
  <title>Root777</title>
</image>
		<item>
		<title>Solution to Error 500 after upgrading to WordPress 2.7</title>
		<link>http://www.root777.com/wordpress/solution-to-error-500-after-upgrading-to-wordpress-27/</link>
		<comments>http://www.root777.com/wordpress/solution-to-error-500-after-upgrading-to-wordpress-27/#comments</comments>
		<pubDate>Tue, 30 Dec 2008 04:02:00 +0000</pubDate>
		<dc:creator>Ajit Gaddam</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[1&1]]></category>
		<category><![CDATA[wordpress error]]></category>

		<guid isPermaLink="false">http://www.root777.com/?p=111</guid>
		<description><![CDATA[After I recently upgraded my blog to the latest version of WordPress v2.7, I noticed an Error 500 &#8211; Internal server error. This seems to be a problem for WordPress blogs which are hosted by 1&#38;1 The solution to the Error 500 &#8211; Internal Server error 1. Create a file called &#8220;php.ini&#8221; in the /wp-admin/ [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>After I recently upgraded my blog to the latest version of WordPress v2.7, I noticed an Error 500 &#8211; Internal server error.</p>
<p>This seems to be a problem for WordPress blogs which are hosted by 1&amp;1</p>
<p>The solution to the Error 500 &#8211; Internal Server error</p>
<p>1. Create a file called &#8220;php.ini&#8221; in the /wp-admin/ directory of your blog</p>
<p>2. In the file add the text &#8220;memory = 20MB&#8221; without the quotes</p>
<p>This should fix the problem</p>
<img src="http://www.root777.com/?ak_action=api_record_view&id=111&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.root777.com/wordpress/solution-to-error-500-after-upgrading-to-wordpress-27/feed/</wfw:commentRss>
		<slash:comments>20</slash:comments>
		</item>
		<item>
		<title>WordPress Security Tips to protect your WordPress Blog</title>
		<link>http://www.root777.com/wordpress/wordpress-security-tips-to-protect-your-wordpress-blog/</link>
		<comments>http://www.root777.com/wordpress/wordpress-security-tips-to-protect-your-wordpress-blog/#comments</comments>
		<pubDate>Sat, 19 Jan 2008 16:16:56 +0000</pubDate>
		<dc:creator>Ajit Gaddam</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[security tips]]></category>

		<guid isPermaLink="false">http://www.root777.com/wordpress/wordpress-security-tips-to-protect-your-wordpress-blog/</guid>
		<description><![CDATA[While WordPress in general is pretty secure grounds up, it is still vulnerable to the many kinds of security exploits out there. WordPress Security Tip # 1: Upgrade your WordPress Blog Keeping your WordPress blog up to date by installing the latest version of WordPress. You may think it is pain to update every time, [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>While WordPress in general is pretty secure grounds up, it is still vulnerable to the many kinds of security exploits out there.</p>
<h3>WordPress Security Tip # 1: Upgrade your WordPress Blog</h3>
<p>Keeping your WordPress blog up to date by installing the <a href="http://wordpress.org/download/" title="download latest version of WordPress" target="_blank">latest version of WordPress</a>. You may think it is pain to update every time, but in terms of security and if you don&#8217;t want your blog to be hacked, this is very very crucial.</p>
<p>WordPress has <a href="http://codex.wordpress.org/Upgrading_WordPress_Extended" title="upgrading wordpress detailed instructions" target="_blank">detailed</a> and <a href="http://codex.wordpress.org/Upgrading_WordPress" title="upgrading wordpress" target="_blank">simple</a> instructions on how to update your blog. Check them out and keep your blog up-to-date. You can subscribe to the WordPress Development blog at <a href="http://wordpress.org/development/feed/" title="wordpress feed" target="_blank">http://wordpress.org/development/feed/</a> which will keep you up-to-date on the latest WordPress patches or the latest WordPress releases.</p>
<h3>WordPress Security Tip # 2: Remove the version string in your header.php file of your WordPress theme</h3>
<p>Again, if you don&#8217;t keep your WordPress blog up-to-date with the latest version, WordPress is kind enough to let potential hackers know that you did not update your blog. Say, you want to find a list of WordPress blogs still running WordPress 2.2, a simple <a href="http://www.google.com/search?hl=en&amp;safe=active&amp;q=content%3D%22WordPress+2.2%22" title="wordpress 2.2 blogs" target="_blank">google search</a> would generate a list.</p>
<p><span id="more-12"></span>Every WordPress theme, in its header.php file has a line that goes</p>
<blockquote><p><em>&lt;meta name=&#8221;generator&#8221; content=&#8221;WordPress &lt;?php bloginfo(&#8216;version&#8217;); ?&gt;&#8221; /&gt; &lt;!-– leave this for stats please &#8211;&gt;</em></p></blockquote>
<p>Make sure that you remove this line from the header.php file of your WordPress theme and prevent any attackers from exploiting an older version of WordPress.</p>
<h3>WordPress Security Tip # 3: Secure your /wp-admin/ folder</h3>
<p><strong> a. .htaccess file:</strong></p>
<p>After editing your .htaccess file, any attempts to access your wp-admin folder will be shown a Forbidden error message. Note: For this method, you need to create a new .htaccess file in your wp-admin folder and not simply replace/edit the .htaccess file in the root folder of your WordPress blog.</p>
<blockquote><p>AuthUserFile /dev/null<br />
AuthGroupFile /dev/null<br />
AuthName “Root777 Access Control”<br />
AuthType Basic<br />
&lt;LIMIT GET&gt;<br />
order deny,allow<br />
deny from all<br />
# whitelist home IP address<br />
allow from 74.208.41.219<br />
# whitelist work IP address<br />
allow from 74.208.59.150<br />
&lt;/LIMIT&gt;</p></blockquote>
<p>This method is very good for those with a static IP address. You can <a href="http://whatismyipaddress.com/" title="find out your IP address" target="_blank">find out your IP address here</a> and replace the IP address shown above with your IP address. If you have multiple authors to your blog, you can add their IP addresses too to this whitelist.</p>
<p><strong>b. Use Login Lockdown plugin:</strong></p>
<p>If you have a dynamic IP address though, locking down access to your /wp-admin/ folder will not work by allowing access only from certain IP address. In such a situation, use <a href="http://www.bad-neighborhood.com/login-lockdown.html" title="Login Lockdown plugin" target="_blank">Login Lockdown plugin</a> which will help in preventing attackers trying to brute force their login.</p>
<p>Any failed login attempts will be recorded. You can also set the number or threshold for failed logins where an IP range can be blocked (an hour by default)</p>
<p><img src="http://farm3.static.flickr.com/2097/2204087370_7d6dbb6086_o.png" alt="login lockout" align="absmiddle" height="297" width="373" /></p>
<p><strong>c. Use robots.txt</strong></p>
<p>Ryan lists an excellent <a href="http://www.techcounter.com/seo/increase-search-engine-rankings-and-prevent-duplicate-content-using-robotstxt/" title="seo optimized robots.txt" target="_blank">SEO Optimized robots.txt file for a WordPress blog.</a> Simply copy the robots.txt file below which also includes a Disallow /wp-* which will prevent any of your WordPress files from being indexed by Google or any other search engines. Note: The robots.txt file below includes exceptions which allows the google image bot, adsense bot and any other bots to index the content.</p>
<blockquote><p>User-agent: *<br />
# disallow all files in these WordPress directories<br />
Disallow: /wp-content/<br />
Disallow: /wp-admin/<br />
Disallow: /wp-includes/<br />
Disallow: /wp-</p>
<p># disallow all files in these directories<br />
Disallow: /tag/<br />
Disallow: /cgi-bin/</p>
<p># disallow robots from parsing individual post feeds and trackbacks<br />
Disallow: /feed/<br />
Disallow: /trackback/<br />
Disallow: */trackback*</p>
<p># disallow any files that are stats related<br />
Disallow: /stats*<br />
Disallow: /about/legal-notice/<br />
Disallow: /about/copyright-policy/<br />
Disallow: /about/terms-and-conditions/<br />
Disallow: /tag<br />
Disallow: /docs*<br />
Disallow: /manual*<br />
Disallow: /category/uncategorized*</p>
<p># disallow files ending with the following extensions<br />
User-agent: Googlebot<br />
Disallow: /*.php$<br />
Disallow: /*.js$<br />
Disallow: /*.inc$<br />
Disallow: /*.css$<br />
Disallow: /*.gz$<br />
Disallow: /*.cgi$<br />
Disallow: /*.wmv$<br />
Disallow: /*.php*<br />
Disallow: /*.gz$<br />
Allow: /wp-content/uploads/</p>
<p>#disallow WayBack archiving site<br />
User-agent: ia_archiver<br />
Disallow: /</p>
<p># allow google image bot to search all images<br />
User-agent: Googlebot-Image<br />
Disallow:<br />
Allow: /*</p>
<p># allow adsense bot on entire site<br />
User-agent: Mediapartners-Google*<br />
Disallow: /*?*<br />
Allow: /*</p></blockquote>
<h3>WordPress Security Tip # 4: Change default password to your WordPress blog</h3>
<p>When you create your WordPress blog for the first time, WordPress generates a simple 6 character password with just numbers and letters. You not only need to change the default password, but create a strong password. Learn more on how you can <a href="http://www.root777.com/computer-security/how-to-create-a-strong-password/" title="how to create a strong password" target="_blank">create a strong password</a>.</p>
<h3>WordPress Security Tip # 5: Put a blank index.html in your WordPress Plugins Folder</h3>
<p>If you type in yourwordpressblog.com/wp-content/plugins/, you can see a list of all your installed WordPress plugins. If someone wanted to hack your blog, they can run exploits on any out-of-date plugin on your blog.</p>
<p>To solve this problem, add a blank index.html to your WordPress plugins folder. This will show a blank page whenever someone attempts to view the list of plugins on your blog.</p>
<p>Thanks to <a href="http://www.mattcutts.com/blog/three-tips-to-protect-your-wordpress-installation/" title="Matt Cutts WordPress security tips" target="_blank">Matt Cutts</a> for inspiring this article. Hopefully these tips will allow for more secure and safe blogging.</p>
<img src="http://www.root777.com/?ak_action=api_record_view&id=12&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.root777.com/wordpress/wordpress-security-tips-to-protect-your-wordpress-blog/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.476 seconds -->
