News for hackers. Stuff that matters.
Re:The Second SHA-1 Hash Collision by clement_b on Tuesday December 31, 2019 @03:00AM (#21919620)
This is great, but it's a bit like an endangered animal giving birth in a zoo.

Has anyone seen a collision happening in the wild? What's the likelihood? Vs UUID?

Re:The Second SHA-1 Hash Collision by bawolff on Tuesday December 31, 2019 @03:11AM (#21919648)
Asking the liklihood is kind of the wrong question.

The problem with sha-1 is the possibility that a malicious person could intentionally make two files with the same hash (in order to do evil). The probability of this happening if someone decides to do it and has sufficient resources to pull it off, is 1. The probability of it happening accidentally hasn't changed and is so small it might as well be 0.

Re:The Second SHA-1 Hash Collision by clement_b on Tuesday December 31, 2019 @03:55AM (#21919792)
Makes sense! Thanks for explaining
Re:The Second SHA-1 Hash Collision by C4stor on Tuesday December 31, 2019 @03:13AM (#21919655)
UUID don't "collide", they're just the same, or not.

They're not generated from any business relevant input, there is nothing to "confuse" in the first place, and the whole concept of uuid "colliding" doesn't make sense.

Re:The Second SHA-1 Hash Collision by deathanatos on Tuesday December 31, 2019 @03:29AM (#21919706)
https://en.wikipedia.org/wiki/Universally_unique_identifier

v5 UUIDs are generated from SHA-1 hashes of their input, so they can collide in exactly the same way a normal SHA-1 can collide: two different inputs yield the same output.

But even for v4 (randomly generated) UUIDs, I would say "collide" is appropriate, if you're asking about the chance of two or more randomly generated v4 UUIDs colliding is. (That is, generating the same UUID twice. Infinitesimal, but the use of "colliding" to ask is still valid.)