git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git and the new SHA-1 prefix collision attack

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 15, 2019, 12:22 UTC
Message-ID
<875zqbx5yz.fsf@evledraar.gmail.com>
[CC-list carried forward from the last SHA-1 thread I found]
Thought I'd sent a brief line about this since nobody else did.

There's a newly published "From Collisions to Chosen-Prefix Collisions Application to Full SHA-1" paper making the news this week which builds on the SHAttered attack: https://eprint.iacr.org/2019/459.pdf

See https://shattered.io for that original attack.

I asked Marc Stevens on Twitter whether the sha1collisiondetection library would cover the sorts of collisions generated by the method described in this paper. He said yes: https://twitter.com/realhashbreaker/status/1128419029536923649

Not all the details are out on this new attack, in particular the researchers (CC'd) haven't yet published details[1] on improvements that would make such an attack cheaper to carry out than the current state-of-the art, which I understand from Marc's Twitter feed is something he's skeptical about.

In any case, it looks like the sha1collisiondetection library will save the day again. Thanks Marc & Dan!

1. https://www.zdnet.com/article/sha-1-collision-attacks-are-now-actually-practical-and-a-looming-danger/
Message 1 of 1 in “Git and the new SHA-1 prefix collision attack”
  1. Ævar Arnfjörð BjarmasonMay 15, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.