3 ms·
There are no known attacks against MD5 as long as the data you hash is not controllable by the attacker. You should still use a different hash algorithm though
by londons_explore 4y ago
There are no known attacks against MD5 as long as the data you hash is not controllable by the attacker.
You should still use a different hash algorithm though.
- mrb 4y agoThat's like saying "There are no known attacks against MD5 as long as you don't try to attack it"
- saagarjha 4y agoNot really. This actually provides useful properties in practice, though you should still probably not rely on that.
- londons_explore 4y agoUsecase where this property is useful: Developer writes some code and publishes it. It's big, so he puts it on an untrusted CDN, and also publishes an MD5 hash of the code (not via the CDN). User downloads the code from the CDN, and verifies the published hash matches. A malicious CDN couldn't make an evil file with a matching hash, based on known attacks against MD5, unless they could influence the Developer to get certain data into the original file.
- mrb 4y ago"malicious CDN couldn't make an evil file" Then the CDN, by definition, would control the data that the end-user (downloader) hashes. But I understand the confusion: londons_explore meant to write "there are no known (practical) preimage attacks" against MD5, which is true, since the only theoretical preimage has a complexity 2^123 or so.
- deleted 4y ago[deleted]