<?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: WordPress: Make Your WordPress A Little Bit More Secure</title>
	<atom:link href="http://www.snippetit.com/2009/05/wordpress-make-your-wordpress-a-little-bit-more-secure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.snippetit.com/2009/05/wordpress-make-your-wordpress-a-little-bit-more-secure/</link>
	<description>IT News, Programming, Internet and Blogging</description>
	<lastBuildDate>Thu, 21 Oct 2010 09:34:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: First Post &#8212; The David Sullivan</title>
		<link>http://www.snippetit.com/2009/05/wordpress-make-your-wordpress-a-little-bit-more-secure/comment-page-1/#comment-269</link>
		<dc:creator>First Post &#8212; The David Sullivan</dc:creator>
		<pubDate>Fri, 29 May 2009 14:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.snippetit.com/?p=173#comment-269</guid>
		<description>[...] tweet about a fix and I tried it and found that there was still work to be done.  See the article Make Your Wordpress a Little More Secure and note my response to [...]</description>
		<content:encoded><![CDATA[<p>[...] tweet about a fix and I tried it and found that there was still work to be done.  See the article Make Your WordPress a Little More Secure and note my response to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: szehau</title>
		<link>http://www.snippetit.com/2009/05/wordpress-make-your-wordpress-a-little-bit-more-secure/comment-page-1/#comment-245</link>
		<dc:creator>szehau</dc:creator>
		<pubDate>Sat, 16 May 2009 16:53:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.snippetit.com/?p=173#comment-245</guid>
		<description>You are quite right about that. I always design my system to show a successful request for the lost password retrieval although user keyed in an invalid user id.</description>
		<content:encoded><![CDATA[<p>You are quite right about that. I always design my system to show a successful request for the lost password retrieval although user keyed in an invalid user id.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Sullivan</title>
		<link>http://www.snippetit.com/2009/05/wordpress-make-your-wordpress-a-little-bit-more-secure/comment-page-1/#comment-243</link>
		<dc:creator>David Sullivan</dc:creator>
		<pubDate>Sat, 16 May 2009 16:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.snippetit.com/?p=173#comment-243</guid>
		<description>Also, the &quot;Lost Your Password&quot; function gives away valid/invalid UserName.  To fix in /wp-login.php, add the &quot;//&quot; comment tags in the two lines of the code below:
   case &#039;retrievepassword&#039; :
   if ( $http_post ) {
   $errors = retrieve_password();
   // if ( !is_wp_error($errors) ) {
   wp_redirect(&#039;wp-login.php?checkemail=confirm&#039;);
   exit();
   // }
   }</description>
		<content:encoded><![CDATA[<p>Also, the &#8220;Lost Your Password&#8221; function gives away valid/invalid UserName.  To fix in /wp-login.php, add the &#8220;//&#8221; comment tags in the two lines of the code below:<br />
   case &#8216;retrievepassword&#8217; :<br />
   if ( $http_post ) {<br />
   $errors = retrieve_password();<br />
   // if ( !is_wp_error($errors) ) {<br />
   wp_redirect(&#8216;wp-login.php?checkemail=confirm&#8217;);<br />
   exit();<br />
   // }<br />
   }</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: szehau</title>
		<link>http://www.snippetit.com/2009/05/wordpress-make-your-wordpress-a-little-bit-more-secure/comment-page-1/#comment-238</link>
		<dc:creator>szehau</dc:creator>
		<pubDate>Fri, 15 May 2009 18:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.snippetit.com/?p=173#comment-238</guid>
		<description>Hi David Sullivan, 

Thanks for heading up that issue. I didn&#039;t notice that WP will focus the field that generate the login error and keep the user name in the field if the user name is correct.

Hopefully the changes will be implemented in the future release of Wordpress.</description>
		<content:encoded><![CDATA[<p>Hi David Sullivan, </p>
<p>Thanks for heading up that issue. I didn&#8217;t notice that WP will focus the field that generate the login error and keep the user name in the field if the user name is correct.</p>
<p>Hopefully the changes will be implemented in the future release of WordPress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Sullivan</title>
		<link>http://www.snippetit.com/2009/05/wordpress-make-your-wordpress-a-little-bit-more-secure/comment-page-1/#comment-237</link>
		<dc:creator>David Sullivan</dc:creator>
		<pubDate>Fri, 15 May 2009 17:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.snippetit.com/?p=173#comment-237</guid>
		<description>Good post and much needed.  However, WordPress still gives it away if you don&#039;t also edit the /wp-login.php file.

For example, if the UserName is wrong, by default WP will focus the cursor to the user_login field and blank it out. But if the Password is the incorrect value and the UserName is correct, WP will fill in the user_login field correct UserName and focus the cursor to the user_pass field.

The workaround in the wp-login.php file is two-fold:
1) Locate the login form with id=&quot;loginform&quot; and under that locate the  field with id=&quot;user_login&quot; and remove the php text from the value parameter so that it says value=&quot;&quot; (about line 469)

2) Next go to the bottom of the page just above the  tag and edit the JavaScript so that between the  tags it just says:
try{document.getElementById(&#039;user_login&#039;).focus();}catch(e){}

That should do it!</description>
		<content:encoded><![CDATA[<p>Good post and much needed.  However, WordPress still gives it away if you don&#8217;t also edit the /wp-login.php file.</p>
<p>For example, if the UserName is wrong, by default WP will focus the cursor to the user_login field and blank it out. But if the Password is the incorrect value and the UserName is correct, WP will fill in the user_login field correct UserName and focus the cursor to the user_pass field.</p>
<p>The workaround in the wp-login.php file is two-fold:<br />
1) Locate the login form with id=&#8221;loginform&#8221; and under that locate the  field with id=&#8221;user_login&#8221; and remove the php text from the value parameter so that it says value=&#8221;" (about line 469)</p>
<p>2) Next go to the bottom of the page just above the  tag and edit the JavaScript so that between the  tags it just says:<br />
try{document.getElementById(&#8216;user_login&#8217;).focus();}catch(e){}</p>
<p>That should do it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

