There's chatter that git will consider truncating sha2 hashes. Is there any security analysis on that?
Since git lets you use arbitrarily-truncated hashes in the UI already, I don't think there's a big benefit to truncating.
-
-
They could also simply stop wasting so much space by not using hex encoding but allowing for more characters.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
it's not about benefit - they want truncation for UI and in general.
@hanno was asking if there're security problems with that. -
..probably not - the chance of a collision will be bigger if a hash is heavily truncated, AFAIK. should be fine for git.
End of conversation
New conversation -
-
-
Truncating SHA256 to length of SHA1 would eliminate collision. Fact that you can search substring is different
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.