<?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: Are you using strong and unique passwords? You should!</title>
	<atom:link href="http://www.spylogic.net/2008/08/are-you-using-strong-and-unique-passwords-you-should/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spylogic.net/2008/08/are-you-using-strong-and-unique-passwords-you-should/</link>
	<description></description>
	<lastBuildDate>Sun, 18 Sep 2011 21:48:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Quzart</title>
		<link>http://www.spylogic.net/2008/08/are-you-using-strong-and-unique-passwords-you-should/comment-page-1/#comment-81</link>
		<dc:creator>Quzart</dc:creator>
		<pubDate>Sat, 16 Aug 2008 17:01:49 +0000</pubDate>
		<guid isPermaLink="false">#comment-81</guid>
		<description>Agreed, partially. It&#039;s good to have a separate password for each application. Only the part of storing passwords together in one place bothers me. That&#039;s why I just keep them all in my head. It isn&#039;t as difficult as you might think ... it only takes about 15 minutes (in the end) to remember a password forever, even the ones with more than 15 and _exotic_ characters.&lt;br /&gt;
You could also use Japanese/Chinese characters in your passwords (like me), problem is that sometimes the password is first converted to the html/UTF-8 equivalent ( &amp;something; ) and then stored. Luckily the html/UTF-8 equivalent is probably more than 6 characters in length, so you should be ok. Another problem is that you must have a computer that can convert romanji (Japanese written using Latin alphabet) to kana (Japanese characters). Some knowledge of the language is useful too ^^.&lt;br /&gt;
&lt;br /&gt;
It shows that LinkedIn perhaps isn&#039;t hashing the passwords before storing it in their database, which obviously isn&#039;t good at all.</description>
		<content:encoded><![CDATA[<p>Agreed, partially. It&#8217;s good to have a separate password for each application. Only the part of storing passwords together in one place bothers me. That&#8217;s why I just keep them all in my head. It isn&#8217;t as difficult as you might think &#8230; it only takes about 15 minutes (in the end) to remember a password forever, even the ones with more than 15 and _exotic_ characters.<br />
You could also use Japanese/Chinese characters in your passwords (like me), problem is that sometimes the password is first converted to the html/UTF-8 equivalent ( &amp;something; ) and then stored. Luckily the html/UTF-8 equivalent is probably more than 6 characters in length, so you should be ok. Another problem is that you must have a computer that can convert romanji (Japanese written using Latin alphabet) to kana (Japanese characters). Some knowledge of the language is useful too ^^.</p>
<p>It shows that LinkedIn perhaps isn&#8217;t hashing the passwords before storing it in their database, which obviously isn&#8217;t good at all.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

