<?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: Web Form Password Strength Meters Are Useless</title>
	<atom:link href="http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/</link>
	<description>A web designoper&#039;s journal</description>
	<lastBuildDate>Fri, 10 Feb 2012 02:23:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: kozmonot</title>
		<link>http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/comment-page-1/#comment-4926</link>
		<dc:creator>kozmonot</dc:creator>
		<pubDate>Fri, 16 Oct 2009 23:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.catchmyfame.com/?p=249#comment-4926</guid>
		<description>Eevee I think you&#039;re missing the argument here. He&#039;s not arguing against strong passwords, but rather the false sense of security that password strength meters are implying. A developer can require any type of complexity in a password, and they should, however who is to say what qualifies as secure? These meters that pop up are just at the whim of whoever designed it and meet no criteria. The side argument is that too many systems allow incorrect password to be entered infinitely, or at least enough to allow them to be cracked, rather than either asking for some form of authentication, or disabling the account. Cheers.</description>
		<content:encoded><![CDATA[<p>Eevee I think you&#8217;re missing the argument here. He&#8217;s not arguing against strong passwords, but rather the false sense of security that password strength meters are implying. A developer can require any type of complexity in a password, and they should, however who is to say what qualifies as secure? These meters that pop up are just at the whim of whoever designed it and meet no criteria. The side argument is that too many systems allow incorrect password to be entered infinitely, or at least enough to allow them to be cracked, rather than either asking for some form of authentication, or disabling the account. Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eevee</title>
		<link>http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/comment-page-1/#comment-4925</link>
		<dc:creator>Eevee</dc:creator>
		<pubDate>Fri, 16 Oct 2009 20:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.catchmyfame.com/?p=249#comment-4925</guid>
		<description>Who exactly do you think is going to encourage good password practices, if not the applications requesting the passwords?  I&#039;ve had several leaked password lists land on my desk in the past few years, and you would not believe how many worthless passwords there are out there.  I&#039;m looking at such a list right now, and I see winners like &#039;ferret&#039;, &#039;cosmos&#039;, &#039;polo&#039;, &#039;bullet&#039;, and yes, &#039;password&#039;.

If the constraints are bad, then fine, complain about that.  There are tons of braindead password rules floating around, and having a strength meter or not doesn&#039;t do anything to change that.  But I hardly see a problem with a little password meter that, at the very least, prevents people from using bare dictionary words as passwords.  It&#039;s not a false sense of security; it does in fact increase security.  Servers do get broken into sometimes.  Your clever monitoring applet will be wrong sometimes.  (Not sure how you intend to differentiate between a user who&#039;s forgotten his password and someone deliberately keeping an account locked, btw.)  A good password will help protect against these things.</description>
		<content:encoded><![CDATA[<p>Who exactly do you think is going to encourage good password practices, if not the applications requesting the passwords?  I&#8217;ve had several leaked password lists land on my desk in the past few years, and you would not believe how many worthless passwords there are out there.  I&#8217;m looking at such a list right now, and I see winners like &#8216;ferret&#8217;, &#8216;cosmos&#8217;, &#8216;polo&#8217;, &#8216;bullet&#8217;, and yes, &#8216;password&#8217;.</p>
<p>If the constraints are bad, then fine, complain about that.  There are tons of braindead password rules floating around, and having a strength meter or not doesn&#8217;t do anything to change that.  But I hardly see a problem with a little password meter that, at the very least, prevents people from using bare dictionary words as passwords.  It&#8217;s not a false sense of security; it does in fact increase security.  Servers do get broken into sometimes.  Your clever monitoring applet will be wrong sometimes.  (Not sure how you intend to differentiate between a user who&#8217;s forgotten his password and someone deliberately keeping an account locked, btw.)  A good password will help protect against these things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/comment-page-1/#comment-4923</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 16 Oct 2009 04:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.catchmyfame.com/?p=249#comment-4923</guid>
		<description>&lt;b&gt;@Eevee&lt;/b&gt;
Any server admin knows the difference between a DoS attack, a legitimate user entering their password incorrectly, and a scripted attempt to login to someone else&#039;s account. Setting up a job to monitor that is what I was referring to. And my point is not to stop people from coming up with strong passwords, just the opposite. I&#039;m against the false sense of security that password meters imply.</description>
		<content:encoded><![CDATA[<p><b>@Eevee</b><br />
Any server admin knows the difference between a DoS attack, a legitimate user entering their password incorrectly, and a scripted attempt to login to someone else&#8217;s account. Setting up a job to monitor that is what I was referring to. And my point is not to stop people from coming up with strong passwords, just the opposite. I&#8217;m against the false sense of security that password meters imply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eevee</title>
		<link>http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/comment-page-1/#comment-4907</link>
		<dc:creator>Eevee</dc:creator>
		<pubDate>Thu, 15 Oct 2009 17:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.catchmyfame.com/?p=249#comment-4907</guid>
		<description>You can&#039;t just disable accounts; that opens a laughably simple DoS.  Just write a script to repeatedly try to log into the account of someone you don&#039;t like, and it will stay disabled forever.  This has actually happened to banks before.

What happens when the CAPTCHA is broken, as it has been before?

What happens if the server is broken into and someone gets ahold of all the password hashes?  I&#039;d sure like my password to be harder to crack.</description>
		<content:encoded><![CDATA[<p>You can&#8217;t just disable accounts; that opens a laughably simple DoS.  Just write a script to repeatedly try to log into the account of someone you don&#8217;t like, and it will stay disabled forever.  This has actually happened to banks before.</p>
<p>What happens when the CAPTCHA is broken, as it has been before?</p>
<p>What happens if the server is broken into and someone gets ahold of all the password hashes?  I&#8217;d sure like my password to be harder to crack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/comment-page-1/#comment-3970</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 19 Sep 2009 18:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.catchmyfame.com/?p=249#comment-3970</guid>
		<description>But I believe that therein lies the flaw with both your Google and Hotmail examples, both of which have been hacked despite the CAPTCHAS. CAPTCHAS are great for separating people from machines, but it doesn&#039;t prevent someone from sitting down and attempting to hack their way into a system. By locking an account after X failed attempts, and then requiring some other form of authentication, you&#039;re making it far more difficult for someone to hack their way in as opposed to throwing up the CAPTCHA barrier which may simply slow them down. I, general I agree with you in terms of keeping things simple, but by doing so in terms of account security I think we need to make the hurdles a bit higher.</description>
		<content:encoded><![CDATA[<p>But I believe that therein lies the flaw with both your Google and Hotmail examples, both of which have been hacked despite the CAPTCHAS. CAPTCHAS are great for separating people from machines, but it doesn&#8217;t prevent someone from sitting down and attempting to hack their way into a system. By locking an account after X failed attempts, and then requiring some other form of authentication, you&#8217;re making it far more difficult for someone to hack their way in as opposed to throwing up the CAPTCHA barrier which may simply slow them down. I, general I agree with you in terms of keeping things simple, but by doing so in terms of account security I think we need to make the hurdles a bit higher.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harald</title>
		<link>http://www.catchmyfame.com/2009/09/01/web-form-password-strength-meters-are-useless/comment-page-1/#comment-3590</link>
		<dc:creator>Harald</dc:creator>
		<pubDate>Sat, 12 Sep 2009 19:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.catchmyfame.com/?p=249#comment-3590</guid>
		<description>People do forget passwords, and when they do they will try to remember it by entering different combination of their password both 3 and 5 times. Therefore I think your suggestion is onto something, but I would not make it as advanced as you suggest. I think it&#039;s better to keep it simple. Google and Hotmail are great examples on this. They don&#039;t disable a user’s account after a certain number of failed login attempts, instead - after a certain number of failed login attempts- you&#039;ll have to solve a captcha for every new attempt.

Good article though :)</description>
		<content:encoded><![CDATA[<p>People do forget passwords, and when they do they will try to remember it by entering different combination of their password both 3 and 5 times. Therefore I think your suggestion is onto something, but I would not make it as advanced as you suggest. I think it&#8217;s better to keep it simple. Google and Hotmail are great examples on this. They don&#8217;t disable a user’s account after a certain number of failed login attempts, instead &#8211; after a certain number of failed login attempts- you&#8217;ll have to solve a captcha for every new attempt.</p>
<p>Good article though :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

