News for hackers. Stuff that matters.
Re:The Second SHA-1 Hash Collision by vbitz on Tuesday December 31, 2019 @03:03AM (#21919628)
This is just the first 320 bytes of the original shattered. They just cut off the rest of the PDF data.
Re:The Second SHA-1 Hash Collision by re on Tuesday December 31, 2019 @03:13AM (#21919656)
Yes. It also isn't the "second" sha-1 collision, by any means -- you could already trivially use the prefix and colliding blocks from the shattered example and append any suffix you want to generate more collisions: https://news.ycombinator.com/item?id=13723892

A true second collision wouldn't start with the same 320 bytes. A more interesting one might use fewer bits to achieve the collision.

Re:The Second SHA-1 Hash Collision by bawolff on Tuesday December 31, 2019 @03:33AM (#21919725)
Lol, i wonder if this is the first example of someone using the inverse of the length extension attack to trick people
Re:The Second SHA-1 Hash Collision by SpicyLemonZest on Tuesday December 31, 2019 @03:14AM (#21919657)
Does that... work? I guess so, but why does it work?
Re:The Second SHA-1 Hash Collision by tedunangst on Tuesday December 31, 2019 @03:21AM (#21919681)
Once the two sha1 states are synchronized, after the first 320 bytes, they will remain in sync as long as you extend them with the same data. (BTW This is why hmac exists, to prevent extension attacks.)
Re:The Second SHA-1 Hash Collision by jacquesm on Tuesday December 31, 2019 @02:57AM (#21919610)
Interesting how 'privacy log' includes 'google', 'twitter', 'facebook' and - strangely - 'paypal' 3rd party bits & pieces.

Authors home page is here: https://phor.net/

Re:The Second SHA-1 Hash Collision by latchkey on Tuesday December 31, 2019 @03:04AM (#21919630)
For those who are curious, here is a screenshot of `vbindiff shat-a.bin shat-b.bin` output in my terminal:

https://imgur.com/a/uZttSbD

Re:The Second SHA-1 Hash Collision by elgfare on Tuesday December 31, 2019 @02:52AM (#21919594)
This has frustratingly little information about how it was done.
Re:The Second SHA-1 Hash Collision by tedunangst on Tuesday December 31, 2019 @03:07AM (#21919636)
Truncate the original files to the differing blocks. Tada.
Re:The Second SHA-1 Hash Collision by ummonk on Tuesday December 31, 2019 @03:14AM (#21919659)
Oh of course. So any of us could generate "new" hash collisions by adding new identical blocks to these...
Re:The Second SHA-1 Hash Collision by djsumdog on Tuesday December 31, 2019 @02:59AM (#21919616)
Yes, there isn't much. The two files have PDF headers; so I presume they were messing around with some PDF exploit experiments? or signed PDF documents?

I wonder if we'll get more information; or if they're holding back until people take it seriously and attempt to get off SHA-1 for critical stuff?

Re:The Second SHA-1 Hash Collision by kfrzcode on Tuesday December 31, 2019 @03:00AM (#21919621)
Won't be the last. Would appreciate a longer writeup but I'm sure we'll see more.

First one, for reference: https://shattered.it/

https://www.schneier.com/blog/archives/2012/10/when_will_we_...

Re:The Second SHA-1 Hash Collision by joshspankit on Tuesday December 31, 2019 @11:34AM (#21922245)
It doesn’t get mentioned enough: this is with the exact same filesize. Most collision mitigations (such as git’s) revolve around using hash combined with filesize as a collision is inevitable, but a collision with the same filesize is much harder.
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.)

Re:The Second SHA-1 Hash Collision by hurricanetc on Tuesday December 31, 2019 @03:26AM (#21919696)
Make sure to like, tweet, and FB comment on this... privacy blog.
Re:The Second SHA-1 Hash Collision by Trias11 on Tuesday December 31, 2019 @02:58AM (#21919613)
Every hash function is guaranteed to have infinite number of collisions.
Re:The Second SHA-1 Hash Collision by sida on Tuesday December 31, 2019 @03:08AM (#21919641)
I mean, this is a really “water is wet” statement
Re:The Second SHA-1 Hash Collision by bawolff on Tuesday December 31, 2019 @03:13AM (#21919654)
Every lottery is garunteed to have a winner. Doesnt mean i wouldnt be excited if i won the jackpot
Re:The Second SHA-1 Hash Collision by nikbackm on Wednesday January 01, 2020 @09:53AM (#21928235)
Depends on the lottery, sometimes there is no one getting all the numbers correct so the prize money accumulates to the next round.
Re:The Second SHA-1 Hash Collision by fulldecent2 on Tuesday December 31, 2019 @02:39AM (#21919560)
Now 1000x smaller than the original Shattered attack from Google! And 1000000x less expensive!!! Buy now