{"thread":{"id":"51100","subject":"Git and the new SHA-1 prefix collision attack","startedAt":"2019-05-15T12:22:35Z","lastAt":"2019-05-15T12:22:35Z","messageCount":1,"participants":["Ævar Arnfjörð Bjarmason"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"375626","messageId":"875zqbx5yz.fsf@evledraar.gmail.com","threadId":"51100","inReplyTo":null,"subject":"Git and the new SHA-1 prefix collision attack","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2019-05-15T12:22:28Z","receivedAt":"2019-05-15T12:22:35Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"[CC-list carried forward from the last SHA-1 thread I found]\n\nThought I'd sent a brief line about this since nobody else did.\n\nThere's a newly published \"From Collisions to Chosen-Prefix Collisions\nApplication to Full SHA-1\" paper making the news this week which builds\non the SHAttered attack: https://eprint.iacr.org/2019/459.pdf\n\nSee https://shattered.io for that original attack.\n\nI asked Marc Stevens on Twitter whether the sha1collisiondetection\nlibrary would cover the sorts of collisions generated by the method\ndescribed in this paper. He said yes:\nhttps://twitter.com/realhashbreaker/status/1128419029536923649\n\nNot all the details are out on this new attack, in particular the\nresearchers (CC'd) haven't yet published details[1] on improvements that\nwould make such an attack cheaper to carry out than the current\nstate-of-the art, which I understand from Marc's Twitter feed is\nsomething he's skeptical about.\n\nIn any case, it looks like the sha1collisiondetection library will save\nthe day again. Thanks Marc & Dan!\n\n1. https://www.zdnet.com/article/sha-1-collision-attacks-are-now-actually-practical-and-a-looming-danger/\n"}]}