<?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>PF&#38;Investing &#187; wordpress</title>
	<atom:link href="http://pfinvesting.com/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://pfinvesting.com</link>
	<description>common sense in personal finance and investing</description>
	<lastBuildDate>Sun, 27 Mar 2011 01:04:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How to secure your WordPress blog</title>
		<link>http://pfinvesting.com/2008/05/05/secure-wordpress/</link>
		<comments>http://pfinvesting.com/2008/05/05/secure-wordpress/#comments</comments>
		<pubDate>Mon, 05 May 2008 13:00:46 +0000</pubDate>
		<dc:creator>Roy</dc:creator>
				<category><![CDATA[Blogging Tips]]></category>
		<category><![CDATA[backup wordpress]]></category>
		<category><![CDATA[harden wordpress]]></category>
		<category><![CDATA[Matt Mullenweg]]></category>
		<category><![CDATA[secure wordpress]]></category>
		<category><![CDATA[upgrade wordpress]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wordpress plugin]]></category>

		<guid isPermaLink="false">http://localhost/2008/05/05/secure-wordpress/</guid>
		<description><![CDATA[Here I put together a collection of tips and suggestions about securing your WordPress blog.]]></description>
			<content:encoded><![CDATA[<p>(This post belongs to the series <a title="About blogging" href="http://pfinvesting.com/2008/04/14/about-blogging/">About blogging</a>.)</p>
<p>Securing a <a title="WordPress" href="http://wordpress.org/" target="_blank">WordPress</a>-powered blog is one of the most pressing concerns of newbie and pro bloggers alike (several horror stories are doing rounds <a title="WordPress Troubleshooting Forum" href="http://wordpress.org/support/forum/3" target="_blank">here</a>). I have done my own research on this topic, and here put together a list of some of the popular suggestions and tips to secure your WordPress blog.<br />
<span id="more-94"></span></p>
<p>First thing you must do, before getting to the list, is carefully read <a title="Harden your WordPress" href="http://codex.wordpress.org/Hardening_WordPress" target="_blank">Hardening WordPress</a>. <img title="key" src="/images/key.jpg" alt="key" width="306" height="178" align="right" />Needless to say, many of the suggestions below are already included there.</p>
<p>Now to the list:</p>
<p><strong>1. Upgrade</strong>. This is the most important word in WordPress security. Because WordPress does not release bugfix patches, all fixes are incorporated in the next full version release (which causes frequent new releases, to stay current with the latest security issues). So, it is usually a good idea to <a title="WordPress download" href="http://wordpress.org/download/" target="_blank">download</a> and <a title="upgrade WordPress" href="http://codex.wordpress.org/Upgrading_WordPress" target="_blank">install</a> the most recent version as soon as it is released. You can even automate the process with <a title="WordPress automatic upgrade plugin" href="http://wordpress.org/extend/plugins/wordpress-automatic-upgrade/" target="_blank">automatic upgrade plugin</a>.</p>
<p>Unfortunately, many WordPress users (including me) find it hard to keep up with such frequent upgrades, mainly because <a title="WordPress Plugins" href="http://wordpress.org/extend/plugins/" target="_blank">plugin</a> authors do not always release compatible plugins fast enough, and such mismatch can break your otherwise smoothly running blog. (Matt Mullenweg has <a title="Matt on securing WordPress" href="http://ma.tt/2008/04/securityfocus-sql-injection-bogus/" target="_blank">something to say</a> about this though.)</p>
<p>Another thing is that after each major version release of the type 2.x.x&#8212;&gt;2.y (like 2.3.3&#8212;&gt;2.5), there is a spike in reporting new bugs, and the next &#8220;minor&#8221; release 2.y.x usually fixes them (like the latest 2.5.1). It is a good idea to wait for this bugfix version, instead of grabbing the version 2.y itself.</p>
<p>Do keep in mind, though, that while upgrading helps prevent future hacking of your blog, it can do little to cure an already hacked blog. So, you must take additional precautions.</p>
<p><strong>2. Back up.</strong> This is the second-most important step in securing your blog. You must <a title="Back up WordPress" href="http://codex.wordpress.org/WordPress_Backups" target="_blank">back up</a> your entire blog, including databases and web site files, at least once a week. This will allow you to revert back to an older version if the blog is hacked. You will, though, lose the new posts and any site changes that you made since the last backup.</p>
<p>There are several options available for backing up your blog. Most blog hosting companies provide various backup services, and you should also take regular backups yourself and keep them on your  local computer. For database backup, you can either use <a title="database backup with phpMyAdmin" href="http://codex.wordpress.org/Backing_Up_Your_Database" target="_blank">phpMyAdmin</a> or <a title="database backup plugin" href="http://www.ilfilosofo.com/blog/wp-db-backup/" target="_blank">database backup plugin</a>. You can also use <a title="backup plugin" href="http://wordpress.designpraxis.at/plugins/backupwordpress/" target="_blank">this plugin</a> to back up both your database and web site files.</p>
<p>Besides upgrading and backing up, there are a number of <a title="secure yoru blog" href="http://www.bloganything.net/922/secure-your-wordpress-blog" target="_blank">little things</a> you should do to further protect your blog:</p>
<p><strong>3. Remove version string from &#8220;header.php&#8221;.</strong> From the admin panel, go to Presentation&#8211;&gt;Theme Editor&#8211;&gt;Header, and delete the generator line containing &#8220;&lt;?php bloginfo(&#8216;version&#8217;); ?&gt;&#8221;. This will remove the WordPress version number from the page source file, and can delay a hacker from exploiting any known security loophole in this version.</p>
<p>If you want to be <a title="remove version string from feed" href="http://www.reaper-x.com/2007/09/01/hardening-wordpress-with-mod-rewrite-and-htaccess/" target="_blank">more cautious</a>, you may also remove the generator line from &#8220;wp-includes/feed-*.php&#8221; files, so that the version number does more cautious not show on your WordPress feed either.</p>
<p>Even easier, use <a title="Replace WP-Version plugin" href="http://wordpress.org/extend/plugins/replace-wp-version/" target="_blank">this plugin</a> instead to do the job for you.</p>
<p><strong>4. Change default &#8220;admin&#8221; username.</strong> This is an important point, and yes, you <strong>can</strong> do this without touching your database, as I have discussed in <a title="change default admin username" href="http://pfinvesting.com/2008/04/17/how-to-change-your-wordpress-admin-username/">this post</a>.</p>
<p><strong>5. Copy .htaccess to /wp-admin directory.</strong> Use the FTP program of your hosting server&#8217;s file manager to copy the .htaccess file in your root directory to the /wp-admin directory. This sets the same access permission to your blog admin panel as your server login access, making sure that only the server owner/user can access this directory.</p>
<p>You can also use <a title="AskApache Password Protect plugin" href="http://www.askapache.com/wordpress/htaccess-password-protect.html" target="_blank">this plugin</a>, which adds an extra layer of security by requiring a username and password (different from your blog username) to access the wp-admin directory.</p>
<p><strong>6. Drop empty index.html file in /plugins directory.</strong> Create an empty &#8220;index.html&#8221; file in your text editor (make sure to set the file type to &#8220;All files&#8221;), and upload it to the wp-content/plugins directory. This will hide the content of this directory, and hence the plugins used by your blog, to any snooping outsider.</p>
<p><strong>7. Check all links in your blog.</strong> One way to know if your blog has been hacked is to check all outbound links for any spam redirection. You can do this by searching for &#8220;http://&#8221; in the source file of every page in your blog, making sure there is no funny link lurking anywhere. Firefox makes this job easy with Tools&#8211;&gt;Page Info&#8211;&gt;Links.</p>
<p><strong>8. Avoid sponsored themes.</strong> An easy way to get spam links in your blog is by installing an unknown 3rd party theme, instead of getting it from reliable sources (such as the WordPress <a title="WordPress themes" href="http://themes.wordpress.net/" target="_blank">theme repository</a>). Advertisers often pay theme developers to add outbound links promoting their sites, which can have all sorts of bad effects on your blog. Matt wrote about it <a title="Matt on sponsored themes" href="http://weblogtoolscollection.com/archives/2007/04/12/on-sponsored-themes/" target="_blank">here</a>.</p>
<p>I&#8217;ll add to this list if I come across any more security tip.</p>
]]></content:encoded>
			<wfw:commentRss>http://pfinvesting.com/2008/05/05/secure-wordpress/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to change your WordPress &#8220;admin&#8221; username</title>
		<link>http://pfinvesting.com/2008/04/17/change-wordpress-admin-username/</link>
		<comments>http://pfinvesting.com/2008/04/17/change-wordpress-admin-username/#comments</comments>
		<pubDate>Thu, 17 Apr 2008 17:56:01 +0000</pubDate>
		<dc:creator>Roy</dc:creator>
				<category><![CDATA[Blogging Tips]]></category>
		<category><![CDATA[harden wordpress]]></category>
		<category><![CDATA[secure wordpress]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://localhost/2008/04/17/how-to-change-your-wordpress-admin-username/</guid>
		<description><![CDATA[A simple way to change the default "admin" username from inside the WordPress admin panel, without having to access your database.]]></description>
			<content:encoded><![CDATA[<p>(This post belongs to the series <a title="about blogging" href="http://pfinvesting.com/2008/04/14/about-blogging/">About blogging</a>.)</p>
<p>A common question of many WordPress users is how to change the default &#8220;admin&#8221; username that WordPress assigns during installation, so that a hacker cannot easily break into the account. The standard &#8220;admin panel-&gt;users-&gt;edit user&#8221; does not let you do this, because your username is tied to your MySQL database access, and you need to make changes in the database itself. The steps are nicely explained <a title="Changing username with phpMyAdmin" href="http://dariablack.wordpress.com/2007/06/21/changing-your-wordpress-admin-user-name/" target="_blank">here</a>.<br />
<span id="more-91"></span></p>
<p>But some of you, like me, are probably squeamish about fiddling with databases, no matter how easy it seems. So I did some digging around to see if there is an even easier way, like doing it from inside the admin panel itself without worrying about databases. Everyone, <a title="Changing admin username" href="http://codex.wordpress.org/User:ringmaster/Hardening_WordPress#Rename_The_Administrative_Account" target="_blank">including WordPress</a>, seems to say this is not possible. But I found out that someone already posted a smart solution <a title="WordPress Forums" href="http://wordpress.org/support/topic/116054" target="_blank">here</a>, and wanted to share this with you.</p>
<p>This is all you need to do:</p>
<ol>
<li>Create a new user (panel-&gt;users-&gt;add user) with the username you would like, and give it &#8220;Administrator&#8221; privilege. You should also assign it same email address, website etc, if you are replacing the admin user with it.</li>
<li>Log out of the admin panel, and log back in with the new user.</li>
<li>Delete the &#8220;admin&#8221; user (panel-&gt;users-&gt;delete user). At the last step you will be reminded to switch all posts and links to the new user (you do <strong>not</strong> want to delete them too!). That&#8217;s it!</li>
</ol>
<p>If you want, you can confirm the new user in the database (phpMyAdmin-&gt;Databases-&gt;your database-&gt;wp_users-&gt;Browse).</p>
]]></content:encoded>
			<wfw:commentRss>http://pfinvesting.com/2008/04/17/change-wordpress-admin-username/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>About blogging</title>
		<link>http://pfinvesting.com/2008/04/14/about-blogging/</link>
		<comments>http://pfinvesting.com/2008/04/14/about-blogging/#comments</comments>
		<pubDate>Mon, 14 Apr 2008 22:34:27 +0000</pubDate>
		<dc:creator>Roy</dc:creator>
				<category><![CDATA[Blogging Tips]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://localhost/2008/04/14/blogging-about-blogging/</guid>
		<description><![CDATA[This is a list of posts I occasionally write on blogging with WordPress.]]></description>
			<content:encoded><![CDATA[<p>This is a blog about investing (and personal finance), and so, while investing is the primary subject here, from time to time I&#8217;ll also write about tips and tricks on blogging with <a title="WordPress" href="http://wordpress.org" target="_blank">WordPress</a>, which is the platform I use for this blog.<br />
<span id="more-95"></span></p>
<p>They will serve partly as a bookkeeping for me so I do not have to go searching for these tips on the Net again, and partly for those of you who would like to try them out on your own blog (the usual disclaimer &#8220;You are responsible so do not blame me&#8221; blah blah&#8230; holds).</p>
<p>These tips are mostly the stuff I pick up on Internet from other (and smarter) WordPress bloggers, and my own occasional hacks, about issues of security, design, optimization, and so on.</p>
<p>Here they are:</p>
<ol>
<li><strong><a title="How to change your WordPress admin username" href="http://pfinvesting.com/2008/04/17/change-wordpress-admin-username/">How to change your WordPress &#8220;admin&#8221; username</a>.</strong></li>
<li><strong><a title="How to secure your WordPress blog" href="http://pfinvesting.com/2008/05/05/secure-wordpress/">How to secure your WordPress blog</a>.</strong></li>
<li>&#8230;</li>
</ol>
<p>This list will grow as more posts are added.</p>
]]></content:encoded>
			<wfw:commentRss>http://pfinvesting.com/2008/04/14/about-blogging/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New home for this blog</title>
		<link>http://pfinvesting.com/2008/02/18/new-home/</link>
		<comments>http://pfinvesting.com/2008/02/18/new-home/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 15:42:23 +0000</pubDate>
		<dc:creator>Roy</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://localhost/2008/02/18/new-home-for-my-blog/</guid>
		<description><![CDATA[PF&#38;Investing is the new home for this blog. Initials &#8220;PF&#8221; stand for &#8220;Personal Finance&#8221;, which, along with the word &#8220;Investing&#8221;, sum up the blog&#8217;s content. The moving process went like a breeze, kudos to WordPress. As you notice, there is a significant lull in my posting activity (I wrote the last one on October 29, [...]]]></description>
			<content:encoded><![CDATA[<p><a title="PF&amp;Investing" href="http://pfinvesting.com/">PF&amp;Investing</a> is the new home for this blog. Initials &#8220;PF&#8221; stand for &#8220;Personal Finance&#8221;, which, along with the word &#8220;Investing&#8221;, sum up the blog&#8217;s content. The moving process went like a breeze, kudos to <a title="WordPress" href="http://wordpress.org/" target="_blank">WordPress</a>.</p>
<p>As you notice, there is a significant lull in my posting activity (I wrote <a title="What is a stock?" href="http://pfinvesting.com/2007/10/29/what-is-stock/">the last one</a> on October 29, 2007). This is only a temporary break, let me assure you, while I am sorting out other  more immediate priorities in my life. I promise to get back here as soon as possible, so please keep checking back.</p>
]]></content:encoded>
			<wfw:commentRss>http://pfinvesting.com/2008/02/18/new-home/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

