<?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: Making your passwords better for less</title>
	<atom:link href="http://www.bitesofapple.com/2010/01/11/making-your-passwords-better-for-less/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bitesofapple.com/2010/01/11/making-your-passwords-better-for-less/</link>
	<description>Fruitful news for small business Apple users.       By Ron Seybold</description>
	<lastBuildDate>Wed, 31 Mar 2010 11:30:42 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jon</title>
		<link>http://www.bitesofapple.com/2010/01/11/making-your-passwords-better-for-less/comment-page-1/#comment-105</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Tue, 12 Jan 2010 03:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitesofapple.com/?p=303#comment-105</guid>
		<description>Of your five rules of thumb, I like 1, 2, and 5, but I think the value of mixed-case and punctuation in passwords is overrated. In terms of bang-for-buck, if you&#039;re going to invest more keystrokes, it&#039;s better to spend them typing longer passwords rather than hitting the shift key. For example, &quot;xyag9p7wzo&quot; takes the same number of keystrokes as &quot;Wd&amp;eq9%&quot; but most people could probably type the first example faster, and it is more secure because it is almost 50% longer, less vulnerable to brute-force. I&#039;ll grant you that if the attacker *knows* I never use the shift key, it would allow for a slightly more efficient brute-force algorithm.

Of course, all of the above only applies for passwords that must be physically typed. If I&#039;m using a password manager that transmits the stored passwords for me, then I&#039;ll use the maximum allowable range of characters with full cryptographic randomness, for example https://www.grc.com/passwords.htm</description>
		<content:encoded><![CDATA[<p>Of your five rules of thumb, I like 1, 2, and 5, but I think the value of mixed-case and punctuation in passwords is overrated. In terms of bang-for-buck, if you&#8217;re going to invest more keystrokes, it&#8217;s better to spend them typing longer passwords rather than hitting the shift key. For example, &#8220;xyag9p7wzo&#8221; takes the same number of keystrokes as &#8220;Wd&amp;eq9%&#8221; but most people could probably type the first example faster, and it is more secure because it is almost 50% longer, less vulnerable to brute-force. I&#8217;ll grant you that if the attacker *knows* I never use the shift key, it would allow for a slightly more efficient brute-force algorithm.</p>
<p>Of course, all of the above only applies for passwords that must be physically typed. If I&#8217;m using a password manager that transmits the stored passwords for me, then I&#8217;ll use the maximum allowable range of characters with full cryptographic randomness, for example <a href="https://www.grc.com/passwords.htm" rel="nofollow">https://www.grc.com/passwords.htm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
