Re:Git 3.0's upcoming SHA-256 default will be a costly mistake
by orf on Friday October 02, 2026 @06:29AM
(#49931920)
you're right, i worded that poorly. what i meant to imply was that a blob hash collision causes any tree referencing it to be malicious, which cascades down to many different commits/tags (potentially all of them, if the tree is untouched since repo creation).
[ Parent
| on HN ]
There are no comments on this comment yet.