<?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: Morons Release Beautiful Attack</title>
	<atom:link href="http://www.links.org/?feed=rss2&#038;p=477" rel="self" type="application/rss+xml" />
	<link>http://www.links.org/?p=477</link>
	<description>Ben Laurie blathering</description>
	<lastBuildDate>Fri, 27 Aug 2010 13:41:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Certyfikat klucza publicznego &#124; hilpers</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-277895</link>
		<dc:creator>Certyfikat klucza publicznego &#124; hilpers</dc:creator>
		<pubDate>Sun, 18 Jan 2009 15:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-277895</guid>
		<description></description>
		<content:encoded><![CDATA[<p>[...] złamać klucz takiego urzędu. Istnieje też inne Jakby niedawno okazało się, że nie musiałby. <a href="http://www.links.org/?p=477" rel="nofollow">http://www.links.org/?p=477</a> <a href="https://blog.startcom.org/?p=145" rel="nofollow">https://blog.startcom.org/?p=145</a>  &#8212; Dariusz Sznajder [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Threadgill</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274274</link>
		<dc:creator>Richard Threadgill</dc:creator>
		<pubDate>Wed, 31 Dec 2008 21:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274274</guid>
		<description>&gt; Ironically, their attack is rendered somewhat pointless right now..

Not really.  The md5-based attack allows a man-in-the-middle to attack *all* ssl sessions flowing their proxy, a bogus certificate attack only allows the attacker to spoof all sessions involving the site for which they&#039;ve spoofed a certificate.</description>
		<content:encoded><![CDATA[<p>&gt; Ironically, their attack is rendered somewhat pointless right now..</p>
<p>Not really.  The md5-based attack allows a man-in-the-middle to attack *all* ssl sessions flowing their proxy, a bogus certificate attack only allows the attacker to spoof all sessions involving the site for which they&#8217;ve spoofed a certificate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Infiltrated&#8217;s Security Predictions for 2009 &#124; We Break Things</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274259</link>
		<dc:creator>Infiltrated&#8217;s Security Predictions for 2009 &#124; We Break Things</dc:creator>
		<pubDate>Wed, 31 Dec 2008 17:37:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274259</guid>
		<description>[...] http://www.links.org/?p=477 [2] http://www.ietf.org/mail-archive/web/saag/current/msg02369.html [3] [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.links.org/?p=477" rel="nofollow">http://www.links.org/?p=477</a> [2] <a href="http://www.ietf.org/mail-archive/web/saag/current/msg02369.html" rel="nofollow">http://www.ietf.org/mail-archive/web/saag/current/msg02369.html</a> [3] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Mason</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274222</link>
		<dc:creator>Justin Mason</dc:creator>
		<pubDate>Wed, 31 Dec 2008 11:00:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274222</guid>
		<description>Charles -- yep, that part is another good example of the &lt;a href=&quot;http://joshua.schachter.org/2007/01/autoincrement.html&quot; rel=&quot;nofollow&quot;&gt;autoincrement considered harmful&lt;/a&gt; antipattern.</description>
		<content:encoded><![CDATA[<p>Charles &#8212; yep, that part is another good example of the <a href="http://joshua.schachter.org/2007/01/autoincrement.html" rel="nofollow">autoincrement considered harmful</a> antipattern.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Darke</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274130</link>
		<dc:creator>Charles Darke</dc:creator>
		<pubDate>Tue, 30 Dec 2008 22:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274130</guid>
		<description>Great attack, but I feel that the CA not taking the precaution of introducing sufficient element of randomness in what it signs is also a significant factor. 

Even if they only introduced a 32bit random, it would have helped.</description>
		<content:encoded><![CDATA[<p>Great attack, but I feel that the CA not taking the precaution of introducing sufficient element of randomness in what it signs is also a significant factor. </p>
<p>Even if they only introduced a 32bit random, it would have helped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johans</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274121</link>
		<dc:creator>johans</dc:creator>
		<pubDate>Tue, 30 Dec 2008 22:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274121</guid>
		<description>These researchers have been warning about such md5 collisions for years. In 2006 they published X.509 certificates in different names with identical md5 hashes to get a wider audience for the md5-collision attacks that were found a year earlier. The paper (which was widely quoted at the time) should still be at http://www.win.tue.nl/hashclash/TargetCollidingCertificates/. In 2007 they published signed PDF documents predicting the outcome of the US-presidential elections (http://www.win.tue.nl/hashclash/Nostradamus/) - people laughed a bit and mostly ignored it. Stevens, De Weger and Lenstra have been telling everybody who would listen that people should stop using md5-signed X.509 certificates and documents; but didn&#039;t find much of an audience outside the academic world.

I must say that I didn&#039;t think of the specific application they published now either. But the basic md5-collission isn&#039;t surprising. You should realise that these are academics (mathematicians), trying to persuade the computer community to stop using md5 for these kind of applications - not software hackers who are out to break systems. Yes, their approach was too rash, but it seems that finally they managed to get people to stop and listen.</description>
		<content:encoded><![CDATA[<p>These researchers have been warning about such md5 collisions for years. In 2006 they published X.509 certificates in different names with identical md5 hashes to get a wider audience for the md5-collision attacks that were found a year earlier. The paper (which was widely quoted at the time) should still be at <a href="http://www.win.tue.nl/hashclash/TargetCollidingCertificates/" rel="nofollow">http://www.win.tue.nl/hashclash/TargetCollidingCertificates/</a>. In 2007 they published signed PDF documents predicting the outcome of the US-presidential elections (<a href="http://www.win.tue.nl/hashclash/Nostradamus/" rel="nofollow">http://www.win.tue.nl/hashclash/Nostradamus/</a>) &#8211; people laughed a bit and mostly ignored it. Stevens, De Weger and Lenstra have been telling everybody who would listen that people should stop using md5-signed X.509 certificates and documents; but didn&#8217;t find much of an audience outside the academic world.</p>
<p>I must say that I didn&#8217;t think of the specific application they published now either. But the basic md5-collission isn&#8217;t surprising. You should realise that these are academics (mathematicians), trying to persuade the computer community to stop using md5 for these kind of applications &#8211; not software hackers who are out to break systems. Yes, their approach was too rash, but it seems that finally they managed to get people to stop and listen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links &#187; More on MD5 Collisions</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274098</link>
		<dc:creator>Links &#187; More on MD5 Collisions</dc:creator>
		<pubDate>Tue, 30 Dec 2008 20:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274098</guid>
		<description>[...] LinksThe Rest I Just Squandered     &#171; Morons Release Beautiful Attack [...]</description>
		<content:encoded><![CDATA[<p>[...] LinksThe Rest I Just Squandered     &laquo; Morons Release Beautiful Attack [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kragen Javier Sitaker</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274089</link>
		<dc:creator>Kragen Javier Sitaker</dc:creator>
		<pubDate>Tue, 30 Dec 2008 19:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274089</guid>
		<description>It appears that your accusation that they are morons boils down to this: &quot;Users could have been protected from this exploit quite easily - only browsers and CAs had to be notified, which is easily achievable without premature public disclosure.&quot;  But according to (second-hand reports of) the researchers&#039; talk, they did notify the browser vendors and CAs.  If that is the case, does that make them not morons?  If that turns out to be the case, maybe you should be more careful in the future about calling people names in public before getting your facts straight.</description>
		<content:encoded><![CDATA[<p>It appears that your accusation that they are morons boils down to this: &#8220;Users could have been protected from this exploit quite easily &#8211; only browsers and CAs had to be notified, which is easily achievable without premature public disclosure.&#8221;  But according to (second-hand reports of) the researchers&#8217; talk, they did notify the browser vendors and CAs.  If that is the case, does that make them not morons?  If that turns out to be the case, maybe you should be more careful in the future about calling people names in public before getting your facts straight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cat</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274080</link>
		<dc:creator>Cat</dc:creator>
		<pubDate>Tue, 30 Dec 2008 18:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274080</guid>
		<description>Justin - that sounds like &quot;clearly the &#039;bad guys&#039; aren&#039;t going to be smart/fast about developing  a useful exploit&quot; to me... and that&#039;s clearly a terrible assumption to make.</description>
		<content:encoded><![CDATA[<p>Justin &#8211; that sounds like &#8220;clearly the &#8216;bad guys&#8217; aren&#8217;t going to be smart/fast about developing  a useful exploit&#8221; to me&#8230; and that&#8217;s clearly a terrible assumption to make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ARG</title>
		<link>http://www.links.org/?p=477&#038;cpage=1#comment-274079</link>
		<dc:creator>ARG</dc:creator>
		<pubDate>Tue, 30 Dec 2008 18:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.links.org/?p=477#comment-274079</guid>
		<description>I don&#039;t get what your beef is. They&#039;ve reconstructed a pointless attack that will cripple teh Interwebs! I mean everyone is efermally affected by it! You come out so harsh. Just because they re-hashed old exploits into a new and uberly stupid improved &quot;0-day&quot; attack, doesn&#039;t mean they&#039;re not geniuses. Right now I&#039;m working on rehashing an oldie but goodie. TCP spoofing! Stay tooned</description>
		<content:encoded><![CDATA[<p>I don&#8217;t get what your beef is. They&#8217;ve reconstructed a pointless attack that will cripple teh Interwebs! I mean everyone is efermally affected by it! You come out so harsh. Just because they re-hashed old exploits into a new and uberly stupid improved &#8220;0-day&#8221; attack, doesn&#8217;t mean they&#8217;re not geniuses. Right now I&#8217;m working on rehashing an oldie but goodie. TCP spoofing! Stay tooned</p>
]]></content:encoded>
	</item>
</channel>
</rss>
