This is the reason you should never sign a document provided by someone else. Notice the blob of random data at the top of the ps files? These were tweaked to make the md5sums “meet in the middle”. The computational effort to “meet in the middle” are only the square root “one meeting the other”. In other words, if the creators hadn’t been allowed to create both documents, the effort would have been unfeasible (well, say, 10^80 ops instead of 10^40 ops).
Take home message: always randomize (adding spaces here and there, etc.) any document you sign that you didn’t write yourself.
And, no, no MD5 has yet been replaced in our fine company. I bet you, in ten years, we will
Ah, cute!!!
This is the reason you should never sign a document provided by someone else. Notice the blob of random data at the top of the ps files? These were tweaked to make the md5sums “meet in the middle”. The computational effort to “meet in the middle” are only the square root “one meeting the other”. In other words, if the creators hadn’t been allowed to create both documents, the effort would have been unfeasible (well, say, 10^80 ops instead of 10^40 ops).
Take home message: always randomize (adding spaces here and there, etc.) any document you sign that you didn’t write yourself.
And, no, no MD5 has yet been replaced in our fine company. I bet you, in ten years, we will
Yeah, what JJV said. Don’t sign stuff prepared by someone else.
And the article you linked to suggests that people are hard at work on similar exploits for SHA-1.