Bugtraq mailing list archives
Re: SHA-1 broken
From: Michael Cordover <michael.cordover () gmail com>
Date: Sat, 19 Feb 2005 14:37:57 +1100
On this topic, I might actually say that a concatenation of two hashes is very secure if the two hashes are sufficiently different. Although MD5 and SHA1 are reasonably similar, let's suppose for a moment that they use entirely different mechanisms. If this were so and the crack time for MD5 was 2**50, for SHA1 2**65, then the crack time for CONCAT(MD5(string), SHA1(string)) would be about 2**115. This is because you need to find something that colides for both. This is *far* more difficult and therefore far more collision resistant. Unfortunately this requires 288 bits - far more than each of the old hashes. Still, that much memory doesn't tend to be a problem ;). Regards, Michael Cordover -- http://mine.mjec.net/
Current thread:
- SHA-1 broken Gadi Evron (Feb 16)
- Re: SHA-1 broken Kent Borg (Feb 17)
- Re: SHA-1 broken Michael Cordover (Feb 17)
- Re: SHA-1 broken dullien (Feb 19)
- Re: SHA-1 broken D.J. Capelis (Feb 19)
- Re: SHA-1 broken Michael Cordover (Feb 20)
- Re: SHA-1 broken Dan Harkless (Feb 19)
- Re: SHA-1 broken Robert Sussland (Feb 17)
- Re: SHA-1 broken dullien (Feb 19)
- Re: SHA-1 broken Darren Reed (Feb 19)
- Re: SHA-1 broken dullien (Feb 19)
- Re: SHA-1 broken Tollef Fog Heen (Feb 19)
- Re: SHA-1 broken Denis Jedig (Feb 21)
- Re: SHA-1 broken dullien (Feb 19)
- <Possible follow-ups>
- RE: SHA-1 broken Scovetta, Michael V (Feb 17)