<?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 for Ryan Day</title>
	<atom:link href="http://www.ryanday.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ryanday.net</link>
	<description>freelance product development</description>
	<lastBuildDate>Fri, 23 Sep 2011 15:51:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Password Insecurity Quickfix by Ryan Day</title>
		<link>http://www.ryanday.net/2011/09/23/password-insecurity-quickfix/comment-page-1/#comment-567</link>
		<dc:creator>Ryan Day</dc:creator>
		<pubDate>Fri, 23 Sep 2011 15:51:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanday.net/?p=626#comment-567</guid>
		<description>Sure, if you really required a grammatically correct English sentence, password crackers would be able to be tailored to that.

But right now the majority of passwords are only 1 word, with 1 instead of i and 0 instead of 0. If we are going to build a cracker to not use brute force, it is still easier to run through a dictionary replacing letters with numbers.</description>
		<content:encoded><![CDATA[<p>Sure, if you really required a grammatically correct English sentence, password crackers would be able to be tailored to that.</p>
<p>But right now the majority of passwords are only 1 word, with 1 instead of i and 0 instead of 0. If we are going to build a cracker to not use brute force, it is still easier to run through a dictionary replacing letters with numbers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Password Insecurity Quickfix by Erik</title>
		<link>http://www.ryanday.net/2011/09/23/password-insecurity-quickfix/comment-page-1/#comment-566</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Fri, 23 Sep 2011 15:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanday.net/?p=626#comment-566</guid>
		<description>Requiring &quot;at least three words&quot; would encourage people to use sentences, which then become *more* crackable then 3 letter passwords. 

Users are likely to use actual sentences, effectively reducing the complexity of their passwords. &quot;My dog has fleas&quot; (or something similar, probably &quot;This is my password&quot;) would simply become the new &quot;password1&quot;.</description>
		<content:encoded><![CDATA[<p>Requiring &#8220;at least three words&#8221; would encourage people to use sentences, which then become *more* crackable then 3 letter passwords. </p>
<p>Users are likely to use actual sentences, effectively reducing the complexity of their passwords. &#8220;My dog has fleas&#8221; (or something similar, probably &#8220;This is my password&#8221;) would simply become the new &#8220;password1&#8243;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nasdaq ITCH by Nasdaq archives &#124; Irisnicolef</title>
		<link>http://www.ryanday.net/2011/08/21/nasdaq-itch/comment-page-1/#comment-565</link>
		<dc:creator>Nasdaq archives &#124; Irisnicolef</dc:creator>
		<pubDate>Thu, 22 Sep 2011 09:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanday.net/?p=573#comment-565</guid>
		<description>[...] Ryan Day &#187; Blog Archive &#187; Nasdaq ITCHAug 21, 2011 &#8230; Ryan Day &#187; Blog Archive &#187; Nasdaq ITCH Says: August 25th, 2011 at 10:08 pm. [.. .] the original post: Ryan Day &#187; Blog Archive &#187; Nasdaq ITCH &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Ryan Day &#187; Blog Archive &#187; Nasdaq ITCHAug 21, 2011 &#8230; Ryan Day &#187; Blog Archive &#187; Nasdaq ITCH Says: August 25th, 2011 at 10:08 pm. [.. .] the original post: Ryan Day &#187; Blog Archive &#187; Nasdaq ITCH &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nasdaq ITCH by Scratching the Itch &#124; Rex Flex</title>
		<link>http://www.ryanday.net/2011/08/21/nasdaq-itch/comment-page-1/#comment-560</link>
		<dc:creator>Scratching the Itch &#124; Rex Flex</dc:creator>
		<pubDate>Fri, 02 Sep 2011 07:05:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanday.net/?p=573#comment-560</guid>
		<description>[...] ( 0 )Scratching the ItchA couple of weeks ago I found an article by Ryan Day about implementing the Nasdaq ITCH protocol in python. I was really excited about this because I had always thought the barriers to [...]</description>
		<content:encoded><![CDATA[<p>[...] ( 0 )Scratching the ItchA couple of weeks ago I found an article by Ryan Day about implementing the Nasdaq ITCH protocol in python. I was really excited about this because I had always thought the barriers to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nasdaq ITCH by Ryan Day » Blog Archive » Nasdaq ITCH</title>
		<link>http://www.ryanday.net/2011/08/21/nasdaq-itch/comment-page-1/#comment-549</link>
		<dc:creator>Ryan Day » Blog Archive » Nasdaq ITCH</dc:creator>
		<pubDate>Fri, 26 Aug 2011 03:08:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanday.net/?p=573#comment-549</guid>
		<description>[...] the original post: Ryan Day » Blog Archive » Nasdaq ITCH   Comments [0]Digg [...]</description>
		<content:encoded><![CDATA[<p>[...] the original post: Ryan Day » Blog Archive » Nasdaq ITCH   Comments [0]Digg [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nasdaq ITCH by Andy</title>
		<link>http://www.ryanday.net/2011/08/21/nasdaq-itch/comment-page-1/#comment-548</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 24 Aug 2011 13:11:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanday.net/?p=573#comment-548</guid>
		<description>Thanks, Ryan!</description>
		<content:encoded><![CDATA[<p>Thanks, Ryan!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

