<?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: Comparative analysis of leaked Sony and Gawker&#160;passwords</title>
	<atom:link href="http://boingboing.net/2011/06/06/comparative-analysis.html/feed" rel="self" type="application/rss+xml" />
	<link>http://boingboing.net/2011/06/06/comparative-analysis.html</link>
	<description>Brain candy for Happy Mutants</description>
	<lastBuildDate>Tue, 18 Jun 2013 22:51:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Antinous / Moderator</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131524</link>
		<dc:creator>Antinous / Moderator</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131524</guid>
		<description>I&#039;ve been hacked, identity thefted or whatever you want to call it three times. In each case, it was done by physical theft of a physical receipt (two credit card accounts) or physical mail (bank account). I just can&#039;t bring myself to worry about someone hacking my comment account at the fancy goldfish forum.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been hacked, identity thefted or whatever you want to call it three times. In each case, it was done by physical theft of a physical receipt (two credit card accounts) or physical mail (bank account). I just can&#8217;t bring myself to worry about someone hacking my comment account at the fancy goldfish forum.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: robulus</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131525</link>
		<dc:creator>robulus</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131525</guid>
		<description>&lt;i&gt;&quot;Assuming the passwords are encrypted in storage&quot;&lt;/i&gt;

Except according to the article (which I just read) Sony had these passwords stored as plain text, which is, frankly, fucking unbelievable. And in that case you make a good point.

In the case of almost every other website in the world, including the website your local primary school set up to advertise their annual fete, passwords stored in the database would be encrypted.

