RSS Bot@lemmy.bestiver.seMB to Hacker News@lemmy.bestiver.seEnglish · 3 months agoWe broke 92% of SHA-256 – you should start to migrate from itstateofutopia.comexternal-linkmessage-square3fedilinkarrow-up19arrow-down11file-text
arrow-up18arrow-down1external-linkWe broke 92% of SHA-256 – you should start to migrate from itstateofutopia.comRSS Bot@lemmy.bestiver.seMB to Hacker News@lemmy.bestiver.seEnglish · 3 months agomessage-square3fedilinkfile-text
minus-squareParagone@lemmy.worldlinkfedilinkEnglisharrow-up1arrow-down1·3 months agoFinding collisions to hashes is inevitable: that is why md5 and sha1 are no longer used. That it now is time for sha256 to fall… it’ll fall to that specific standard sooner-or-later… That is why I believe that the only sane thing to do is to use 2+ hashes, together, & check all of them: It may be a collision same-hash-for-different-file for ONE of them, but to do that, simultaneously, for TWO+ of them?? That’s a whole different deal of difficulty to find a collision for. MASSIVELY more improbable. _ /\ _
Finding collisions to hashes is inevitable:
that is why md5 and sha1 are no longer used.
That it now is time for sha256 to fall… it’ll fall to that specific standard sooner-or-later…
That is why I believe that the only sane thing to do is to use 2+ hashes, together, & check all of them:
It may be a collision same-hash-for-different-file for ONE of them, but to do that, simultaneously, for TWO+ of them??
That’s a whole different deal of difficulty to find a collision for.
MASSIVELY more improbable.
_ /\ _