Re:SHA-1 'fully and practically broken' by new collision (2020)
by bawolff on Tuesday October 12, 2021 @06:04PM
(#28845612)
> That is, two insecure hashes may be secure together for git's purposes.
Generally that's not true for Merkle–Damgård (e.g. sha1, sha2) hashes - afaik the difficulty of finding a collision in the more difficult hash is the same (up to big-oh) as finding it in both hashes.
Re:SHA-1 'fully and practically broken' by new collision (2020)
by zzo38computer on Tuesday October 12, 2021 @11:09PM
(#28847824)
In git I don't know, but in fossil, it already does that if the file that the collision is generated for is not the manifest file. The manifest file and all other files are identified by the SHA-1 hash (in newer versions SHA3-256 is also supported), although the manifest file also has a R card which is the MD5 hash of the all of the other files. This means that if there is a collision, it will be detected and the file would be rejected.
Here is a link to Linus's post on the internet archive
https://web.archive.org/web/20170717192607/https://plus.goog...
And here are some hn posts around the same time
https://news.ycombinator.com/item?id=13733481
https://news.ycombinator.com/item?id=13719368