‹ BackHN Continuity

Thread

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

570 points · 536 comments · chmaynard

  1. wat10000 · · focus · HN ↗
    I feel like if it takes this much ink to explain why using an insecure primitive is actually safe, you should just fix it.

    The arguments make sense, but how ironclad are they? How confident are you that some clever black hat won’t figure out a way to take advantage of it?

    This is one of the most widely used programs in the world. Let’s close the hole.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.