Originally posted by: Jaiman Tuckuh
I've googled up bits and pieces about it - didn't find the exact page that I read before, but the same info. And that md4, then md5 were developed as upgrades to the CRC 32 method that SFV uses. CRC 32 uses a 32-bit hash, and md5 uses 128-bit. The higher bits, (and other headache-inducing details), keep it from giving a false-ok (a bigger problem with bigger files) by some ridiculously greater factor. CRC 32, then Md5 caught on in mainstream proggies. Par uses the md5 hash for its testing. (Don't ask me how par does its recovery, I think it has to do with magical pixie spells or something.
).
Great info JT.I've googled up bits and pieces about it - didn't find the exact page that I read before, but the same info. And that md4, then md5 were developed as upgrades to the CRC 32 method that SFV uses. CRC 32 uses a 32-bit hash, and md5 uses 128-bit. The higher bits, (and other headache-inducing details), keep it from giving a false-ok (a bigger problem with bigger files) by some ridiculously greater factor. CRC 32, then Md5 caught on in mainstream proggies. Par uses the md5 hash for its testing. (Don't ask me how par does its recovery, I think it has to do with magical pixie spells or something.
). Tho I say SHA1 all the way baby! with 160-bit hashes.
I've read it was developed to replace MD5.
It also happens to be what the torrent protocol uses internally.
SWESB_RTW up soon