<?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/" xmlns:coop="http://www.google.com/coop/namespace" > <channel><title>Comments on: Lockdown Your WP-Admin with &#8220;Login Lockdown&#8221;</title> <atom:link href="http://wpvibe.com/lockdown-your-wp-admin-with-login-lockdown-135/feed/" rel="self" type="application/rss+xml" /><link>http://wpvibe.com/lockdown-your-wp-admin-with-login-lockdown-135/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=lockdown-your-wp-admin-with-login-lockdown</link> <description>Get into the Culture!</description> <lastBuildDate>Fri, 03 Sep 2010 15:30:58 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: The Digital Life &#38; Tools Blog</title><link>http://wpvibe.com/lockdown-your-wp-admin-with-login-lockdown-135/#comment-629</link> <dc:creator>The Digital Life &#38; Tools Blog</dc:creator> <pubDate>Thu, 28 Jan 2010 15:16:08 +0000</pubDate> <guid isPermaLink="false">http://wpvibe.com/?p=135#comment-629</guid> <description>Hi, I just caught the tweet on this.Thanks for sharing about this plugin. I&#039;ll be sure to check it out.Another security measure that bloggers running on WordPress might want to consider is to create a user (other than &quot;admin&quot;) who is an administrator-level user. Then make &quot;admin&quot; a normal user (like subscriber or some such).Since entry depends on knowing two things (the username and password), without knowing the username for the administrative user, attackers are surely not going to be able to get in even if they were somehow able to guess a password.</description> <content:encoded><![CDATA[<p>Hi, I just caught the tweet on this.</p><p>Thanks for sharing about this plugin. I&#8217;ll be sure to check it out.</p><p>Another security measure that bloggers running on WordPress might want to consider is to create a user (other than &#8220;admin&#8221;) who is an administrator-level user. Then make &#8220;admin&#8221; a normal user (like subscriber or some such).</p><p>Since entry depends on knowing two things (the username and password), without knowing the username for the administrative user, attackers are surely not going to be able to get in even if they were somehow able to guess a password.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using memcached (user agent is rejected)
Database Caching 2/16 queries in 0.004 seconds using apc
Content Delivery Network via cache.wpvibe.com (user agent is rejected)

Served from: wpvibe.com @ 2010-09-09 21:32:19 -->