‹ BackHN Continuity

Thread

Git 3.0's upcoming SHA-256 default will be a costly mistake

570 points · 536 comments · chmaynard

  1. kazinator · · focus · HN ↗
    I positively don't care about the collision issue.

    If you need to certify the authenticity of some code, and you've decided that a Git hash of any kind is going to be your certificate, you have a problem between keyboard and chair which is not fixable by stronger hashes in Git.

    I don't want instability and churn in tooling.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.