<?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: Secure Passphrases</title>
	<atom:link href="http://pthree.org/2006/12/15/secure-passphrases/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2006/12/15/secure-passphrases/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Wed, 16 May 2012 07:36:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-beta2-20489</generator>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-110431</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Thu, 05 Nov 2009 03:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-110431</guid>
		<description>i&#039;m familiar with pwgen and the man page, thanks.</description>
		<content:encoded><![CDATA[<p>i&#8217;m familiar with pwgen and the man page, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RTFM</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-110428</link>
		<dc:creator>RTFM</dc:creator>
		<pubDate>Wed, 04 Nov 2009 23:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-110428</guid>
		<description>pwgen [HowManyCharacters like 100] [how man passwords do you need] -n -c  -y  --&gt; gives me nice ones... just read the manpage

you can even use a file&#039;s hash with -h  but don&#039;t lose the file ;)</description>
		<content:encoded><![CDATA[<p>pwgen [HowManyCharacters like 100] [how man passwords do you need] -n -c  -y  &#8211;&gt; gives me nice ones&#8230; just read the manpage</p>
<p>you can even use a file&#8217;s hash with -h  but don&#8217;t lose the file <img src='http://pthree.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Levi</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-22143</link>
		<dc:creator>Levi</dc:creator>
		<pubDate>Mon, 18 Dec 2006 22:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-22143</guid>
		<description>Lonnie:  Reading over my comment, I admit I was a bit harsh.  We ended up having a nice discussion on #utah, though, so I hope no feelings were permanently hurt. :)

Anyway, I think there were some fundamentally wrong assumptions in the security comparisons, and the mathematical analysis of cryptographic things should always be considered, because these things don&#039;t always follow intuition.

Given an 8 character limit, which used to be quite common, it was very important to avoid dictionary words and use as many odd characters as possible.  Now, adding additional characters can make even passphrases with plain English phrases much more secure than any 8-character password.  

Emphasizing obfuscation when simply adding a few more words could create a much stronger passphrase is unfortunate.</description>
		<content:encoded><![CDATA[<p>Lonnie:  Reading over my comment, I admit I was a bit harsh.  We ended up having a nice discussion on #utah, though, so I hope no feelings were permanently hurt. <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Anyway, I think there were some fundamentally wrong assumptions in the security comparisons, and the mathematical analysis of cryptographic things should always be considered, because these things don&#8217;t always follow intuition.</p>
<p>Given an 8 character limit, which used to be quite common, it was very important to avoid dictionary words and use as many odd characters as possible.  Now, adding additional characters can make even passphrases with plain English phrases much more secure than any 8-character password.  </p>
<p>Emphasizing obfuscation when simply adding a few more words could create a much stronger passphrase is unfortunate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-21804</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Sat, 16 Dec 2006 03:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-21804</guid>
		<description>Actually you can create passwords longer than 8 characters with pwgen. Just by adding a number, so:

pwgen -cn 20

Will create 20 character passwords with numbers and cases.</description>
		<content:encoded><![CDATA[<p>Actually you can create passwords longer than 8 characters with pwgen. Just by adding a number, so:</p>
<p>pwgen -cn 20</p>
<p>Will create 20 character passwords with numbers and cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lonnie Olson</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-21795</link>
		<dc:creator>Lonnie Olson</dc:creator>
		<pubDate>Sat, 16 Dec 2006 01:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-21795</guid>
		<description>Re: Levi
I am pretty sure his claim that &#039;ienjoyprogrammingperl&#039; is less secure was not compared to very strong 8 character passwords, but compared to what it could/should be, as he later explained.  You are so picky.</description>
		<content:encoded><![CDATA[<p>Re: Levi<br />
I am pretty sure his claim that &#8216;ienjoyprogrammingperl&#8217; is less secure was not compared to very strong 8 character passwords, but compared to what it could/should be, as he later explained.  You are so picky.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lonnie Olson</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-21794</link>
		<dc:creator>Lonnie Olson</dc:creator>
		<pubDate>Sat, 16 Dec 2006 01:17:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-21794</guid>
		<description>Thanks, I really enjoyed this.  Your techniques for good, long passphrases are very good.

Let me recommend better pass(word&#124;phrase) generators.
1. For strong, memorable passphrases use &lt;a href=&quot;http://www.adel.nursat.kz/apg/&quot; rel=&quot;nofollow&quot;&gt;apg&lt;/a&gt;.  This tool will generate strong passphrases (configurable length and strength), and can optionally print out the pronunciation key.  These passwords are not in the dictionary, but are still pronounceable, hence memorable.

2. For extremely strong, rarely used (WEP/WPA keys), long passphrases.  Use &lt;a href=&quot;https://www.grc.com/passwords.htm&quot; rel=&quot;nofollow&quot;&gt;GRC&#039;s Perfect Passwords&lt;/a&gt;.  It generates completely random nonsense.  It s delivered very securely over SSL.</description>
		<content:encoded><![CDATA[<p>Thanks, I really enjoyed this.  Your techniques for good, long passphrases are very good.</p>
<p>Let me recommend better pass(word|phrase) generators.<br />
1. For strong, memorable passphrases use <a href="http://www.adel.nursat.kz/apg/" rel="nofollow">apg</a>.  This tool will generate strong passphrases (configurable length and strength), and can optionally print out the pronunciation key.  These passwords are not in the dictionary, but are still pronounceable, hence memorable.</p>
<p>2. For extremely strong, rarely used (WEP/WPA keys), long passphrases.  Use <a href="https://www.grc.com/passwords.htm" rel="nofollow">GRC&#8217;s Perfect Passwords</a>.  It generates completely random nonsense.  It s delivered very securely over SSL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ubuntu Tutorials</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-21757</link>
		<dc:creator>Ubuntu Tutorials</dc:creator>
		<pubDate>Fri, 15 Dec 2006 19:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-21757</guid>
		<description>You do have some good points with this post.  I understand pwgen doesn&#039;t make the *best* passwords but its better than &quot;password&quot; or something crappy like a lot of people use.

I&#039;ve extended my post to refer to your extended outline.  Thanks</description>
		<content:encoded><![CDATA[<p>You do have some good points with this post.  I understand pwgen doesn&#8217;t make the *best* passwords but its better than &#8220;password&#8221; or something crappy like a lot of people use.</p>
<p>I&#8217;ve extended my post to refer to your extended outline.  Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Levi</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-21752</link>
		<dc:creator>Levi</dc:creator>
		<pubDate>Fri, 15 Dec 2006 17:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-21752</guid>
		<description>Clearly you&#039;re a bit rusty on your combinatorics.  You claim that &#039;ienjoyprogrammingperl&#039; is insecure because it only uses lowercase characters and contains dictionary words.  Let&#039;s look at the math, shall we?

First, let&#039;s look at the naive brute-force method assuming only lowercase letters.  That&#039;s 21 characters, each of which has 26 possibilities, which gives us a total search space of 26^21 combinations.  I&#039;ll let you put that in your calculator yourself, as it&#039;s too big to type, and certainly not a realistic search space.  Compare this with an 8-character password using all 256 characters, which yields only 256^8 combinations.  This is a MUCH smaller number, though still huge.  So, a completely obfuscated 8-character password is far less secure than a 21-character password consisting only of lowercase letters in the face of a brute force attack.

Now, let&#039;s examine a dictionary attack.  My /usr/dict/words has 98569 words in it.  If the hacker were to correctly guess that your password consisted of 4 non-repeated words (which is a best-case scenario, of course) then there would be 98569*98568*98567*98567 combinations.  This is the same order of magnitude as an 8 character password utilizing potentially all 256 characters!  In fact, it&#039;s more than 5 times bigger of a search space.

Anyway, you can now clearly see that your assertion that &#039;iloveprogrammingperl&#039; is an extremely weak password is total bunk.  It is actually more secure than an 8-character random password.  It is true that using extra characters that remove the possibility of dictionary attacks make your password more secure, but there is a point of diminishing returns, and I think you crossed it somewhere before your final obfuscation there.</description>
		<content:encoded><![CDATA[<p>Clearly you&#8217;re a bit rusty on your combinatorics.  You claim that &#8216;ienjoyprogrammingperl&#8217; is insecure because it only uses lowercase characters and contains dictionary words.  Let&#8217;s look at the math, shall we?</p>
<p>First, let&#8217;s look at the naive brute-force method assuming only lowercase letters.  That&#8217;s 21 characters, each of which has 26 possibilities, which gives us a total search space of 26^21 combinations.  I&#8217;ll let you put that in your calculator yourself, as it&#8217;s too big to type, and certainly not a realistic search space.  Compare this with an 8-character password using all 256 characters, which yields only 256^8 combinations.  This is a MUCH smaller number, though still huge.  So, a completely obfuscated 8-character password is far less secure than a 21-character password consisting only of lowercase letters in the face of a brute force attack.</p>
<p>Now, let&#8217;s examine a dictionary attack.  My /usr/dict/words has 98569 words in it.  If the hacker were to correctly guess that your password consisted of 4 non-repeated words (which is a best-case scenario, of course) then there would be 98569*98568*98567*98567 combinations.  This is the same order of magnitude as an 8 character password utilizing potentially all 256 characters!  In fact, it&#8217;s more than 5 times bigger of a search space.</p>
<p>Anyway, you can now clearly see that your assertion that &#8216;iloveprogrammingperl&#8217; is an extremely weak password is total bunk.  It is actually more secure than an 8-character random password.  It is true that using extra characters that remove the possibility of dictionary attacks make your password more secure, but there is a point of diminishing returns, and I think you crossed it somewhere before your final obfuscation there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tristan Rhodes</title>
		<link>http://pthree.org/2006/12/15/secure-passphrases/#comment-21745</link>
		<dc:creator>Tristan Rhodes</dc:creator>
		<pubDate>Fri, 15 Dec 2006 16:36:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2006/12/15/secure-passphrases/#comment-21745</guid>
		<description>Aaron,

Thanks for the post.  I do like the idea of using passphrases, but I don&#039;t usually encrypt them as much as you. I would probably end up with something like this:

IEnjoyProgrammingPerl!
or
IenjoYprogramminGperL!

Here is my favorite password generator.  It provides all the options I need. I usually have it create 50 passwords and I choose the one that is easiest to remember.

http://www.winguides.com/security/password.php

Password Length: (4 - 64 chars)
Include Letters: YES
Include Mixed Case: YES
Include Numbers: YES
Include Punctuation: YES
Use similar characters:	(i, l, o, 1, 0, I) NO
Quantity: 50</description>
		<content:encoded><![CDATA[<p>Aaron,</p>
<p>Thanks for the post.  I do like the idea of using passphrases, but I don&#8217;t usually encrypt them as much as you. I would probably end up with something like this:</p>
<p>IEnjoyProgrammingPerl!<br />
or<br />
IenjoYprogramminGperL!</p>
<p>Here is my favorite password generator.  It provides all the options I need. I usually have it create 50 passwords and I choose the one that is easiest to remember.</p>
<p><a href="http://www.winguides.com/security/password.php" rel="nofollow">http://www.winguides.com/security/password.php</a></p>
<p>Password Length: (4 &#8211; 64 chars)<br />
Include Letters: YES<br />
Include Mixed Case: YES<br />
Include Numbers: YES<br />
Include Punctuation: YES<br />
Use similar characters:	(i, l, o, 1, 0, I) NO<br />
Quantity: 50</p>
]]></content:encoded>
	</item>
</channel>
</rss>

