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.
Wayland actually increases the barrier to entry by improving the security model.
Git commit hashes were never meant for security or trust, and trying to crowbar them into that role is shortsighted, as Linus argues.
Personally, I’m in favor of the migration and would already be using it (except Nix only supports sha1 atm). But, the security argument isn’t a good one.
I’m in favor of a better hashing algorithm because the hash will be a better hash, not because I think it will improve the cryptographic security and trust of my repos. But honestly, that’s just a nerd mental thing. I could take it or leave it. SHA1 is sufficient for the role.
Wayland actually increases the barrier to entry by improving the security model.
Git commit hashes were never meant for security or trust, and trying to crowbar them into that role is shortsighted, as Linus argues.
Personally, I’m in favor of the migration and would already be using it (except Nix only supports sha1 atm). But, the security argument isn’t a good one.
I’m in favor of a better hashing algorithm because the hash will be a better hash, not because I think it will improve the cryptographic security and trust of my repos. But honestly, that’s just a nerd mental thing. I could take it or leave it. SHA1 is sufficient for the role.