<?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: The Purpose of Passwords</title>
	<atom:link href="http://blog.nikolaidis.com/2006/08/19/the-purpose-of-passwords/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nikolaidis.com/2006/08/19/the-purpose-of-passwords/</link>
	<description>Aikido, comics, eating well, information security, open source, mountain biking, and caffeine - this blog has everything!</description>
	<lastBuildDate>Mon, 14 Jun 2010 01:57:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter&#8217;s Soapbox &#187; Basic World of Warcraft (and PC) Security Tips</title>
		<link>http://blog.nikolaidis.com/2006/08/19/the-purpose-of-passwords/comment-page-1/#comment-10596</link>
		<dc:creator>Peter&#8217;s Soapbox &#187; Basic World of Warcraft (and PC) Security Tips</dc:creator>
		<pubDate>Thu, 03 Jan 2008 21:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nikolaidis.com/?p=24#comment-10596</guid>
		<description>[...] The account was hacked by a brute force attack, so there&#8217;s nothing that could be done.  While this is certainly possible, it is more likely that the user logged on to a machine that was somehow compromised by spyware which logged the user&#8217;s keystrokes and phoned home with them. The best thing you can do in the case of a brute force attack would be to have a strong password, which is 8+ characters long, and contains a mixture of upper case, lower case, numeric, and non-alphanumeric (think &#8220;cartoon swearing&#8221;) characters. See this post on some ideas for picking a strong password. [...]</description>
		<content:encoded><![CDATA[<p>[...] The account was hacked by a brute force attack, so there&#8217;s nothing that could be done.  While this is certainly possible, it is more likely that the user logged on to a machine that was somehow compromised by spyware which logged the user&#8217;s keystrokes and phoned home with them. The best thing you can do in the case of a brute force attack would be to have a strong password, which is 8+ characters long, and contains a mixture of upper case, lower case, numeric, and non-alphanumeric (think &#8220;cartoon swearing&#8221;) characters. See this post on some ideas for picking a strong password. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
