NG BBS - Why cant MD5 be decoded?

NG BBS - Why cant MD5 be decoded?: "MD5 is impossible to reverse because of the way it is implemented. I suggest you look into the RFCs if you want more info.

It can't be decoded, it can be -cracked- and that's it. Also, breaking a hash is known when you find a way to get collisions a lot sooner than expected. So, that means, you would have to get the MSG Digest of 3.40282367 * 10e38 to find an MD5 collision, if you find a way to get a collision in less hashes, you've broken the hash, not decrypted, broken.

Fact: MD5 uses Hexadecimal, which is a radix 16, fact, MD5 produces a 128-bit hash digest AKA 32-bytes. This means, that you can have a 16^128 MD5 different hashes, and I believe the amount of atoms in the universe is supposedly a googol, which is WAY less, so good luck on working out the algorithm that way.

MD5 first off pads the stuff it's hashing, so you've got a 25meg file, it goes down to 64 bytes, and the rest of it (25536 bytes lost), so if you can find a way to reverse this and regenerate all that lost data, then please, do so.
MD5 also uses Modulus division on it's subject and XORs it, so finding that is also impossible, yes, it is, you can't reverse modulus.

MD5 is otherwise, just padding and a lot of bitwise operations, and for future reference, MD5 was NEVER ment for stuff like passwords, the man who developed it at MIT gave it one purpose: to use it as a checksum algorithm.

MD5 isn't the safest thing out there, I believe SHA1 is much safter."