Software Integrity Checksum and Code Signing Vulnerability
"We announce two different Win32 executable files with different functionality but identical MD5 hash values. This shows that trust in MD5 as a tool for verifying software integrity, and as a hash function used in code signing, has become questionable."
This is a pretty simple explanation of why MD5 should no longer be completely trusted. The exploit they find is interesting in that they are able to get the same key by adding padding bytes to the original and colliding executables. I can't think of any rational reason why a developer would do this on their own unless someone internally wanted to exploit the software.
Additionally there are these comments on SHA-1.
"Note that also the collision resistance of SHA-1 does not live up to its design criteria anymore, though attacking SHA-1 is still much more difficult than attacking MD5."
No comments:
Post a Comment