1994
DOI: 10.1007/3-540-48285-7_26
|View full text |Cite
|
Sign up to set email alerts
|

Collisions for the compression function of MD5

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
54
0

Year Published

2005
2005
2015
2015

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 172 publications
(55 citation statements)
references
References 4 publications
1
54
0
Order By: Relevance
“…While our results don't endanger the collision resistance of the RIPEMD-128 hash function as a whole, we emphasize that semi-free-start collision attacks are a strong warning sign which indicates that RIPEMD-128 might not be as secure as the community expected. Considering the history of the attacks on the MD5 compression function [7,8], MD5 hash function [28], and then MD5-protected certificates [24], we believe that another function than RIPEMD-128 should be used for new security applications.…”
Section: Resultsmentioning
confidence: 99%
“…While our results don't endanger the collision resistance of the RIPEMD-128 hash function as a whole, we emphasize that semi-free-start collision attacks are a strong warning sign which indicates that RIPEMD-128 might not be as secure as the community expected. Considering the history of the attacks on the MD5 compression function [7,8], MD5 hash function [28], and then MD5-protected certificates [24], we believe that another function than RIPEMD-128 should be used for new security applications.…”
Section: Resultsmentioning
confidence: 99%
“…Not reflected in the table is the fact that already in 1993 it was known that there was serious trouble with MD5, based on collisions in its compression function (cf. [1], [3]). We leave any speculation about the future of SHA-1 cryptanalysis to the knowledgeable reader.…”
Section: Resultsmentioning
confidence: 99%
“…This distinguisher utilizes the dBB pseudo-collision path of MD5 [5], where the hash values collide with probability 2 −46 when the IV difference satisfies the dBB-condition, i.e.,…”
Section: Recent Attack On Hmac/nmac-md5 and Md5-mac [18]mentioning
confidence: 99%
“…For MD4, because it is easy to find a differential path with high probability [15,20], there are some successful cryptanalytic results on MACs based on MD4 [4,6,14]. For HMAC/NMAC-MD5, there is only one available differential path that is called dBB pseudo-collision path [5]. Because the dBB pseudo-collision consists of two different IVs and the same message, so all the attacks [4,6,11,14] are in the related-key setting.…”
Section: Introductionmentioning
confidence: 99%