<?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: Small Security Tipps for your WordPress Install</title>
	<atom:link href="http://wpengineer.com/small-security-tipps-for-your-wordpress-install/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/</link>
	<description>WordPress News, Hacks, Tipps, Tutorials, Plugins and Themes</description>
	<lastBuildDate>Sun, 14 Mar 2010 15:20:14 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Hoff - WP Blog Host</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-3152</link>
		<dc:creator>John Hoff - WP Blog Host</dc:creator>
		<pubDate>Tue, 29 Dec 2009 16:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-3152</guid>
		<description>@WPExploerer - Use the WordPress Firewall plugin to help guard against injection attempts.

Also, Jeff Starr of Perishable Press has a neat little trick to help guard against injections:
&lt;a href=&quot;http://perishablepress.com/press/2009/12/22/protect-wordpress-against-malicious-url-requests/&quot; rel=&quot;nofollow&quot;&gt;Protect WordPress Against Malicious URL Requests&lt;/a&gt;

I suggest using his 4G Blacklist as well. There&#039;s a link to it in his article.</description>
		<content:encoded><![CDATA[<p>@WPExploerer - Use the WordPress Firewall plugin to help guard against injection attempts.</p>
<p>Also, Jeff Starr of Perishable Press has a neat little trick to help guard against injections:<br />
<a href="http://perishablepress.com/press/2009/12/22/protect-wordpress-against-malicious-url-requests/" rel="nofollow" class="liexternal">Protect WordPress Against Malicious URL Requests</a></p>
<p>I suggest using his 4G Blacklist as well. There's a link to it in his article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WPExplorer</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-3150</link>
		<dc:creator>WPExplorer</dc:creator>
		<pubDate>Mon, 28 Dec 2009 23:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-3150</guid>
		<description>One of my website got hacked recently with a link injection. It is all cleaned now, but I am still working to get it all secured nicely. Thank you for the tips.</description>
		<content:encoded><![CDATA[<p>One of my website got hacked recently with a link injection. It is all cleaned now, but I am still working to get it all secured nicely. Thank you for the tips.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: サーバー移行とWordpressアップグレード &#124; Nutspress</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-3074</link>
		<dc:creator>サーバー移行とWordpressアップグレード &#124; Nutspress</dc:creator>
		<pubDate>Mon, 21 Dec 2009 01:47:49 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-3074</guid>
		<description>[...] 移行のついでにデータベースのテーブル名を変更、ユーザーもAdminからこちらで設定したものに変更。このあたりはphpAdminでSQLを実行したり、直接データベースを触って値を変更したりしています。 Small Security Tipps for your WordPress Install [...]</description>
		<content:encoded><![CDATA[<p>[...] 移行のついでにデータベースのテーブル名を変更、ユーザーもAdminからこちらで設定したものに変更。このあたりはphpAdminでSQLを実行したり、直接データベースを触って値を変更したりしています。 Small Security Tipps for your WordPress Install [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hoff - WP Blog Host</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-2040</link>
		<dc:creator>John Hoff - WP Blog Host</dc:creator>
		<pubDate>Sat, 21 Nov 2009 20:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-2040</guid>
		<description>I think most people read posts like these and never really follow through with implementation. That&#039;s too bad because people&#039;s blogs get hacked every single day.

No one likes the boring / technical sides of blogging (ok, maybe some do), but if bloggers think for a moment about how much time they actually invest into their blog (and money), isn&#039;t it worth taking a couple of days locking it down and protecting their investment?

About the SSL admin login, there&#039;s a plugin out which forces SSL logins, but I never really understood why it&#039;s needed? After all, like you said, you can force the issue through the wp-config file. I feel the same way about the Google Analytics and Feedburner plugins, but that&#039;s another topic.

I actually just wrote a post about &lt;a href=&quot;http://wpbloghost.com/blog/wordpress-admin-ssl/&quot; rel=&quot;nofollow&quot;&gt;logging into WordPress through SSL&lt;/a&gt;. I hope you don&#039;t mind the link, but I think it goes well with what you talked about here.</description>
		<content:encoded><![CDATA[<p>I think most people read posts like these and never really follow through with implementation. That's too bad because people's blogs get hacked every single day.</p>
<p>No one likes the boring / technical sides of blogging (ok, maybe some do), but if bloggers think for a moment about how much time they actually invest into their blog (and money), isn't it worth taking a couple of days locking it down and protecting their investment?</p>
<p>About the SSL admin login, there's a plugin out which forces SSL logins, but I never really understood why it's needed? After all, like you said, you can force the issue through the wp-config file. I feel the same way about the Google Analytics and Feedburner plugins, but that's another topic.</p>
<p>I actually just wrote a post about <a href="http://wpbloghost.com/blog/wordpress-admin-ssl/" rel="nofollow" class="liexternal">logging into WordPress through SSL</a>. I hope you don't mind the link, but I think it goes well with what you talked about here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ken the tech</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-2027</link>
		<dc:creator>ken the tech</dc:creator>
		<pubDate>Wed, 18 Nov 2009 17:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-2027</guid>
		<description>Thanks for the detailed process. Really helpful for anyone on it&#039;s first contact with wp :)

here another way of installing Wordpress through cPanel:

http://www.kensfi.com/how-to-install-wordpress-in-7-steps-using-cpanel/

Very good for everyone who&#039;s familiar with cPanel interface :)</description>
		<content:encoded><![CDATA[<p>Thanks for the detailed process. Really helpful for anyone on it's first contact with wp <img src='http://wpengineer.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>here another way of installing Wordpress through cPanel:</p>
<p><a href="http://www.kensfi.com/how-to-install-wordpress-in-7-steps-using-cpanel/" rel="nofollow" class="liexternal">http://www.kensfi.com/how-to-install-wordpress-in-7-steps-using-cpanel/</a></p>
<p>Very good for everyone who's familiar with cPanel interface <img src='http://wpengineer.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Smart</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1998</link>
		<dc:creator>Dan Smart</dc:creator>
		<pubDate>Fri, 13 Nov 2009 08:41:20 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1998</guid>
		<description>Tomas yes it is simple enough to discover the wp-content name, however this step is useful in blocking automated tools that don&#039;t check.</description>
		<content:encoded><![CDATA[<p>Tomas yes it is simple enough to discover the wp-content name, however this step is useful in blocking automated tools that don't check.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1993</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1993</guid>
		<description>Hey Thomas, that is true :)</description>
		<content:encoded><![CDATA[<p>Hey Thomas, that is true <img src='http://wpengineer.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Kapler</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1985</link>
		<dc:creator>Tomas Kapler</dc:creator>
		<pubDate>Tue, 10 Nov 2009 18:11:28 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1985</guid>
		<description>just small comment about renaming wp-content - quite useless, when all files like images, css ... are in the same folder, so it take anyone about 1 second to find out what the new folder is, just by looking at any image address.

It would be better to redefine only plugin folder (and hope that you do not have security hole in your theme)</description>
		<content:encoded><![CDATA[<p>just small comment about renaming wp-content - quite useless, when all files like images, css ... are in the same folder, so it take anyone about 1 second to find out what the new folder is, just by looking at any image address.</p>
<p>It would be better to redefine only plugin folder (and hope that you do not have security hole in your theme)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1984</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 10 Nov 2009 17:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1984</guid>
		<description>Hey Bryan, thanks for mentioning, but Frank already linked to the reference in the paragraph right under &quot;Authentication Unique Keys&quot;. But it probably didn&#039;t stand out enough. :)

@all, glad you like the little tips Frank gave you! Compliments always welcome!</description>
		<content:encoded><![CDATA[<p>Hey Bryan, thanks for mentioning, but Frank already linked to the reference in the paragraph right under "Authentication Unique Keys". But it probably didn't stand out enough. <img src='http://wpengineer.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@all, glad you like the little tips Frank gave you! Compliments always welcome!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1983</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Tue, 10 Nov 2009 14:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1983</guid>
		<description>Wordpress.org has an api utility to generate random valid text for all 4 security keys:

https://api.wordpress.org/secret-key/1.1/</description>
		<content:encoded><![CDATA[<p>Wordpress.org has an api utility to generate random valid text for all 4 security keys:</p>
<p><a href="https://api.wordpress.org/secret-key/1.1/" rel="nofollow" class="liwp">https://api.wordpress.org/secret-key/1.1/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Indrek</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1979</link>
		<dc:creator>Indrek</dc:creator>
		<pubDate>Tue, 10 Nov 2009 06:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1979</guid>
		<description>Thanks for these great tips. I actually hadn&#039;t heard about some of them so for me this article was very informative.

Off to securing my blog</description>
		<content:encoded><![CDATA[<p>Thanks for these great tips. I actually hadn't heard about some of them so for me this article was very informative.</p>
<p>Off to securing my blog</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roseli A. Bakar</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1978</link>
		<dc:creator>Roseli A. Bakar</dc:creator>
		<pubDate>Tue, 10 Nov 2009 05:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1978</guid>
		<description>Awesome tutorials Frank ! 

This post will help many wordpress users &quot;protect&quot; their blogs better.</description>
		<content:encoded><![CDATA[<p>Awesome tutorials Frank ! </p>
<p>This post will help many wordpress users "protect" their blogs better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EthanJ</title>
		<link>http://wpengineer.com/small-security-tipps-for-your-wordpress-install/#comment-1977</link>
		<dc:creator>EthanJ</dc:creator>
		<pubDate>Tue, 10 Nov 2009 00:07:51 +0000</pubDate>
		<guid isPermaLink="false">http://wpengineer.com/?p=1796#comment-1977</guid>
		<description>Great post. Been using a couple of these for a while but I&#039;m embarrassed to say I&#039;ve tried the rename wp-content one. Thanks.</description>
		<content:encoded><![CDATA[<p>Great post. Been using a couple of these for a while but I'm embarrassed to say I've tried the rename wp-content one. Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
