Re:OpenSSL site defacement involving hypervisor hack rattles...
by 0x0 on Thursday January 02, 2014 @10:42PM
(#7004017)
Not at all unlikely. Plenty of places to put adjustment bits to correct into a hash collision, like in comments, firmware blobs, unused files. One of the md5 collision examples from earlier was two postscript files that both parsed fine but had different messages.
[ Parent
| on HN ]
Re:OpenSSL site defacement involving hypervisor hack rattles...
by a-nom-a-ly on Thursday January 02, 2014 @10:59PM
(#7004068)
You might have a point regarding binary blobs but, IMO, if they can alter text(comments, source, etc.) in such a way that it's not obvious to the human reviewer, then they deserve to succeed. I don't know what `unused files` means. Git used `sha1` last time I checked, so I'm not sure why you mention `md5`.
Re:OpenSSL site defacement involving hypervisor hack rattles...
by 0x0 on Thursday January 02, 2014 @11:27PM
(#7004169)
Unused files: there are always plenty of files in a source distribution that aren't actually being used during a compile, for example a README file. As far as I know a commit id is a sha sum of a tree of files, so you could probably put any "adjusting bits" in an unimportant file.
Md5: Just an example of how hash collisions can work in real life (not aware of any published sha1 examples)