<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lithik Systems &#187; passphrase</title>
	<atom:link href="http://www.lithik.com/tag/passphrase/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lithik.com</link>
	<description>Transforming businesses by bending technology to the will of our clients</description>
	<lastBuildDate>Thu, 26 Jan 2012 15:28:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Creating Good Passwords</title>
		<link>http://www.lithik.com/2009/08/04/creating-good-passwords/</link>
		<comments>http://www.lithik.com/2009/08/04/creating-good-passwords/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 16:35:37 +0000</pubDate>
		<dc:creator>Karl Fox</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[good password]]></category>
		<category><![CDATA[good passwords]]></category>
		<category><![CDATA[guess]]></category>
		<category><![CDATA[length]]></category>
		<category><![CDATA[memorable]]></category>
		<category><![CDATA[pass phrase]]></category>
		<category><![CDATA[passphrase]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[passwords]]></category>
		<category><![CDATA[rainbow tables]]></category>
		<category><![CDATA[scope]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[sentence]]></category>

		<guid isPermaLink="false">http://www.lithik.com/?p=299</guid>
		<description><![CDATA[The keys to good password hygiene are: Making them hard to guess, Never writing them down, Limiting the scope of passwords, and Limiting the ability of an attacker to make repeated guesses. Password Complexity A recent study on password memorability and security uncovered two surprising results: The most important factor in the security of passwords [...]]]></description>
			<content:encoded><![CDATA[<p>The keys to good password hygiene are:</p>
<ul>
<li>Making them hard to guess,</li>
<li>Never writing them down,</li>
<li>Limiting the scope of passwords, and</li>
<li>Limiting the ability of an attacker to make repeated guesses.</li>
</ul>
<h2>Password Complexity</h2>
<p>A recent study on password memorability and security uncovered two surprising results:<br />
<span id="more-299"></span></p>
<ul>
<li>The most important factor in the security of passwords is consistency—implementing technical controls to enforce password quality.</li>
<li>So-called “passphrase” passwords are equal in quality to completely random passwords, yet are no more difficult to remember than any other user-chosen password.</li>
</ul>
<p>Good passwords (those that are least vulnerable to password cracking attacks) utilize the full spectrum of allowable characters (Capital and lower case letters, numbers and symbols) and are long enough to force password crackers to use their slowest “brute force” technique.</p>
<h2>Memorable Passwords</h2>
<p>“Passphrase” passwords meet both of these requirements. To create one, just choose a memorable sentence and make it your password. Windows considers the space character to be a special character, so setting your password to &#8220;I love the Buckeyes!&#8221; meets the Windows password complexity requirement, gives you a password 20 characters long, and declares your allegiance just as well as &#8220;goBUCKS!&#8221; without falling to a password cracker in the first two seconds.</p>
<p>If your computer system limits you to relatively short passwords (say, 8 or 10 characters), or if you are a two-finger typist, take a simple sentence, assemble the first letters from each word in the sentence (as with an acronym), including appropriate capitalization and punctuation, then modify the new password slightly using numbers or special characters. For example, the phrase, “Obama declares nuclear war; details at 11” might be entered as “Odnw;d@11” which looks like a random password, yet is easy to remember. Similarly, the phrase, “It’s noon and I am hungry” could be typed in as “It’s12&amp;Iah.” Unlike random passwords, passwords of this style are not any harder to memorize than shorter ones.</p>
<h2>Length is Key</h2>
<p>The power tools used by the bad guys can make quick work of password hash files these days, but choosing a password at least 15 or 16 characters long can move the advantage back to your side.</p>
<p><a href="http://en.wikipedia.org/wiki/Rainbow_table">Rainbow tables</a> can crack any password hash up to the length limit of the table in a very short time.  Since these tables grow exponentially large with the password length, there are probably few or no existing rainbow tables (yet!) for passwords longer than 15 or 16 characters.</p>
<p>Additionally, traditional Windows password crackers such as <a href="http://en.wikipedia.org/wiki/John_the_Ripper">John the Ripper</a> typically only crack the <a href="http://en.wikipedia.org/wiki/LM_hash">LAN Manager hash</a>, a relatively insecure password storage method that can only handle passwords 14 characters long or shorter.  Choosing a 15-character password forces the hacker to resort to the more esoteric and less computationally efficient NTLM (MD4) password hash algorithm.  Knowing this, you can make the bad guy&#8217;s job a whole lot harder by <a href="http://support.microsoft.com/?kbid=299656">not storing the LAN manager hash of your password</a> in the first place.</p>
<h2>Password Scope and Availability</h2>
<p>Even with an excellent password, however, an attacker can still break in if he has the opportunity (and patience) to make a hundred billion guesses at your password. It is also critically important to:</p>
<ol>
<li>Limit the number of failed password attempts, or at least limit the rate, and</li>
<li>Log repeated failures so that action can be taken.</li>
</ol>
<p>Similarly, choosing excellent passwords has little value if you use the same password for your business VPN and your Facebook or Amazon account. A hacker who manages to gain access to all of Amazon’s account holders is very quickly going to see if the user foxk@lithik.com with the password H@rd2gess has VPN access to lithik.com with username foxk and the same password. This type of attack is easily automated across thousands of stolen passwords.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.lithik.com/2009/08/04/creating-good-passwords/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

