# md5sum collision question

I've been reading the wikipedia page, trying to get a better understanding of how to produce a collision.

http://en.wikipedia.org/wiki/MD5#Collision_vulnerabilities

The wikipedia page above states: "two colliding files is a template file with a 128-byte block of data, aligned on a 64-byte boundary that can be changed freely"

What does 64-byte boundary mean, Does that mean I can't change byte 64 but I can change the other bytes in the 128-byte block of data?

Furthermore, how do I verify that two different files generates the same md5 without using a program, just by looking at the bits? (This part is a homework question, if you guys can point me in the right direction, that would be great).

-
As for the second question, I don't think that that is feasible in the general sense. Maybe you could check if they are block aligned and end with a similar block, but in general you should only be able to detect identical files. It also depends what you mean with "just looking at the bits". If that means that your brain should not be involved, then you can't. –  Maarten Bodewes Sep 22 '13 at 15:09

I once made two batch files that ended with such a precalculated block, data that was simply ignored. I changed a single bit (ASCII 0 to ASCII 1) to make the batch files do two different things altogether, using an if statement on the value. Then I regenerated the block. In my sample I printed out two entirely different texts, even though the MD5 was exactly the same. Very informative, but the virus scanner of my company made sure my backup was completely destroyed, as it also contained a sample virus :) McAfee can scan all the files from a .zip, but it can only destroy a full .zip... –  Maarten Bodewes Sep 22 '13 at 15:06