Pierre-Yves Lapersonne@programming.dev to Programming@programming.dev · 1 month agoGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comexternal-linkmessage-square25linkfedilinkarrow-up198arrow-down18 cross-posted to: programming@programming.dev
arrow-up190arrow-down1external-linkGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comPierre-Yves Lapersonne@programming.dev to Programming@programming.dev · 1 month agomessage-square25linkfedilink cross-posted to: programming@programming.dev
minus-squarequantumvoid0@programming.devlinkfedilinkEnglisharrow-up8·1 month agothats bad, i got couple of repos on sha-256, i wonder what happens if they drop it, which i think they wont, do i have to like re-create them?
minus-squarechickenf622@sh.itjust.workslinkfedilinkarrow-up18·1 month agoI don’t think they’ll drop sha256. The breaking change is that it’s now the default instead of sha1.
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up2·29 days agoIt’s too late for this to have any effect. It’s more “brace for the shitty unnecessary storm”. If you thought “main” was stupid…
thats bad, i got couple of repos on sha-256, i wonder what happens if they drop it, which i think they wont, do i have to like re-create them?
I don’t think they’ll drop sha256. The breaking change is that it’s now the default instead of sha1.
It’s too late for this to have any effect. It’s more “brace for the shitty unnecessary storm”.
If you thought “main” was stupid…