Re:SHA-1 'fully and practically broken' by new collision (2020)
by seoaeu on Tuesday October 12, 2021 @10:28PM
(#28847555)
There's plenty of workflows where untrusted people have their proposed changes audited and then written to a git repo
[ Parent
| on HN ]
Re:SHA-1 'fully and practically broken' by new collision (2020)
by lamontcg on Wednesday October 13, 2021 @02:06AM
(#28848720)
How do they get through the auditing?
If I'm looking at a PR which contains a hash collision with code that does a `sudo rm -rf --no-preserve-root /` and I don't accept the malicious code, the hash collision becomes irrelevant.