Re:How easy is it in 2022 to find a SHA1 collision?
by userbinator on Sunday April 24, 2022 @08:18PM
(#31149531)
It's still not as easy as MD5, which can be done in a few seconds on a 10-year-old CPU.
[ Parent
| on HN ]
Re:How easy is it in 2022 to find a SHA1 collision?
by khnov on Sunday April 24, 2022 @09:03PM
(#31149777)
are you saying you need few seconds to crack an md5 hash using an old cpu ?
Re:How easy is it in 2022 to find a SHA1 collision?
by TheDong on Sunday April 24, 2022 @09:25PM
(#31149913)
That's not the case. They're saying you can find a collision easily (i.e. I can easily give you two files that have the same md5sum).
However, "crack an md5 hash" isn't what that means. First, you can't really "crack" a hash (there are infinitely many inputs that have the same hash), but even just going from a hash to any input with that hash is much harder.
That's a preimage attack, and a preimage attack for md5, according to wikipedia, remains theoretical https://en.wikipedia.org/wiki/MD5#Preimage_vulnerability.
I welcome anyone to give a counter example by giving me something that has an md5 hash of 08fc873f2aac5acce46ed751613472fe
Re:How easy is it in 2022 to find a SHA1 collision?
by greggsy on Sunday April 24, 2022 @10:21PM
(#31150212)
Odds are that itβs a hash of the Rick Roll url, so challenge accepted.
Re:How easy is it in 2022 to find a SHA1 collision?
by TillE on Sunday April 24, 2022 @09:46PM
(#31150032)
Yeah, this is an important point. The known published attacks on MD5 are pretty narrow, so there are many circumstances where you can rely on MD5 hashes if you have to.
Re:How easy is it in 2022 to find a SHA1 collision?
by quickthrower2 on Sunday April 24, 2022 @09:48PM
(#31150046)
Careful, you are open to a $5 wrench attack
Re:How easy is it in 2022 to find a SHA1 collision?
by maccard on Monday April 25, 2022 @03:46AM
(#31151603)
That's also true if you use a more secure hash.
Re:How easy is it in 2022 to find a SHA1 collision?
by quickthrower2 on Monday April 25, 2022 @09:15PM
(#31162896)
Was said a bit in jest, but in seriousness - only if you publish the hash and dox yourself, or the attacker gets your hash from a DB, some identifier, and finds you. That was the joke - in this case the comment does this. (I have no idea if or how much doxxed I didn't check)
Re:How easy is it in 2022 to find a SHA1 collision?
by TheDong on Tuesday April 26, 2022 @07:14PM
(#31174326)
Given I generated the hash with something like "head -c 1000 /dev/urandom | md5sum", I also don't really think a wrench attack would work here, even if you could find me. I don't know any input that produces that md5sum, no matter how many times you hit me with a wrench.
Re:How easy is it in 2022 to find a SHA1 collision?
by userbinator on Sunday April 24, 2022 @10:02PM
(#31150111)
You can generate collisions in seconds.
https://github.com/brimstone/fastcoll
There's plenty of others, that one was just a random one I picked.
Re:How easy is it in 2022 to find a SHA1 collision?
by MiguelX413 on Sunday April 24, 2022 @09:23PM
(#31149899)
I'm pretty sure that's what they said.