asklemmy·Ask Lemmybyasudox Why do the majority of projects still use SHA1 for Git commit hashes?It seems like SHA1 has been deprecated a long time ago. So why do people still not use SHA256 for new repos?View original on lemmy.asudox.dev15Comments5
sslazer2au lemmy.world1Hide 1 replyBecause the git commit hash is not suppose to be used as a security measure, just a identification measure.38
KKairos replylemmy.todaySha1 is still secure for this use too. Both preimage properties remain unbroken.6
Bricked feddit.org1Hide 1 replyWhat do you mean by "use SHA1 for Git"? Are you referring to commit hashes? They probably don't have any security implications that would warrant a stronger hash15
Because the git commit hash is not suppose to be used as a security measure, just a identification measure.
Sha1 is still secure for this use too. Both preimage properties remain unbroken.
What do you mean by "use SHA1 for Git"? Are you referring to commit hashes? They probably don't have any security implications that would warrant a stronger hash
yes. commit hashes. fixed the title.
It's the default, and iirc git only uses SHA-1 for id stuff.