|
BugTraq
MD5 To Be Considered Harmful Someday Dec 06 2004 11:29PM Dan Kaminsky (dan doxpara com) (3 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 01:46AM Joel Maslak (jmaslak antelope net) (2 replies) MD5 To Be Considered Harmful Today Dec 08 2004 01:39AM Pavel Machek (pavel ucw cz) (1 replies) Re: MD5 To Be Considered Harmful Today Dec 08 2004 10:23PM Dan Kaminsky (dan doxpara com) (1 replies) Re: MD5 To Be Considered Harmful Someday Dec 07 2004 10:54PM Gandalf The White (gandalf digital net) (4 replies) RE: MD5 To Be Considered Harmful Someday Dec 08 2004 04:01AM David Schwartz (davids webmaster com) (2 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 09:30PM George Georgalis (george galis org) (1 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 04:36AM Gandalf The White (gandalf digital net) (3 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 09:44PM Keith Oxenrider (koxenrider sol-biotech com) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 09:17PM Solar Designer (solar openwall com) (1 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 08:48PM Paul Wouters (paul xtdnet nl) (2 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 08:52PM Dan Kaminsky (dan doxpara com) (1 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 01:51AM Joel Maslak (jmaslak antelope net) (1 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 12:13AM Tim (tim-security sentinelchicken org) (2 replies) Re: MD5 To Be Considered Harmful Someday Dec 08 2004 06:52PM David F. Skoll (dfs roaringpenguin com) |
|
Privacy Statement |
>The algorithm is far more complicated than "raw" MD5. It consists of
>1000 iterations of MD5 with both output from the previous iteration
>and the original input (plaintext password and salt) being rolled into
>the hash on each iteration.
>
>
Brute force work efforts like password cracking tend to be an
exponential times a constant -- say, 2^32 operations that take 100ms
each. Increasing the complexity of a legitimate password verification
increases the constant. Interestingly, the more efficient a legitimate
verifier becomes, the more efficient your brute forcer is.
Not that brute force is the only approach available. There are numerous
attacks that might break "pure" MD5 but fail given such massive
overlapping. There are, however, others that abuse extra rounds to
great effect. For instance, SHA-0 is an 80 round algorithm. Biham's
paper (http://eprint.iacr.org/2004/146/) showed that an 82 round variant
is actually much weaker. And Joux's unreleased paper makes it very
clear that simply stacking primitives doesn't create nearly the level of
combinatorial complexity that you'd expect.
Of course, as I've said elsewhere passwords really aren't at all
vulnerable to the MD5 attack. But, if they were, extra iterations
wouldn't be helpful. Once the first round collided, all future rounds
would continue to collide.
--Dan
www.doxpara.com
[ reply ]