News for hackers. Stuff that matters.

A comment on SHA-1 'fully and practically broken' by new collision (2020). Parent comment

Re:SHA-1 'fully and practically broken' by new collision (2020) by throw_away on Tuesday October 12, 2021 @04:12PM (#28844495)
Looks like there's a migration plan for git to SHA-256:

https://git-scm.com/docs/hash-function-transition/

[ Parent | on HN ]
Re:SHA-1 'fully and practically broken' by new collision (2020) by lokedhs on Wednesday October 13, 2021 @01:40AM (#28848593)
Last updated in 2017. What is the current status of this?
[ Parent | on HN ]
Re:SHA-1 'fully and practically broken' by new collision (2020) by Greek0 on Wednesday October 13, 2021 @02:10AM (#28848741)
As of January 2021, SHA256 repositories are supported, but experimental. They can be created with `git init --object-format sha256`. If I understand correctly, they don't mix at all with SHA1 repositories (i.e. you can't pull/push from/to between SHA1 and SHA256 repos).

See https://stackoverflow.com/questions/65870508/git-and-sha-256

[ Parent | on HN ]
Re:SHA-1 'fully and practically broken' by new collision (2020) by beermonster on Wednesday October 13, 2021 @02:03AM (#28848700)
Here is discussion [1] on the issue on the Git mailing list at the time with some useful context WRT git. Unsure what current status is. Git 2.29 Had experimental support for sha256.. not sure what it’s current status is, but that was a year ago.

[1] https://marc.info/?t=148786884600001&r=1&w=2

[ Parent | on HN ]