| hahahahahahahahahaahahahahahahahAHAshAHshAHSuHDisaHDUhasiHadushIUDAHSiuHDIUASh |
[Nov. 30th, 2007|03:52 pm] |
grey-mbp-osx:Downloads greydavid$ md5 HelloWorld-colliding.exe
MD5 (HelloWorld-colliding.exe) = 18fcc4334f44fed60718e7dacd82dddf
grey-mbp-osx:Downloads greydavid$ md5 GoodbyeWorld-colliding.exe
MD5 (GoodbyeWorld-colliding.exe) = 18fcc4334f44fed60718e7dacd82dddf
grey-mbp-osx:Downloads greydavid$ crc32 HelloWorld-colliding.exe
8beb795c
grey-mbp-osx:Downloads greydavid$ crc32 GoodbyeWorld-colliding.exe
9ede53db
I wrote about something like this a couple years ago, not that anyone read it really aside from a few friends. http://advogato.org/person/grey/diary/10.html I'm not sure if OpenBSD ever improved their ports system, but the guys over in the darwinports/macports realm did take my idea and implement it supposedly.
crc32 = secure!
well, no, but hahahaAHahashashahsdhsauhdsahusdhauidhsa it's nice when I can finally test a theory. |
|
|
| Comments: |
I don't disagree with you, even sha-1 has been considered dead for a while let alone md5; but I have to admit, for what I was interested in I just wanted some files that had a collision to test something else against, that's why I was happy.
Reference #3 in particular is of interest to me, but I'd rather have something of my own to verify in 20 seconds than read someone's claims of how easily it's done. And finally, someone provided that, I'm not sure if there was anything else novel other than use of ps3's or something (shrug).
The "md5" program in FreeBSD 7.0 is currently buggy, and returns the totally wrong hash sometimes. I haven't figure out why yet. "md5deep" and "diff" produce correct results on the same system. | |