Sony should switch to Wordpress, for Christ&#039;s sake.</description>
		<content:encoded><![CDATA[<p><i>&#8220;Assuming the passwords are encrypted in storage&#8221;</i></p>
<p>Except according to the article (which I just read) Sony had these passwords stored as plain text, which is, frankly, fucking unbelievable. And in that case you make a good point.</p>
<p>In the case of almost every other website in the world, including the website your local primary school set up to advertise their annual fete, passwords stored in the database would be encrypted.</p>
<p>Sony should switch to WordPress, for Christ&#8217;s sake.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thebes</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131527</link>
		<dc:creator>Thebes</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131527</guid>
		<description>What sort of fuckwit decides to store a million passwords as plaintext?
That takes a special kind of stupidity.</description>
		<content:encoded><![CDATA[<p>What sort of fuckwit decides to store a million passwords as plaintext?<br />
That takes a special kind of stupidity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131528</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131528</guid>
		<description>Why would you be surprised by this? Unless a site has my credit card details or other private information, I use the same weak password.  I don&#039;t really care if someone can post comments using my boingboing account, for example. Even facebook doesn&#039;t matter that much.</description>
		<content:encoded><![CDATA[<p>Why would you be surprised by this? Unless a site has my credit card details or other private information, I use the same weak password.  I don&#8217;t really care if someone can post comments using my boingboing account, for example. Even facebook doesn&#8217;t matter that much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Friesen</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131532</link>
		<dc:creator>Daniel Friesen</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131532</guid>
		<description>&quot;I have an honest question that maybe someone here could answer: If I use a password that is not a real word and is ten characters long, how much incremental gain in security do I get from including numbers or other characters?&quot;
A lot of people use all lowercase passwords, so naturally a password cracker will try to brute force all lowercase combinations before they jump into any symbols. The difference in entropy between all lowercase is from 26 possible options for each character, to 69 possible options for each character. The search space jumps from 146,813,779,479,510 possible passwords to 2,482,167,502,723,212,150 possible passwords.

Going by a hypothetical scenario where someone managed to get an online service&#039;s database, but that online service managed to at least hash the passwords, and assuming the cracker has the capability to make one hundred billion password guesses per second (which isn&#039;t unreasonable since someone built a homebrew rig that could make 33.1 billion password guesses per second) the 10 char alphanumeric password would take 24.47 minutes to guess. Replacing one character with a digit and another with a symbol changes that to taking 9.47 months to guess that single password. Pad that to 15 and it&#039;ll take 8.52 hundred million centuries.

Steve Gibson came up with a really good way to make secure and easily memorable passwords which I&#039;d recommend using: https://www.grc.com/%5Chaystack.htm

Course you wouldn&#039;t want to reuse the same pattern on random websites since if one was cracked and had plaintext they could look at your padding pattern. So I&#039;d recommend using it in combination with something like LastPass or KeePass.</description>
		<content:encoded><![CDATA[<p>&#8220;I have an honest question that maybe someone here could answer: If I use a password that is not a real word and is ten characters long, how much incremental gain in security do I get from including numbers or other characters?&#8221;<br />
A lot of people use all lowercase passwords, so naturally a password cracker will try to brute force all lowercase combinations before they jump into any symbols. The difference in entropy between all lowercase is from 26 possible options for each character, to 69 possible options for each character. The search space jumps from 146,813,779,479,510 possible passwords to 2,482,167,502,723,212,150 possible passwords.</p>
<p>Going by a hypothetical scenario where someone managed to get an online service&#8217;s database, but that online service managed to at least hash the passwords, and assuming the cracker has the capability to make one hundred billion password guesses per second (which isn&#8217;t unreasonable since someone built a homebrew rig that could make 33.1 billion password guesses per second) the 10 char alphanumeric password would take 24.47 minutes to guess. Replacing one character with a digit and another with a symbol changes that to taking 9.47 months to guess that single password. Pad that to 15 and it&#8217;ll take 8.52 hundred million centuries.</p>
<p>Steve Gibson came up with a really good way to make secure and easily memorable passwords which I&#8217;d recommend using: <a href="https://www.grc.com/%5Chaystack.htm" rel="nofollow">https://www.grc.com/%5Chaystack.htm</a></p>
<p>Course you wouldn&#8217;t want to reuse the same pattern on random websites since if one was cracked and had plaintext they could look at your padding pattern. So I&#8217;d recommend using it in combination with something like LastPass or KeePass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131534</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131534</guid>
		<description>Not really a representative sample. I subbed a numeric for non-alphnumeric for my playstation password because it&#039;s difficult to enter punctuation on a Playstation controller. 
</description>
		<content:encoded><![CDATA[<p>Not really a representative sample. I subbed a numeric for non-alphnumeric for my playstation password because it&#8217;s difficult to enter punctuation on a Playstation controller. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rindan</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131541</link>
		<dc:creator>Rindan</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131541</guid>
		<description>The best security is sometimes no security.  A lot of websites that I use, BoingBoing included, have simple all lower case passwords.  A dictionary attack won&#039;t get it, but it would be rejected by my company&#039;s security policy for multiple failures.  So what?  If you care enough to hack my BoingBoing account, what exactly are you going to do?  Troll in my name?  I can live with that.  If I had a Sony account, it would have gotten that junk password.  My Sony password and my e-mail account is completely useless.  At best, you might be able to troll a few forums in my name.  I can live with that.

The only sites worth having real security on are ones that matter.  My banking password and my Amazon account have strong passwords. My Google account, which could potentially give you ALL of my passwords has 2-step encryption so that you would not only need to know my password, but also have my phone.  At that point, it means you have a gun to my head and I&#039;m probably not going to fret if you break into my bank account.

Frankly, the password obsession is a bit much to begin with.  The difference between a 6 letters all lower case (300 million combinations) password that can&#039;t fall to a dictionary attack and one that is 32 random characters is pretty minimal and not worth thinking about except in truly high security situations.  It is better to have something you can remember and don&#039;t have to write on post-it notes that can be &quot;hacked&quot; by someone looking at the post-it note.  The only reason to enforce any sort of password standard is to prevent people from doing &quot;boobs&quot; as a password.

Far more important is to have some sort of 2-step authentication on things that are worth locking down.  It isn&#039;t a perfect defense.  Someone can always take a security token and put a gun to your head, but for most people, a cell phone and a password is security enough.  I give big props to Google for doing a really good job on their 2-step encryption for gmail.</description>
		<content:encoded><![CDATA[<p>The best security is sometimes no security.  A lot of websites that I use, BoingBoing included, have simple all lower case passwords.  A dictionary attack won&#8217;t get it, but it would be rejected by my company&#8217;s security policy for multiple failures.  So what?  If you care enough to hack my BoingBoing account, what exactly are you going to do?  Troll in my name?  I can live with that.  If I had a Sony account, it would have gotten that junk password.  My Sony password and my e-mail account is completely useless.  At best, you might be able to troll a few forums in my name.  I can live with that.</p>
<p>The only sites worth having real security on are ones that matter.  My banking password and my Amazon account have strong passwords. My Google account, which could potentially give you ALL of my passwords has 2-step encryption so that you would not only need to know my password, but also have my phone.  At that point, it means you have a gun to my head and I&#8217;m probably not going to fret if you break into my bank account.</p>
<p>Frankly, the password obsession is a bit much to begin with.  The difference between a 6 letters all lower case (300 million combinations) password that can&#8217;t fall to a dictionary attack and one that is 32 random characters is pretty minimal and not worth thinking about except in truly high security situations.  It is better to have something you can remember and don&#8217;t have to write on post-it notes that can be &#8220;hacked&#8221; by someone looking at the post-it note.  The only reason to enforce any sort of password standard is to prevent people from doing &#8220;boobs&#8221; as a password.</p>
<p>Far more important is to have some sort of 2-step authentication on things that are worth locking down.  It isn&#8217;t a perfect defense.  Someone can always take a security token and put a gun to your head, but for most people, a cell phone and a password is security enough.  I give big props to Google for doing a really good job on their 2-step encryption for gmail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sabik</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131556</link>
		<dc:creator>sabik</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131556</guid>
		<description>&lt;blockquote&gt;Far more important is to have some sort of 2-step authentication on things that are worth locking down.&lt;/blockquote&gt;

Ah, two-factor authentication. Something you know, and something you stole while working for RSA.</description>
		<content:encoded><![CDATA[<blockquote><p>Far more important is to have some sort of 2-step authentication on things that are worth locking down.</p></blockquote>
<p>Ah, two-factor authentication. Something you know, and something you stole while working for RSA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrs</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131558</link>
		<dc:creator>Chrs</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131558</guid>
		<description>Well agreed with many of these comments; Gawker password? Not worth my time to burn one of my &lt;i&gt;good&lt;/i&gt; memorized ones.  I&#039;ve got a relatively shitty default for unimportant site logins.  Gmail?  That there is a strong fucking password.  </description>
		<content:encoded><![CDATA[<p>Well agreed with many of these comments; Gawker password? Not worth my time to burn one of my <i>good</i> memorized ones.  I&#8217;ve got a relatively shitty default for unimportant site logins.  Gmail?  That there is a strong fucking password.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131577</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131577</guid>
		<description>Umm, just a quick question. How could you analyze the passwords if they where encrypted. Are you admitting that the gawker password database stores passwords in plain text?

ouch.

</description>
		<content:encoded><![CDATA[<p>Umm, just a quick question. How could you analyze the passwords if they where encrypted. Are you admitting that the gawker password database stores passwords in plain text?</p>
<p>ouch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dargaud</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131579</link>
		<dc:creator>dargaud</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131579</guid>
		<description>What do you mean no alphanumeric passwords allowed ? You mean I can&#039;t have &#039;; DROP DATABASE; &#039; as a password ?</description>
		<content:encoded><![CDATA[<p>What do you mean no alphanumeric passwords allowed ? You mean I can&#8217;t have &#8216;; DROP DATABASE; &#8216; as a password ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antinous / Moderator</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131580</link>
		<dc:creator>Antinous / Moderator</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131580</guid>
		<description>Also, it&#039;s really easy to turn a date into a strong password that you can easily memorize. You&#039;ve already got upper and lower case, plus numbers. Add a NAN character and create an ordering system that you use for all your passwords.</description>
		<content:encoded><![CDATA[<p>Also, it&#8217;s really easy to turn a date into a strong password that you can easily memorize. You&#8217;ve already got upper and lower case, plus numbers. Add a NAN character and create an ordering system that you use for all your passwords.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wrybread</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131581</link>
		<dc:creator>wrybread</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131581</guid>
		<description>Why would anyone use a strong password for a Gawker or Sony account or anything so insignificant? If someone wants to hack either of those accounts, i say have fun with it, you&#039;ve earned it, and it&#039;ll make a good story for me.

Email and banking on the other hand...



</description>
		<content:encoded><![CDATA[<p>Why would anyone use a strong password for a Gawker or Sony account or anything so insignificant? If someone wants to hack either of those accounts, i say have fun with it, you&#8217;ve earned it, and it&#8217;ll make a good story for me.</p>
<p>Email and banking on the other hand&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AitchJay</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1133374</link>
		<dc:creator>AitchJay</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1133374</guid>
		<description>I read a really easy way to make strong passwords on lifehacker: make a sentence for each site you visit &quot;I made this 1 sentence for my BoingBoing password&quot; and use the first letter of each word &quot;Imt1sfmBBp&quot;.

It&#039;s a good mnemonic, and easy to use.

</description>
		<content:encoded><![CDATA[<p>I read a really easy way to make strong passwords on lifehacker: make a sentence for each site you visit &#8220;I made this 1 sentence for my BoingBoing password&#8221; and use the first letter of each word &#8220;Imt1sfmBBp&#8221;.</p>
<p>It&#8217;s a good mnemonic, and easy to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131589</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131589</guid>
		<description>Honestly, not all that much.  As this whole ordeal demonstrates, most passwords are compromised not through decryption or brute force, but stealing them.

If you&#039;re choosing a password for an admin account or a role account on a server, or something that&#039;s likely to see a lot of exposure, making it a target, it really doesn&#039;t make much of a difference.  For end-user stuff, as long as you pick something relatively arbitrary that has no personal connection, it won&#039;t get guessed, even by a script.

As someone who&#039;s been a sysadmin at various times, I can say that it&#039;s far safer to encourage people to choose simple, hard to guess passwords and encourage them to change them frequently than it is to enforce draconian password policy.  If you force them to use difficult passwords, they&#039;ll just get frustrated and write them down, share them with others, etc.

It boils down to this simple fact: hackers probably don&#039;t want your data.  Your computer is more useful as a node in a botnet than as a source of data.  If they do want it, it&#039;s far less work for them to trick you into giving it to them than trying to extract it via technical means.  Having safe passwords is less about syntactic complexity than it is about good stewardship.</description>
		<content:encoded><![CDATA[<p>Honestly, not all that much.  As this whole ordeal demonstrates, most passwords are compromised not through decryption or brute force, but stealing them.</p>
<p>If you&#8217;re choosing a password for an admin account or a role account on a server, or something that&#8217;s likely to see a lot of exposure, making it a target, it really doesn&#8217;t make much of a difference.  For end-user stuff, as long as you pick something relatively arbitrary that has no personal connection, it won&#8217;t get guessed, even by a script.</p>
<p>As someone who&#8217;s been a sysadmin at various times, I can say that it&#8217;s far safer to encourage people to choose simple, hard to guess passwords and encourage them to change them frequently than it is to enforce draconian password policy.  If you force them to use difficult passwords, they&#8217;ll just get frustrated and write them down, share them with others, etc.</p>
<p>It boils down to this simple fact: hackers probably don&#8217;t want your data.  Your computer is more useful as a node in a botnet than as a source of data.  If they do want it, it&#8217;s far less work for them to trick you into giving it to them than trying to extract it via technical means.  Having safe passwords is less about syntactic complexity than it is about good stewardship.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nosehat</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131591</link>
		<dc:creator>nosehat</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131591</guid>
		<description>For me, one of the more surprising facts about this is that 2/3 of the users who have both a Sony account and a Gawker account have the same password.

I&#039;m not surprised at all that most people reuse their passwords.

The surprising twist here is that the Gawker data was released 5 months ago.  That means that 2/3 of the Gawker victims kept using the same password for multiple accounts &lt;i&gt;even after they knew this password had been published on the web with their email addresses for months!&lt;/i&gt;.

Does Boing Boing store our passwords as plain text?  If so, I&#039;m going to change mine to something rude and humorous.</description>
		<content:encoded><![CDATA[<p>For me, one of the more surprising facts about this is that 2/3 of the users who have both a Sony account and a Gawker account have the same password.</p>
<p>I&#8217;m not surprised at all that most people reuse their passwords.</p>
<p>The surprising twist here is that the Gawker data was released 5 months ago.  That means that 2/3 of the Gawker victims kept using the same password for multiple accounts <i>even after they knew this password had been published on the web with their email addresses for months!</i>.</p>
<p>Does Boing Boing store our passwords as plain text?  If so, I&#8217;m going to change mine to something rude and humorous.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SamSam</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131851</link>
		<dc:creator>SamSam</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131851</guid>
		<description>Another &quot;is this password safe&quot; question:

A few months ago I switched from having 2-3 strong passwords for my 6-7 Important Accounts (banks, etc) to having 1 strong password with small variations on it for each account.

So I now have an 10-character strong &quot;base&quot; password (mixed-case alphanumeric) with 3 extra unique characters bracketing it for each of the 6-7 important websites.

How secure is this strategy?</description>
		<content:encoded><![CDATA[<p>Another &#8220;is this password safe&#8221; question:</p>
<p>A few months ago I switched from having 2-3 strong passwords for my 6-7 Important Accounts (banks, etc) to having 1 strong password with small variations on it for each account.</p>
<p>So I now have an 10-character strong &#8220;base&#8221; password (mixed-case alphanumeric) with 3 extra unique characters bracketing it for each of the 6-7 important websites.</p>
<p>How secure is this strategy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ganman</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1132366</link>
		<dc:creator>ganman</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1132366</guid>
		<description>SamSam, if your &quot;base&quot; password is followed by, say, &quot;aol&quot; as your variation for your AOL account, your three-letter OneWest Bank variation would be easy as hell to pick off. In fact, one could argue that strategy is _worse_, as it provides a simple key for every other password if one is compromised. . </description>
		<content:encoded><![CDATA[<p>SamSam, if your &#8220;base&#8221; password is followed by, say, &#8220;aol&#8221; as your variation for your AOL account, your three-letter OneWest Bank variation would be easy as hell to pick off. In fact, one could argue that strategy is _worse_, as it provides a simple key for every other password if one is compromised. . </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cowicide</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131604</link>
		<dc:creator>Cowicide</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131604</guid>
		<description>I think the main lesson is don&#039;t use the same passwords everywhere.  That&#039;s, of course, easier said than done unless you use something like &lt;a href=&quot;http://agilebits.com/products/1Password&quot;&gt;1Password&lt;/a&gt; (which I love).</description>
		<content:encoded><![CDATA[<p>I think the main lesson is don&#8217;t use the same passwords everywhere.  That&#8217;s, of course, easier said than done unless you use something like <a href="http://agilebits.com/products/1Password">1Password</a> (which I love).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GyroMagician</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131618</link>
		<dc:creator>GyroMagician</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131618</guid>
		<description>Punctuation symbols move on different keyboard layouts (letters too, but not so much, unless it&#039;s French). Is the keyboard I&#039;m using UK, US or Swiss? And no, often the keyboard layout doesn&#039;t always match the keyboard appearance. I discovered this the hard way, trying to login from an Icelandic keyboard when my password contained a Â£ sign. My first requirement for a password is that I can use it to login, security actually comes second.</description>
		<content:encoded><![CDATA[<p>Punctuation symbols move on different keyboard layouts (letters too, but not so much, unless it&#8217;s French). Is the keyboard I&#8217;m using UK, US or Swiss? And no, often the keyboard layout doesn&#8217;t always match the keyboard appearance. I discovered this the hard way, trying to login from an Icelandic keyboard when my password contained a Â£ sign. My first requirement for a password is that I can use it to login, security actually comes second.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1132644</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1132644</guid>
		<description>This is my password, how secure is it?

klqwf43hfpo3uh4p;o4h4oif;3nfkjwen&#039;f3xr80[8u09</description>
		<content:encoded><![CDATA[<p>This is my password, how secure is it?</p>
<p>klqwf43hfpo3uh4p;o4h4oif;3nfkjwen&#8217;f3xr80[8u09</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitch_M</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131621</link>
		<dc:creator>Mitch_M</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131621</guid>
		<description>It takes three touches on a picture of a key to type some characters on an iPad, and the layout of the pictures of keys changes between applications. That and hearing &quot;Oh, you have an iPad! That&#039;s sooo cool!&quot; are the biggest annoyances of using an iPad for work. I did set up my password for something that I use only at work without special characters because of the multiple &quot;keystrokes&quot; per character feature.</description>
		<content:encoded><![CDATA[<p>It takes three touches on a picture of a key to type some characters on an iPad, and the layout of the pictures of keys changes between applications. That and hearing &#8220;Oh, you have an iPad! That&#8217;s sooo cool!&#8221; are the biggest annoyances of using an iPad for work. I did set up my password for something that I use only at work without special characters because of the multiple &#8220;keystrokes&#8221; per character feature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SamSam</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1132400</link>
		<dc:creator>SamSam</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1132400</guid>
		<description>Yes, if someone works out the system (which is slightly more complex than your suggestion, but only slightly).

But the idea was that each site had a cryptographically very secure password (14 alphanumeric mixed-case characters), and each site had a different password, all while being extremely easy to commit to memory.

So it would take a long time for someone to crack one of them, and even if one of the sites has a horrendous breach of security and was storying plain-text passwords (mine couldn&#039;t be rainbow-tabled), the hackers would need to be looking at all hundreds of thousands of passwords by hand, see mine and guess there was a system to it, rather than doing any of the kind of automated processing in the article above.

At least that was the idea.</description>
		<content:encoded><![CDATA[<p>Yes, if someone works out the system (which is slightly more complex than your suggestion, but only slightly).</p>
<p>But the idea was that each site had a cryptographically very secure password (14 alphanumeric mixed-case characters), and each site had a different password, all while being extremely easy to commit to memory.</p>
<p>So it would take a long time for someone to crack one of them, and even if one of the sites has a horrendous breach of security and was storying plain-text passwords (mine couldn&#8217;t be rainbow-tabled), the hackers would need to be looking at all hundreds of thousands of passwords by hand, see mine and guess there was a system to it, rather than doing any of the kind of automated processing in the article above.</p>
<p>At least that was the idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: quicksand</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131657</link>
		<dc:creator>quicksand</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131657</guid>
		<description>There&#039;s definitely a tradeoff with password crackability. How likely is it that someone will actually attack your password, versus just getting it off the server, or through a keylogger, or by raiding &#039;saved passwords&#039; or some other method. How valuable is that access anyway?

For most people, keeping difficult passwords  - right or wrong - just doesn&#039;t seem worth the effort.</description>
		<content:encoded><![CDATA[<p>There&#8217;s definitely a tradeoff with password crackability. How likely is it that someone will actually attack your password, versus just getting it off the server, or through a keylogger, or by raiding &#8216;saved passwords&#8217; or some other method. How valuable is that access anyway?</p>
<p>For most people, keeping difficult passwords  &#8211; right or wrong &#8211; just doesn&#8217;t seem worth the effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HotNachos</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131661</link>
		<dc:creator>HotNachos</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131661</guid>
		<description>Passwords are tools &amp; if this many people are unwilling or unable to use them &quot;properly&quot;, maybe the problem lies not with the users but with the tools offered to them. A system that requires human users to memorize &amp; have perfect recall of multiple unique, long &amp; complex passwords is a broken system. </description>
		<content:encoded><![CDATA[<p>Passwords are tools &#038; if this many people are unwilling or unable to use them &#8220;properly&#8221;, maybe the problem lies not with the users but with the tools offered to them. A system that requires human users to memorize &#038; have perfect recall of multiple unique, long &#038; complex passwords is a broken system. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AnthonyC</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1132949</link>
		<dc:creator>AnthonyC</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1132949</guid>
		<description>Assume, for simplicity, the following.
1) The service you&#039;re using is otherwise secure. That is, no one is going to simply steal your password and username out of their database.
2) The service is susceptible to (and only to) brute-force attempts. That it, it will not lock you out after some number of false passwords. Some banks and such only only a few wrong guesses before locking you out. In some cases you then have to wait and get a letter in the mail before re-setting the password.

In that case, the difficulty of cracking your password grows exponentially with length. There are 26 lower and 26 upper case letters, and 10 digits. The number of possible length-n alphanumeric passwords is then 62^n. That is 1.2^n times more than letter-only, and 2.4^n times more than lower-case only
A truly random bit string, using all possible ASCII characters including some you can&#039;t normally type, would give a password space of size 256^n. For a nine character password, this would be a billion time more difficult to guess than lowercase-only.

My premises are, of course, unreasonable. Hacking a server is much easier than guessing individual passwords. Taking advantage of password re-use is quite effective as well, I&#039;d expect.</description>
		<content:encoded><![CDATA[<p>Assume, for simplicity, the following.<br />
1) The service you&#8217;re using is otherwise secure. That is, no one is going to simply steal your password and username out of their database.<br />
2) The service is susceptible to (and only to) brute-force attempts. That it, it will not lock you out after some number of false passwords. Some banks and such only only a few wrong guesses before locking you out. In some cases you then have to wait and get a letter in the mail before re-setting the password.</p>
<p>In that case, the difficulty of cracking your password grows exponentially with length. There are 26 lower and 26 upper case letters, and 10 digits. The number of possible length-n alphanumeric passwords is then 62^n. That is 1.2^n times more than letter-only, and 2.4^n times more than lower-case only<br />
A truly random bit string, using all possible ASCII characters including some you can&#8217;t normally type, would give a password space of size 256^n. For a nine character password, this would be a billion time more difficult to guess than lowercase-only.</p>
<p>My premises are, of course, unreasonable. Hacking a server is much easier than guessing individual passwords. Taking advantage of password re-use is quite effective as well, I&#8217;d expect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: akwhitacre</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131674</link>
		<dc:creator>akwhitacre</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131674</guid>
		<description>I typed that into the attorney&#039;s calculator at my house closing and slid it across to my wife.

She didn&#039;t find it nearly as funny.</description>
		<content:encoded><![CDATA[<p>I typed that into the attorney&#8217;s calculator at my house closing and slid it across to my wife.</p>
<p>She didn&#8217;t find it nearly as funny.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IshMEL</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131685</link>
		<dc:creator>IshMEL</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131685</guid>
		<description>PasswordMaker is still my go-to solution -- I enter my &quot;easy&quot; password, it hashes it with the site URL and produces a strong password.</description>
		<content:encoded><![CDATA[<p>PasswordMaker is still my go-to solution &#8212; I enter my &#8220;easy&#8221; password, it hashes it with the site URL and produces a strong password.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: splint</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131435</link>
		<dc:creator>splint</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131435</guid>
		<description>Fat lot of good it did those 1 per centers with the complicated passwords.</description>
		<content:encoded><![CDATA[<p>Fat lot of good it did those 1 per centers with the complicated passwords.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brainspore</title>
		<link>http://boingboing.net/2011/06/06/comparative-analysis.html#comment-1131440</link>
		<dc:creator>Brainspore</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-1131440</guid>
		<description>My thoughts exactly. What&#039;s the point of coming up with a password that looks like you had a stroke while typing if the company you entrust it to can&#039;t keep it secret? Better to have a password like &quot;boobs&quot; with a company that has some decent security measures in place.</description>
		<content:encoded><![CDATA[<p>My thoughts exactly. What&#8217;s the point of coming up with a password that looks like you had a stroke while typing if the company you entrust it to can&#8217;t keep it secret? Better to have a password like &#8220;boobs&#8221; with a company that has some decent security measures in place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
