*scottstuff* : SHA-1 Broken /blog/2005/02/16/sha-1-broken?format=rss en-us 40 Comment on SHA-1 Broken by mirabile <p>Suggest moving to RIPEMD-160?</p> <p>From what I&#8217;ve heard, SHA-2 (SHA-384/512) is not more secure than SHA-1 except for the greater length, but RIPEMD-160 (in contrast to RIPEMD) still looks great.</p> <p>Any cryptographers know about it? (I&#8217;d like to hear from you, even per eMail.)</p> <p>Btw, RIPEMD-160 is better than SHA-1 anyway, because it&#8217;s from Europe ;-)</p> <p>PS: This is the first time I consider commenting a blog&#8230;</p> Wed, 16 Feb 2005 04:03:46 -0800 urn:uuid:58587d662f86af0b5e7b7efc8fadce15 http://scottstuff.net/blog/2005/02/16/sha-1-broken#comment-1164 Comment on SHA-1 Broken by core <p>Far out&#8230; I eagerly await more detail&#8230;</p> <p>peace, core</p> Wed, 16 Feb 2005 04:10:28 -0800 urn:uuid:4cc89c42395151192e39cd1000bb8b60 http://scottstuff.net/blog/2005/02/16/sha-1-broken#comment-337 Comment on SHA-1 Broken by Uri <p>We should shift attention from MD5- and SHA-based MAC design to block cipher-based MAC/MDC.</p> Wed, 16 Feb 2005 07:40:42 -0800 urn:uuid:c991c97256cfeaed6f51b64a59076fcf http://scottstuff.net/blog/2005/02/16/sha-1-broken#comment-517 Comment on SHA-1 Broken by porky <p>MD4, MD5, HAVAL-128 and RIPEMD already found broken in CRYPTO&#8217;04.</p> <p><a href="http://eprint.iacr.org/2004/199.pdf" rel="nofollow">http://eprint.iacr.org/2004/199.pdf</a></p> Wed, 16 Feb 2005 23:30:52 -0800 urn:uuid:cc5973d4a2e62843128bd31caaac9343 http://scottstuff.net/blog/2005/02/16/sha-1-broken#comment-1163 Comment on SHA-1 Broken by neel <p>the same team had broken the MD5 earlier&#8230;seems its the programmer&#8217;s generic &#8220;am god&#8221; syndrome</p> Thu, 15 Dec 2005 02:02:48 -0800 urn:uuid:63fda408a25d599756d5b9c20cad28c8 http://scottstuff.net/blog/2005/02/16/sha-1-broken#comment-755