<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: How to Choose a Good Password</title>
	<atom:link href="http://www.securitycatalyst.com/how-to-choose-a-good-password/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.securitycatalyst.com/how-to-choose-a-good-password/</link>
	<description>Michael Santarcangelo delivers Awareness that Works™</description>
	<lastBuildDate>Mon, 28 Jun 2010 13:51:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://www.securitycatalyst.com/how-to-choose-a-good-password/comment-page-1/#comment-894</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 31 Mar 2009 12:24:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=1369#comment-894</guid>
		<description>Strength is determined as a factor of the overall &quot;key space&quot; and the length. Assuming uppercase, lowercase digits and non-alpha characters are allowed, then the longer password is better. While we like to beat people about the head and shoulders to suggest they need to choose inane combinations as a password, taking two words that they know, and joining them together with some non-standard characters creates a long password that should not fall prey to dictionary attacks.</description>
		<content:encoded><![CDATA[<p>Strength is determined as a factor of the overall &#8220;key space&#8221; and the length. Assuming uppercase, lowercase digits and non-alpha characters are allowed, then the longer password is better. While we like to beat people about the head and shoulders to suggest they need to choose inane combinations as a password, taking two words that they know, and joining them together with some non-standard characters creates a long password that should not fall prey to dictionary attacks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Intern's Revenge</title>
		<link>http://www.securitycatalyst.com/how-to-choose-a-good-password/comment-page-1/#comment-893</link>
		<dc:creator>Intern's Revenge</dc:creator>
		<pubDate>Tue, 31 Mar 2009 04:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.securitycatalyst.com/?p=1369#comment-893</guid>
		<description>Thanks guys! I was looking for a good clip to segue into a brief discussion about basic password policies over at the Intern&#039;s Revenge blog. Although I was a little surprised about advising people to use two dictionary words as a &quot;strong password.&quot; Am I alone in thinking that&#039;s not good practice?</description>
		<content:encoded><![CDATA[<p>Thanks guys! I was looking for a good clip to segue into a brief discussion about basic password policies over at the Intern&#8217;s Revenge blog. Although I was a little surprised about advising people to use two dictionary words as a &#8220;strong password.&#8221; Am I alone in thinking that&#8217;s not good practice?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
