codeinabox@programming.dev to Git@programming.devEnglish · 2 months agoGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comexternal-linkmessage-square14fedilinkarrow-up177arrow-down17cross-posted to: technology@lemmy.world
arrow-up170arrow-down1external-linkGit 3.0's upcoming SHA-256 default will be a costly mistakeblog.gitbutler.comcodeinabox@programming.dev to Git@programming.devEnglish · 2 months agomessage-square14fedilinkcross-posted to: technology@lemmy.world
minus-squareexdor@programming.devlinkfedilinkarrow-up1·2 months agoWhere? The attack is vague and unlikely, but blak3 might be faster. Of course less support than sha256
minus-squareColloidal@programming.devlinkfedilinkarrow-up1·2 months 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.
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.