<?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: Building Strong and Memorable Passwords (Part 4 of 4)</title>
	<atom:link href="http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/feed/" rel="self" type="application/rss+xml" />
	<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/</link>
	<description>Home of Todd Sieling's product design and strategy services for the web.</description>
	<lastBuildDate>Thu, 11 Mar 2010 06:26:24 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave</title>
		<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/comment-page-1/#comment-5</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-5</guid>
		<description>Changing your password frequently would just be a matter of changing the first dictionary/foreign word.

The true enemies of secure passwords are restrictive and inconsistent policies.  The example password above would qualify for most password policies but not for all.  I have seen policies that state that the password must be in between 5 and 8 characters.  I have also seen many systems where only the first 8 characters were used, regardless of the true length of the password.

In my own workplace we have several inconsistent password policies.  (There&#039;s actually only one, officially mandated policy but every department implements it differently.)

Some passwords must be changed monthly, some every three months.  Some are unrestricted, some must have at least one capital and at least one number, one must have **two** numbers... no more, no less and won&#039;t accept any &quot;special&quot; characters although no one has defined what &quot;special&quot; characters are and finally some must have all of the above **and** special characters.

My only saving grace is that I **can** remember lots of horribly complex passwords.

Anyway, enough of my rant.  Nice suggestions and a very good password choosing guide for anyone with a sane workplace.</description>
		<content:encoded><![CDATA[<p>Changing your password frequently would just be a matter of changing the first dictionary/foreign word.</p>
<p>The true enemies of secure passwords are restrictive and inconsistent policies.  The example password above would qualify for most password policies but not for all.  I have seen policies that state that the password must be in between 5 and 8 characters.  I have also seen many systems where only the first 8 characters were used, regardless of the true length of the password.</p>
<p>In my own workplace we have several inconsistent password policies.  (There&#8217;s actually only one, officially mandated policy but every department implements it differently.)</p>
<p>Some passwords must be changed monthly, some every three months.  Some are unrestricted, some must have at least one capital and at least one number, one must have **two** numbers&#8230; no more, no less and won&#8217;t accept any &#8220;special&#8221; characters although no one has defined what &#8220;special&#8221; characters are and finally some must have all of the above **and** special characters.</p>
<p>My only saving grace is that I **can** remember lots of horribly complex passwords.</p>
<p>Anyway, enough of my rant.  Nice suggestions and a very good password choosing guide for anyone with a sane workplace.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Acronyms</title>
		<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/comment-page-1/#comment-6</link>
		<dc:creator>Acronyms</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-6</guid>
		<description>So hackers can&#039;t access foreign dictionaries? Instead take a memorable line from a song/poem/simpsons quote/whatever. Use the first letter of each word. Eg, &quot;Alas poor Yorrick I knew him well&quot; Apyikhw.</description>
		<content:encoded><![CDATA[<p>So hackers can&#8217;t access foreign dictionaries? Instead take a memorable line from a song/poem/simpsons quote/whatever. Use the first letter of each word. Eg, &#8220;Alas poor Yorrick I knew him well&#8221; Apyikhw.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xan</title>
		<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/comment-page-1/#comment-7</link>
		<dc:creator>xan</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-7</guid>
		<description>What is wrong with password1?</description>
		<content:encoded><![CDATA[<p>What is wrong with password1?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/comment-page-1/#comment-8</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-8</guid>
		<description>Very good article! One addition to a foreign language word is pick a word that means something to you and alter the spelling (ie. I use an old misspelt street address backwards). Easy for me to remember. I also find after a little while your hands can almost type the passwords themselves (scary I know!). Anyway that&#039;s my 2c worth</description>
		<content:encoded><![CDATA[<p>Very good article! One addition to a foreign language word is pick a word that means something to you and alter the spelling (ie. I use an old misspelt street address backwards). Easy for me to remember. I also find after a little while your hands can almost type the passwords themselves (scary I know!). Anyway that&#8217;s my 2c worth</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ewok</title>
		<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/comment-page-1/#comment-9</link>
		<dc:creator>ewok</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-9</guid>
		<description>Great thing about password1 is that you can use it again next quarter by changing it to password2 ;) The fun rolls on!</description>
		<content:encoded><![CDATA[<p>Great thing about password1 is that you can use it again next quarter by changing it to password2 <img src='http://corvusconsulting.ca/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  The fun rolls on!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bleh</title>
		<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/comment-page-1/#comment-10</link>
		<dc:creator>bleh</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-10</guid>
		<description>I always use temp1234, is that secure enough?</description>
		<content:encoded><![CDATA[<p>I always use temp1234, is that secure enough?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan</title>
		<link>http://corvusconsulting.ca/2007/10/building-strong-and-memorable-passwords-part-4-of-4/comment-page-1/#comment-11</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-11</guid>
		<description>I allways use a bit of leet-speak. Changing o&#039;s to 0&#039;s (zeros), I to 1, T to 7, and so on

H3ll0W0r1d</description>
		<content:encoded><![CDATA[<p>I allways use a bit of leet-speak. Changing o&#8217;s to 0&#8217;s (zeros), I to 1, T to 7, and so on</p>
<p>H3ll0W0r1d</p>
]]></content:encoded>
	</item>
</channel>
</rss>
