<?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: Password requirements</title>
	<atom:link href="http://usabilitythoughts.com/password-requirements.html/feed" rel="self" type="application/rss+xml" />
	<link>http://usabilitythoughts.com/password-requirements.html</link>
	<description>content meets user</description>
	<lastBuildDate>Tue, 08 Jun 2010 20:14:08 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Simon</title>
		<link>http://usabilitythoughts.com/password-requirements.html/comment-page-1#comment-3843</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sat, 06 Feb 2010 12:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=126#comment-3843</guid>
		<description>@Jacob - Wrong, &#039;newyorkcity&#039; is less secure than Pus9I34 in every way, teh first is not only open to dictionary attacks it also has fewer combinations.

@adrian - Putting a maximum limit on a pasword is not stupid, putting a vey small one is, but putting some sort of maximum on is sensible. 

As for making users use different characters, tough, users are the first to complain if their account gets hacked, but then when a users use &quot;1234&quot; or &quot;password&quot; for their accoutn what do they expect, unfortuantely some users need to be saved from their own stupidty.</description>
		<content:encoded><![CDATA[<p>@Jacob &#8211; Wrong, &#8216;newyorkcity&#8217; is less secure than Pus9I34 in every way, teh first is not only open to dictionary attacks it also has fewer combinations.</p>
<p>@adrian &#8211; Putting a maximum limit on a pasword is not stupid, putting a vey small one is, but putting some sort of maximum on is sensible. </p>
<p>As for making users use different characters, tough, users are the first to complain if their account gets hacked, but then when a users use &#8220;1234&#8243; or &#8220;password&#8221; for their accoutn what do they expect, unfortuantely some users need to be saved from their own stupidty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Wyke</title>
		<link>http://usabilitythoughts.com/password-requirements.html/comment-page-1#comment-2144</link>
		<dc:creator>Jacob Wyke</dc:creator>
		<pubDate>Sun, 26 Jul 2009 03:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=126#comment-2144</guid>
		<description>Totally agree with you on this one, I hate sites that force me to include a mixture of numbers and uppercase letters as it makes it no more stronger if you already have a long password.

Yes a 6 letter (a-z) password is less secure than than a 6 letter (a-zA-Z0-9) password, but not as strong as a 10+ letter (a-z) one.

I&#039;m personally just waiting for more sites to start asking for passphrases so that they become common enough that users understand them and don&#039;t get confused.</description>
		<content:encoded><![CDATA[<p>Totally agree with you on this one, I hate sites that force me to include a mixture of numbers and uppercase letters as it makes it no more stronger if you already have a long password.</p>
<p>Yes a 6 letter (a-z) password is less secure than than a 6 letter (a-zA-Z0-9) password, but not as strong as a 10+ letter (a-z) one.</p>
<p>I&#8217;m personally just waiting for more sites to start asking for passphrases so that they become common enough that users understand them and don&#8217;t get confused.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luiz Esmiralha</title>
		<link>http://usabilitythoughts.com/password-requirements.html/comment-page-1#comment-999</link>
		<dc:creator>Luiz Esmiralha</dc:creator>
		<pubDate>Mon, 08 Jun 2009 12:37:21 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=126#comment-999</guid>
		<description>Adrian,

that&#039;s good advice only if you are providing generic, personal, &quot;harmless&quot; services to your customers, like blogs and picture albums. Stuff that don&#039;t impact revenue. Services that demand security need a stronger password policy.</description>
		<content:encoded><![CDATA[<p>Adrian,</p>
<p>that&#8217;s good advice only if you are providing generic, personal, &#8220;harmless&#8221; services to your customers, like blogs and picture albums. Stuff that don&#8217;t impact revenue. Services that demand security need a stronger password policy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
