<?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 Username Enumeration</title>
	<atom:link href="http://blogsecurity.net/news/news-180707/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/news/news-180707</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AskApache</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-757</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Mon, 20 Aug 2007 17:50:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-757</guid>
		<description>Very very cool article!  I created a wordpress plugin that you might want to check out and see if your method will still be useful.

&lt;a href=&quot;http://www.askapache.com/wordpress/htaccess-password-protect.html&quot; rel=&quot;nofollow&quot;&gt;htaccess password protect wp-admin&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Very very cool article!  I created a wordpress plugin that you might want to check out and see if your method will still be useful.</p>
<p><a href="http://www.askapache.com/wordpress/htaccess-password-protect.html" rel="nofollow">htaccess password protect wp-admin</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security Hub &#187; Blog Archive &#187; Enumera&#231;&#227;o de usu&#225;rios no Wordpress</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-691</link>
		<dc:creator>Security Hub &#187; Blog Archive &#187; Enumera&#231;&#227;o de usu&#225;rios no Wordpress</dc:creator>
		<pubDate>Tue, 14 Aug 2007 10:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-691</guid>
		<description>[...] O link para o texto original é este. [...]</description>
		<content:encoded><![CDATA[<p>[...] O link para o texto original é este. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dyingeyes weblog &#187; Sicherheit bei Wordpress-Benutzernamen</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-665</link>
		<dc:creator>dyingeyes weblog &#187; Sicherheit bei Wordpress-Benutzernamen</dc:creator>
		<pubDate>Sat, 11 Aug 2007 20:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-665</guid>
		<description>[...] von einem lesenswerten (englischsprachigen) Artikel &#8250;WordPress Username Enumeration&#8249; in BlogSecurity ein paar kurze Anmerkungen zu Verwendung von Benutzernamen in Wordpress &#8211; [...]</description>
		<content:encoded><![CDATA[<p>[...] von einem lesenswerten (englischsprachigen) Artikel &#8250;WordPress Username Enumeration&#8249; in BlogSecurity ein paar kurze Anmerkungen zu Verwendung von Benutzernamen in Wordpress &#8211; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recommended site for WordPress security</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-334</link>
		<dc:creator>Recommended site for WordPress security</dc:creator>
		<pubDate>Thu, 19 Jul 2007 12:16:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-334</guid>
		<description>[...] it is not holding back new WordPress holes from disclosure &#8212; for example, a new article yesterday showed how to perform enumeration on WordPress installation by brute force, so that valid usernames [...]</description>
		<content:encoded><![CDATA[<p>[...] it is not holding back new WordPress holes from disclosure &mdash; for example, a new article yesterday showed how to perform enumeration on WordPress installation by brute force, so that valid usernames [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-328</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Wed, 18 Jul 2007 23:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-328</guid>
		<description>Adrian, heh, I can beat that story but its for a drink at the pub evening :)</description>
		<content:encoded><![CDATA[<p>Adrian, heh, I can beat that story but its for a drink at the pub evening :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Pastor</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-333</link>
		<dc:creator>Adrian Pastor</dc:creator>
		<pubDate>Wed, 18 Jul 2007 17:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-333</guid>
		<description>David,

Don&#039;t take my word for it, but I think the 6 chars are a derived from a partial hash (first 6 chars of MD5 hash?) of a random value. Hopefully it&#039;s truly random, otherwise we have

36^6 = 2176782336 combinations

which is a lot! :)

Not too long ago we came across a financial app. The app would generate new passwords when clicking on &quot;I forgot my password&quot; that would be sent to your email. The problem is that the pwds were made of a word from either of the following groups:

- classic musician names
- fruits
- colors

plus two digits. You might think I&#039;m kidding but this is a real story.</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>Don&#8217;t take my word for it, but I think the 6 chars are a derived from a partial hash (first 6 chars of MD5 hash?) of a random value. Hopefully it&#8217;s truly random, otherwise we have</p>
<p>36^6 = 2176782336 combinations</p>
<p>which is a lot! :)</p>
<p>Not too long ago we came across a financial app. The app would generate new passwords when clicking on &#8220;I forgot my password&#8221; that would be sent to your email. The problem is that the pwds were made of a word from either of the following groups:</p>
<p>- classic musician names<br />
- fruits<br />
- colors</p>
<p>plus two digits. You might think I&#8217;m kidding but this is a real story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-332</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Wed, 18 Jul 2007 13:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-332</guid>
		<description>Phil, yes, those who implemented our hardening guide (atleast those able to) would be immune to a degree against this attack, nice point!</description>
		<content:encoded><![CDATA[<p>Phil, yes, those who implemented our hardening guide (atleast those able to) would be immune to a degree against this attack, nice point!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philipp</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-331</link>
		<dc:creator>Philipp</dc:creator>
		<pubDate>Wed, 18 Jul 2007 13:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-331</guid>
		<description>That vulnerability is the perfect example for a blog which isn&#039;t &lt;a href=&quot;http://blogsecurity.net/wordpress/article-210607/&quot; rel=&quot;nofollow&quot;&gt;hardened&lt;/a&gt;. That attack isn&#039;t possible when you hardened your blog. Or it&#039;s quite harder to achieve if you have at least password protected your wp-admin area. So for all who didn&#039;t considered harden their wp install should rethink their decision.</description>
		<content:encoded><![CDATA[<p>That vulnerability is the perfect example for a blog which isn&#8217;t <a href="http://blogsecurity.net/wordpress/article-210607/" rel="nofollow">hardened</a>. That attack isn&#8217;t possible when you hardened your blog. Or it&#8217;s quite harder to achieve if you have at least password protected your wp-admin area. So for all who didn&#8217;t considered harden their wp install should rethink their decision.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://blogsecurity.net/news/news-180707/comment-page-1#comment-330</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Wed, 18 Jul 2007 11:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=49#comment-330</guid>
		<description>Adrian, sometimes we underestimate the traditionl brute force approach, awesome article.

&lt;blockquote&gt;
It may be interesting to look into the default admin password generation that WordPress recommends when installing a blog. If I remember correctly its 6 characters, all lower-case with digits.
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>Adrian, sometimes we underestimate the traditionl brute force approach, awesome article.</p>
<blockquote><p>
It may be interesting to look into the default admin password generation that WordPress recommends when installing a blog. If I remember correctly its 6 characters, all lower-case with digits.
</p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>
