Thread

1. ltbarcly3 · 1790875540 · focus · HN ↗

   This seems like Y2K fud.

   The alternative to making sha256 the default is to leave sha1 the default. Nobody changes to sha256. sha1 is broken in 10 years. Suddenly everyone has to switch all at once on the same day because it is a critical security issue, but github never implemented sha256 because they didn't have to. This would be a major problem.

   This is very very easy to fix if you run into it.

   1. Adopt git 3.0 if you can with sha256.

   2. If you can't use sha256, set the config to put things back to sha1. Wherever you need to do this you probably already set dozens of ENV vars or settings, just add a new one.

   Or write a 15 page analysis about how the above is so hard people will probably just find it catastrophic to even think about.

   1. bityard · 1790875960 · focus · HN ↗

      It's easy for _one person_ to fix. It's not easy for the entire git ecosystem as a whole. GitHub, large internal corporate git repos, CI/CD systems, projects with submodules, etc. The second half the article explains all of this.

Unofficial Hacker News client; not affiliated with Y Combinator.