<?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 cracking goes into&#160;hyperdrive</title>
	<atom:link href="http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html/feed" rel="self" type="application/rss+xml" />
	<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html</link>
	<description>Brain candy for Happy Mutants</description>
	<lastBuildDate>Sat, 25 May 2013 06:01: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: kaymac</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1514798</link>
		<dc:creator>kaymac</dc:creator>
		<pubDate>Wed, 22 Aug 2012 13:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1514798</guid>
		<description>My strategy is to use a few unique and pretty difficult passwords for high value sites like banking and email and pretty much a single 8 character password for e/thing else that won&#039;t affect me very much if it gets stolen. Go ahead and compromise my BoingBoing login. Not really a big whoop.

Is there a problem with this strategy that I&#039;m missing?</description>
		<content:encoded><![CDATA[<p>My strategy is to use a few unique and pretty difficult passwords for high value sites like banking and email and pretty much a single 8 character password for e/thing else that won&#8217;t affect me very much if it gets stolen. Go ahead and compromise my BoingBoing login. Not really a big whoop.</p>
<p>Is there a problem with this strategy that I&#8217;m missing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hinten</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1514714</link>
		<dc:creator>hinten</dc:creator>
		<pubDate>Wed, 22 Aug 2012 08:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1514714</guid>
		<description>Wow, four pages to say: &quot;Passwords are a weak security and identification mechanism.&quot; The time and effort would be better spend on discussing full alternatives: biometrics, token, certificates, etc.

Alternatives to password identification are required now.</description>
		<content:encoded><![CDATA[<p>Wow, four pages to say: &#8220;Passwords are a weak security and identification mechanism.&#8221; The time and effort would be better spend on discussing full alternatives: biometrics, token, certificates, etc.</p>
<p>Alternatives to password identification are required now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coderjoe</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1514398</link>
		<dc:creator>Coderjoe</dc:creator>
		<pubDate>Wed, 22 Aug 2012 00:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1514398</guid>
		<description> &quot;correct horse battery staple&quot;? That&#039;s amazing! I have the same password on my luggage!</description>
		<content:encoded><![CDATA[<p> &#8221;correct horse battery staple&#8221;? That&#8217;s amazing! I have the same password on my luggage!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adent1066</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1514151</link>
		<dc:creator>adent1066</dc:creator>
		<pubDate>Tue, 21 Aug 2012 20:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1514151</guid>
		<description>http://xkcd.com/936/ 
This is great password advice</description>
		<content:encoded><![CDATA[<p><a href="http://xkcd.com/936/" rel="nofollow">http://xkcd.com/936/</a><br />
This is great password advice</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antinous / Moderator</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1514145</link>
		<dc:creator>Antinous / Moderator</dc:creator>
		<pubDate>Tue, 21 Aug 2012 20:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1514145</guid>
		<description>You might enjoy shopping at penisland.net</description>
		<content:encoded><![CDATA[<p>You might enjoy shopping at penisland.net</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glaurung_quena</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1514031</link>
		<dc:creator>Glaurung_quena</dc:creator>
		<pubDate>Tue, 21 Aug 2012 19:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1514031</guid>
		<description>The biggest problem, of course, is the number of sites that have totally stupid password policies.  For instance, one of our banks (Bank of Montreal) insists that we must use a password of exactly 6 characters, no more, no less (and no symbols allowed).  So, insofar as they let you, the best practice is to use long (over 12 characters) passwords with symbols, mixed case, and spaces.  Use internal punctuation, capitalization, and numbers (not just appended at the beginning or end), but don&#039;t go overboard if you&#039;re planning on memorizing it. A short sentence, or the initial letters of a long sentence, can form the basis for something that&#039;s secure but easy to remember.  Length is far more important than complexity when it comes to making a password hard to crack.  

Never re-using any passwords ever is fine advice, but then you are stuck using a password manager, which means you won&#039;t be able to access your accounts from a public computer, or when using a borrowed phone.  And circumstances in which you find yourself without a computer/phone of your own (ie, your house burned down, you&#039;ve been robbed, your hard disk has crashed, etc) may be exactly the circumstances in which you will need to access your accounts.   

Fundamentally, when it comes to password re-use, you have to balance security and convenience, the safety of nobody being able to hack your accounts with the possibility you&#039;ll find yourself unable to access your accounts when you need them.  You also need to balance just how horrible it would be if someone hacked into each account -- you may not particularly care if your Facebook is hacked, or you might regard that as almost as bad as having your bank account hacked.  

The other huge problem is how your email is the key to unlocking your entire online life -- since almost every site allows password resets via email, if someone can hack into your email account, that gives them access to everything you&#039;ve linked to that account, regardless of whether or not your password was unique.  Using one email for social media logins and a different email for your banking is a start (and then set the backup email address for resetting those accounts to yet a third email), but fundamentally there&#039;s no good solution for this.
</description>
		<content:encoded><![CDATA[<p>The biggest problem, of course, is the number of sites that have totally stupid password policies.  For instance, one of our banks (Bank of Montreal) insists that we must use a password of exactly 6 characters, no more, no less (and no symbols allowed).  So, insofar as they let you, the best practice is to use long (over 12 characters) passwords with symbols, mixed case, and spaces.  Use internal punctuation, capitalization, and numbers (not just appended at the beginning or end), but don&#8217;t go overboard if you&#8217;re planning on memorizing it. A short sentence, or the initial letters of a long sentence, can form the basis for something that&#8217;s secure but easy to remember.  Length is far more important than complexity when it comes to making a password hard to crack.  </p>
<p>Never re-using any passwords ever is fine advice, but then you are stuck using a password manager, which means you won&#8217;t be able to access your accounts from a public computer, or when using a borrowed phone.  And circumstances in which you find yourself without a computer/phone of your own (ie, your house burned down, you&#8217;ve been robbed, your hard disk has crashed, etc) may be exactly the circumstances in which you will need to access your accounts.   </p>
<p>Fundamentally, when it comes to password re-use, you have to balance security and convenience, the safety of nobody being able to hack your accounts with the possibility you&#8217;ll find yourself unable to access your accounts when you need them.  You also need to balance just how horrible it would be if someone hacked into each account &#8212; you may not particularly care if your Facebook is hacked, or you might regard that as almost as bad as having your bank account hacked.  </p>
<p>The other huge problem is how your email is the key to unlocking your entire online life &#8212; since almost every site allows password resets via email, if someone can hack into your email account, that gives them access to everything you&#8217;ve linked to that account, regardless of whether or not your password was unique.  Using one email for social media logins and a different email for your banking is a start (and then set the backup email address for resetting those accounts to yet a third email), but fundamentally there&#8217;s no good solution for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boundegar</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513783</link>
		<dc:creator>Boundegar</dc:creator>
		<pubDate>Tue, 21 Aug 2012 16:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513783</guid>
		<description>So I guess I shouldn&#039;t use princess any more.  Sadness.</description>
		<content:encoded><![CDATA[<p>So I guess I shouldn&#8217;t use princess any more.  Sadness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513756</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 21 Aug 2012 16:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513756</guid>
		<description>Use a password manager (LastPass, 1Password, Keepass, etc.)

Generate a unique, random password for every site. The longer the better (as many characters as the field allows) . This is doubly true for your email accounts.
Do the same for &quot;Security Questions&quot;, which are notoriously weak. Don&#039;t even try to answer them, just fill in the answers with another randomly generated password.

Use two-factor authentication whenever available, and pressure any and all sites you use to implement two-factor authentication if they haven&#039;t already (Facebook and Gmail both implement two-factor authentication, so activate that and when possible use one of those to log in to other sites).</description>
		<content:encoded><![CDATA[<p>Use a password manager (LastPass, 1Password, Keepass, etc.)</p>
<p>Generate a unique, random password for every site. The longer the better (as many characters as the field allows) . This is doubly true for your email accounts.<br />
Do the same for &#8220;Security Questions&#8221;, which are notoriously weak. Don&#8217;t even try to answer them, just fill in the answers with another randomly generated password.</p>
<p>Use two-factor authentication whenever available, and pressure any and all sites you use to implement two-factor authentication if they haven&#8217;t already (Facebook and Gmail both implement two-factor authentication, so activate that and when possible use one of those to log in to other sites).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald Pottol</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513719</link>
		<dc:creator>Ronald Pottol</dc:creator>
		<pubDate>Tue, 21 Aug 2012 16:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513719</guid>
		<description>Lastpass comes close, I have a browser plug (Dolphin for Android) in on my phone as well as on the desktop, plus a phone app, so I can almost always copy-paste. Plus I use Google Authenticator on my phone. You do want to have your one time passwords written down though, so you can get in if you loose or wipe your phone.</description>
		<content:encoded><![CDATA[<p>Lastpass comes close, I have a browser plug (Dolphin for Android) in on my phone as well as on the desktop, plus a phone app, so I can almost always copy-paste. Plus I use Google Authenticator on my phone. You do want to have your one time passwords written down though, so you can get in if you loose or wipe your phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Baruch</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513715</link>
		<dc:creator>Robert Baruch</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513715</guid>
		<description>If you choose a weak password, meaning it happens to be one of the millions of common ones, then &lt;i&gt;any&lt;/i&gt; site &lt;i&gt;anywhere&lt;/i&gt; that has a breach can lead to your account being compromised, even if your account is not on the breached site. All because you chose a weak password.

Suppose you choose one common English word out of a list of, say, 1000. Then you can be almost certain that your password is in the list of common passwords.

If, however, your password is, say, four English words out of that same list of 1000, then that list of common passwords would have to be 10^12 items long in order to contain your password with certainty. Or it would have to do an O(N^4) search, which is ludicrous. Use five words to be sure, though -- 10^12 items is probably within reach real soon now. Using a 40-bit code for each entry, you&#039;d only need 5 terabytes for that list.

So I do think the strength of your password is key (ha ha), and you can&#039;t hope that every site everywhere is secure.</description>
		<content:encoded><![CDATA[<p>If you choose a weak password, meaning it happens to be one of the millions of common ones, then <i>any</i> site <i>anywhere</i> that has a breach can lead to your account being compromised, even if your account is not on the breached site. All because you chose a weak password.</p>
<p>Suppose you choose one common English word out of a list of, say, 1000. Then you can be almost certain that your password is in the list of common passwords.</p>
<p>If, however, your password is, say, four English words out of that same list of 1000, then that list of common passwords would have to be 10^12 items long in order to contain your password with certainty. Or it would have to do an O(N^4) search, which is ludicrous. Use five words to be sure, though &#8212; 10^12 items is probably within reach real soon now. Using a 40-bit code for each entry, you&#8217;d only need 5 terabytes for that list.</p>
<p>So I do think the strength of your password is key (ha ha), and you can&#8217;t hope that every site everywhere is secure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TaymonBeal</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513682</link>
		<dc:creator>TaymonBeal</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513682</guid>
		<description>As a developer, I believe not only that password security is not very good in the best case, but also that if I attempted to implement my own password storage scheme, I&#039;d almost certainly screw it up.

So I use OpenID for authentication whenever possible.</description>
		<content:encoded><![CDATA[<p>As a developer, I believe not only that password security is not very good in the best case, but also that if I attempted to implement my own password storage scheme, I&#8217;d almost certainly screw it up.</p>
<p>So I use OpenID for authentication whenever possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thorzdad</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513680</link>
		<dc:creator>Thorzdad</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513680</guid>
		<description>The issue seems to be less the passwords users choose, and more in the security of the db on websites themselves.</description>
		<content:encoded><![CDATA[<p>The issue seems to be less the passwords users choose, and more in the security of the db on websites themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TaymonBeal</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513678</link>
		<dc:creator>TaymonBeal</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513678</guid>
		<description>&lt;a href=&quot;http://www.codinghorror.com/blog/2011/09/cutting-the-gordian-knot-of-web-identity.html&quot; rel=&quot;nofollow&quot;&gt;Jeff Atwood has a good essay on exactly this.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://www.codinghorror.com/blog/2011/09/cutting-the-gordian-knot-of-web-identity.html" rel="nofollow">Jeff Atwood has a good essay on exactly this.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johne Cook</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513674</link>
		<dc:creator>Johne Cook</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513674</guid>
		<description>Ah, &#039;Kee Pass.&#039; I had the emPHAsis on the wrong sylLable. ;)</description>
		<content:encoded><![CDATA[<p>Ah, &#8216;Kee Pass.&#8217; I had the emPHAsis on the wrong sylLable. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sigdrifa</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513673</link>
		<dc:creator>sigdrifa</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513673</guid>
		<description>Yeah, that&#039;s pretty much why I could never get exited about online services for this purpose. I prefer offline software with a locally stored database as a password manager.</description>
		<content:encoded><![CDATA[<p>Yeah, that&#8217;s pretty much why I could never get exited about online services for this purpose. I prefer offline software with a locally stored database as a password manager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sigdrifa</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513672</link>
		<dc:creator>sigdrifa</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513672</guid>
		<description>Keepass works just fine. And there&#039;s a portable app, too. 

http://keepass.info</description>
		<content:encoded><![CDATA[<p>Keepass works just fine. And there&#8217;s a portable app, too. </p>
<p><a href="http://keepass.info" rel="nofollow">http://keepass.info</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sincarne</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513662</link>
		<dc:creator>sincarne</dc:creator>
		<pubDate>Tue, 21 Aug 2012 15:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513662</guid>
		<description>1Password mostly fits the bill: Mac, iOS, PC, Android clients. You can get a lovely read-only look at your passwords if you store your database online. The only criticism is some Ajax-y log-in forms can confuse it.

As to how easy it is, I&#039;ve got my (admittedly slightly techie) retiree parents using it.

https://agilebits.com/onepassword</description>
		<content:encoded><![CDATA[<p>1Password mostly fits the bill: Mac, iOS, PC, Android clients. You can get a lovely read-only look at your passwords if you store your database online. The only criticism is some Ajax-y log-in forms can confuse it.</p>
<p>As to how easy it is, I&#8217;ve got my (admittedly slightly techie) retiree parents using it.</p>
<p><a href="https://agilebits.com/onepassword" rel="nofollow">https://agilebits.com/onepassword</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: monkeyfufu</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513651</link>
		<dc:creator>monkeyfufu</dc:creator>
		<pubDate>Tue, 21 Aug 2012 14:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513651</guid>
		<description>True - the password manager would need to be easy enough for a non-tech to use.   And it would need to be that same ease on every system.  Even at work.  Otherwise, a randomly generated password just means I can&#039;t get to any of my accounts on certain computers.  </description>
		<content:encoded><![CDATA[<p>True &#8211; the password manager would need to be easy enough for a non-tech to use.   And it would need to be that same ease on every system.  Even at work.  Otherwise, a randomly generated password just means I can&#8217;t get to any of my accounts on certain computers.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513648</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Tue, 21 Aug 2012 14:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513648</guid>
		<description>&quot;Password Manager&quot; simple?
If you can suggest one that allows easy access from PC/MAC/Android/iPhone and is generically accessible from browsers out on the internet (i.e. machines I don&#039;t own and can&#039;t install software on) and cope properly with the huge range of login mechanisms then I can probably come up with a handful of other features it lacks (to make it as easy as having a password in your head).

I think that a decently uncrackable source for ID and authentication could be something for governments to look at instead of fartling around trying to prevent kids from downloading porn and the like. 
(Except that like any government IT project it would be doomed to be a massive failure from inception till about 5-10 years later when everyone realises they&#039;ve ironed out the bugs and it&#039;s actually not bad.)</description>
		<content:encoded><![CDATA[<p>&#8220;Password Manager&#8221; simple?<br />
If you can suggest one that allows easy access from PC/MAC/Android/iPhone and is generically accessible from browsers out on the internet (i.e. machines I don&#8217;t own and can&#8217;t install software on) and cope properly with the huge range of login mechanisms then I can probably come up with a handful of other features it lacks (to make it as easy as having a password in your head).</p>
<p>I think that a decently uncrackable source for ID and authentication could be something for governments to look at instead of fartling around trying to prevent kids from downloading porn and the like. <br />
(Except that like any government IT project it would be doomed to be a massive failure from inception till about 5-10 years later when everyone realises they&#8217;ve ironed out the bugs and it&#8217;s actually not bad.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Nelson</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513633</link>
		<dc:creator>Sean Nelson</dc:creator>
		<pubDate>Tue, 21 Aug 2012 14:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513633</guid>
		<description>If LastPass and/or Yubikey ever gets compromised, I&#039;m screwed.</description>
		<content:encoded><![CDATA[<p>If LastPass and/or Yubikey ever gets compromised, I&#8217;m screwed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sigdrifa</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513625</link>
		<dc:creator>sigdrifa</dc:creator>
		<pubDate>Tue, 21 Aug 2012 14:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513625</guid>
		<description>I guess something as simple as a password manager and randomly generated passwords would be enough if you only could convince non-technical people to use them. _That&#039;s_ the hard part.</description>
		<content:encoded><![CDATA[<p>I guess something as simple as a password manager and randomly generated passwords would be enough if you only could convince non-technical people to use them. _That&#8217;s_ the hard part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johne Cook</title>
		<link>http://boingboing.net/2012/08/21/password-cracking-goes-into-hy.html#comment-1513611</link>
		<dc:creator>Johne Cook</dc:creator>
		<pubDate>Tue, 21 Aug 2012 13:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://boingboing.net/?p=177348#comment-1513611</guid>
		<description>So what should a good password look like? Is it time for the passphrase? Passparagraphs? Retina scans?</description>
		<content:encoded><![CDATA[<p>So what should a good password look like? Is it time for the passphrase? Passparagraphs? Retina scans?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
