On 19/09/11 20:11, Greg Sabino Mullane wrote:
supported by many OSs, libraries, etc. As far as collisions, there are plenty of easy solutions, such as:
- Check for a collision before allowing a new revision, and do something
if so (to handle the pre-image attack)
- When reverting, do a select count(*) where md5=? and then do something
more advanced when more than one match is found
- Use the checksum to find the revision fast, but still do a full byte
comparison.
A very simple thing that could be done is to use checksum, then size, and then full text.