Block, SkipCaptcha, Upload, Automoderated users, Check users, delete, edit, Moderators, move, oversight, protect, rollback
19,320
edits
Changes
Jump to navigation
Jump to search
mLine 5:
Line 5: − +
→Collisions: typo
==Collisions ==
==Collisions ==
A hash is intended to be completely unique to a given set of bytes. However, this is not always the case. Given enough processing effort, an identical hash can be produced using alternative input data. This is known as a hash collision, when two pieces of data produce the same hash. It is a security risk for such collisions to be feasibly created, since original data can be replaced with alternate data, and the hash still indicates that nothing was changed. For this reason, large key sizes are preferred for hashing, since they make it much more difficult to produce a collision. Typically, any collision which is found would only replace valid data with gibberish. However, this is not guaranteed; given enough computing effort, it is possible to replace data is a meaningful way while still matching the hash.<br />
A hash is intended to be completely unique to a given set of bytes. However, this is not always the case. Given enough processing effort, an identical hash can be produced using alternative input data. This is known as a hash collision, when two pieces of data produce the same hash. It is a security risk for such collisions to be feasibly created, since original data can be replaced with alternate data, and the hash still indicates that nothing was changed. For this reason, large key sizes are preferred for hashing, since they make it much more difficult to produce a collision. Typically, any collision which is found would only replace valid data with gibberish. However, this is not guaranteed; given enough computing effort, it is possible to replace data in a meaningful way while still matching the hash.<br />
Algorithms such as MD5<ref>https://blog.avira.com/md5-the-broken-algorithm/</ref><ref>http://cryptocrats.com/crypto/md5-the-hash-algorithm-is-now-broken/</ref> and SHA-1<ref>https://www.thesslstore.com/blog/sha-1-collision-created/</ref> have been "broken" by producing collisions.
Algorithms such as MD5<ref>https://blog.avira.com/md5-the-broken-algorithm/</ref><ref>http://cryptocrats.com/crypto/md5-the-hash-algorithm-is-now-broken/</ref> and SHA-1<ref>https://www.thesslstore.com/blog/sha-1-collision-created/</ref> have been "broken" by producing collisions.