<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Matasano Chargen - Latest Comments in RSA Signature Forgery Explained (with Nate Lawson) - Part II</title><link>http://matasanochargen.disqus.com/</link><description></description><language>en</language><lastBuildDate>Wed, 13 Sep 2006 19:37:50 -0000</lastBuildDate><item><title>Re: RSA Signature Forgery Explained (with Nate Lawson) - Part II</title><link>http://www.matasano.com/log/487/rsa-signature-forgery-explained-with-nate-lawson-part-ii/#comment-2320515</link><description>MD5 makes this attack very slightly easier. SHA256 would make it slightly harder (you'd have a harder time sliding a bogus hash into a 1024 bit modulus). But all the engineering you could do with hash functions are for nothing if you don't get signature verification right.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Ptacek</dc:creator><pubDate>Wed, 13 Sep 2006 19:37:50 -0000</pubDate></item><item><title>Re: RSA Signature Forgery Explained (with Nate Lawson) - Part II</title><link>http://www.matasano.com/log/487/rsa-signature-forgery-explained-with-nate-lawson-part-ii/#comment-2320514</link><description>I'd love to hear an explanation for why the people in charge of the TLS standard haven't added any ciphersuites with alternative hashes.&lt;br&gt;&lt;br&gt;They add a screwball symmetric algorithm like SEED, yet they can't be bothered to add suites that use SHA-256, SHA-512, Whirlpool, or Tiger, even when there was speculation that SHA-1 would be next to fall when MD5 attacks were announced a couple years ago?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tyme</dc:creator><pubDate>Wed, 13 Sep 2006 17:07:04 -0000</pubDate></item><item><title>Re: RSA Signature Forgery Explained (with Nate Lawson) - Part II</title><link>http://www.matasano.com/log/487/rsa-signature-forgery-explained-with-nate-lawson-part-ii/#comment-2320513</link><description>Silly question, but couldn't the entire thing have been avoided had we&lt;br&gt;&lt;br&gt;a) switched to OAEP ?&lt;br&gt;b) implemented OAEP correctly ?&lt;br&gt;c) refused to trust anyone who uses a low exponent ?&lt;br&gt;&lt;br&gt;At least, if we trust the random oracle model, we have something relatively strong in our hands (OAEP). I am consistently surprised that the migration away from other, clearly weaker message padding schemes isn't happening more quickly.&lt;br&gt;&lt;br&gt;Cheers,&lt;br&gt;Halvar</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Halvar</dc:creator><pubDate>Wed, 13 Sep 2006 16:31:04 -0000</pubDate></item></channel></rss>