Re:SHA1 collisions make Git vulnerable to attacks
by CJefferson on Monday February 27, 2017 @05:44AM
(#13743292)
My git with different hash would be useless. It wouldn't be able to interact with github, bitbucket, or pull/push to anyone else's repositories. I may as well rename the package.
Fixing this is going to require breaking backwards compatability with every program that works with git -- it's going to be a huge undertaking, because early in git's design they didn't support multiple hash functions.
Re:SHA1 collisions make Git vulnerable to attacks
by RubyPinch on Monday February 27, 2017 @06:20AM
(#13743420)
To clarify, I mean to replace the hash with something that would collide far more often, to simulate collisions, to see how git handles them
Re:SHA1 collisions make Git vulnerable to attacks
by robin__j on Monday February 27, 2017 @07:56AM
(#13743829)
https://stackoverflow.com/a/34599081
In this SO answer does it by reducing the hash size from 160-bit to 4-bit.
Re:SHA1 collisions make Git vulnerable to attacks
by CJefferson on Monday February 27, 2017 @06:41AM
(#13743508)
Ah, that is a much more sensible request! Sorry for my harsh reply.
Re:SHA1 collisions make Git vulnerable to attacks
by hvidgaard on Monday February 27, 2017 @04:45AM
(#13743053)
You can, but they should reengineer Git to use any hash function, and not assume output length.
Re:SHA1 collisions make Git vulnerable to attacks
by mattkrause on Monday February 27, 2017 @04:59AM
(#13743103)
I think the bigger problem is that tons of other stuff also assumes the output length.
http://stackoverflow.com/a/34599081 has actually gone about doing it, but it has been over a year since that, and as linus says, there has been multiple collision mitigations added as well, so tests should probably be re-done