<?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: When did Marcus Ranum get generic (and destructive)?</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=307" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=307</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Pete</title>
		<link>http://spiresecurity.com/?p=307&#038;cpage=1#comment-431</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Wed, 30 May 2007 18:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=307#comment-431</guid>
		<description><![CDATA[@Dan -

You make my point well - a &quot;strong&quot; password is not going to protect against that type of attack at all - you are better off picking a pseudo-strong one (i.e. one that can survive a handful of guesses) that can be memorized and logging the hell out of the system. And the more obvious solution is multi-factor authentication.

But there is little/no need to even get that complex. Consider the recent case with MySpace passwords being collected through a phishing attack - in that case, it doesn&#039;t matter if your password is 50 alpha-numeric random characters - you&#039;re dead.
]]></description>
		<content:encoded><![CDATA[<p>@Dan -</p>
<p>You make my point well &#8211; a &#8220;strong&#8221; password is not going to protect against that type of attack at all &#8211; you are better off picking a pseudo-strong one (i.e. one that can survive a handful of guesses) that can be memorized and logging the hell out of the system. And the more obvious solution is multi-factor authentication.</p>
<p>But there is little/no need to even get that complex. Consider the recent case with MySpace passwords being collected through a phishing attack &#8211; in that case, it doesn&#8217;t matter if your password is 50 alpha-numeric random characters &#8211; you&#8217;re dead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Weber</title>
		<link>http://spiresecurity.com/?p=307&#038;cpage=1#comment-430</link>
		<dc:creator>Dan Weber</dc:creator>
		<pubDate>Wed, 30 May 2007 18:31:18 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=307#comment-430</guid>
		<description><![CDATA[&gt;&gt; a good example? Well, Marcus uses passwords. Let me tell you,
&gt;&gt; anyone fighting the &quot;strong password&quot; battle is completely
&gt;&gt; missing the new(/old) threat models out there.

In general, I agree, in that weak passwords aren&#039;t what&#039;s going to be causing new troubles.

However, given all the functionality/vulnerability that Web 2.0 is opening up, I think we could be surprised by just comes in the future.

Imagine, for example, a CSRF attack distributed by XSS, essentially turning millions of browsers into millions of password-guessers.

(Of course, you could legitimately ask why they aren&#039;t using their botnets for that right now.  My point is that since the attackers have shown that their imaginations generally outstrip ours, declaring any particular vector as over-and-done seems premature.)
]]></description>
		<content:encoded><![CDATA[<p>>> a good example? Well, Marcus uses passwords. Let me tell you,<br />
>> anyone fighting the &#8220;strong password&#8221; battle is completely<br />
>> missing the new(/old) threat models out there.</p>
<p>In general, I agree, in that weak passwords aren&#8217;t what&#8217;s going to be causing new troubles.</p>
<p>However, given all the functionality/vulnerability that Web 2.0 is opening up, I think we could be surprised by just comes in the future.</p>
<p>Imagine, for example, a CSRF attack distributed by XSS, essentially turning millions of browsers into millions of password-guessers.</p>
<p>(Of course, you could legitimately ask why they aren&#8217;t using their botnets for that right now.  My point is that since the attackers have shown that their imaginations generally outstrip ours, declaring any particular vector as over-and-done seems premature.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
