codeinabox@programming.dev to Git@programming.devEnglish · 1 month agoGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comexternal-linkmessage-square14linkfedilinkarrow-up176arrow-down17cross-posted to: programming@programming.devprogramming@programming.dev
arrow-up169arrow-down1external-linkGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comcodeinabox@programming.dev to Git@programming.devEnglish · 1 month agomessage-square14linkfedilinkcross-posted to: programming@programming.devprogramming@programming.dev
minus-squareexdor@programming.devlinkfedilinkarrow-up1·29 days agoWhere? The attack is vague and unlikely, but blak3 might be faster. Of course less support than sha256
minus-squareColloidal@programming.devlinkfedilinkarrow-up1·29 days agoGrep blake3? Basically changing the algorithm is pointless, but you can tack on another algo, which can be sha-256, blake3, etc. It’s a good read.
Why not blake3?
Addressed in the article.
Where?
The attack is vague and unlikely, but blak3 might be faster. Of course less support than sha256
Grep blake3? Basically changing the algorithm is pointless, but you can tack on another algo, which can be sha-256, blake3, etc. It’s a good read.