News for hackers. Stuff that matters.
Re:NIST Retires SHA-1 Cryptographic Algorithm by est31 on Thursday December 15, 2022 @01:22PM (#34003503)
That's the general anti-agility argument wielded against git, but note that git's use cases require it to process historic data.

E.g. you will want to be able to read some sha-1-only repo from disk that was last touched a decade ago. That's a different thing than some protocol which requires both parties to be on-line, say wireguard, in which instance it's easier to switch both to a new version that uses a different cryptographic algorithm.

Git has such protocols as well, and maybe it can deprecate sha-1 support there eventually, but even there it has to support both sha-1 and sha-2 for a while because not everyone is using the latest and greatest version of git, and no sysadmin wants the absolute horror of flag days.

Re:NIST Retires SHA-1 Cryptographic Algorithm by miga on Thursday December 15, 2022 @02:44PM (#34004618)
It would be safer to forbid broken hashes after certain date, and consider only those earlier hashes that have been counter-signed by new algorithms.
Re:NIST Retires SHA-1 Cryptographic Algorithm by lazide on Thursday December 15, 2022 @09:03PM (#34008669)
So then you can’t load an archived repo?