Git 3.0 will make SHA-256 the new default content hashing algorithm and it will be an incomprehensibly expensive and ultimately valueless and avoidable global nightmare.
Yes I read the article. I don’t agree with all the conclusions.
Now is the best time to change to a new algo. SHA1 is not completely broken yet. It most probably will be at some point.
Also AFAIK they will have compatibility tools for SHA1 repos in git. I don’t see the big deal with the path they chose.
We will probably nor agree on that one. I think the hashes are important and that they are mutable right new with effort and later without. It’s okay that we don’t agree though. The git maintainers have made their decision anyways.
Yes I read the article. I don’t agree with all the conclusions.
Now is the best time to change to a new algo. SHA1 is not completely broken yet. It most probably will be at some point.
Also AFAIK they will have compatibility tools for SHA1 repos in git. I don’t see the big deal with the path they chose.
We will probably nor agree on that one. I think the hashes are important and that they are mutable right new with effort and later without. It’s okay that we don’t agree though. The git maintainers have made their decision anyways.