The blame and mistake isn’t honestly on git, but the rest of the tooling ecosystem. This wasn’t a snap decision and the fact that nobody thought to get ready in the 6 god fucking years that this has been planned is the real problem.
This will be painful, but only because apparently nobody was willing to just start supporting it 5min before the deadline.
I tried to implement my own git from scratch. And when I got to choose a hashing algorithm, I reached the exact same conclusion as the author pretty fast.
The hashing algorithm doesn’t really matter as long as it’s good enough to prevent accidental collisions. And if there is a collision, it is extremely easy to check.
If you are about to create a new object and an object with that hash already exists, you compare the 2 objects. If they are the same, nothing happened. If they are different, you just found a collision. Throw some obscure error that will only be witnessed once in the lifetime of the universe and be done with it. Tell the user to change a single bit of the input and be done with it.
The purpose of object hashes in git was never to provide security. Security is achieved through other means.
Security is achieved through other means.
Let’s explicit this: you can, and should, sign your commits if you want security (no commit tampering). You need to:
- generated a gpg key:
gpg --full-generate-key - set git to look for the public key to use:
git config --global user.signingkey [public key ID] - set git to sign your commits:
git config --global commit.gpgsign true
Note that I used
--globalhere but you can do without to sign on a per-project basis.Also
gpgUX is terrible, to find the[public key ID]use the commandgpg --list-keys, it should looks like:pub ed25519 2026-01-01 [SC] <- type algorithm date and capability (this key is only to Sign and Certify) 662E3CDD6FE329002D0CA5BB40339DD82B12EF16 <- Public key ID uid [ultimate] my full name (Master Key) <my_email@domain.com> <- owner information (should be your name and email address) sub rsa4096 2026-01-01 [E] <- sub key used to encrypt sub ed25519 2026-01-01 [S] [expires: 2027-01-01] <- subkey used to signLast, if you want to save/backup you keys the default location of
gpgfiles is~/gnupgor you can export keys withgpg --export [key ID] > path/to/file.keyfor the public part andgpg --export-secret-keys [private key ID]for the private part. Both export can have a-aor--armorargument to output as base64 text instead of raw binary.[private key ID]can be found withgpg --list-secret-keys.EDIT: after writing this I checked https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work and TIL you can sign tags too.
EDIT 2: you can also use your ssh key to sign ->
git config --global gpg.format ssh(I am less inclined to do this as you won’t have subkeys and expiration date but this would be simplier indeed)If you want to avoid the gpg mess, you can actually also configure gut to sign with your SSH key.
- generated a gpg key:
Even if it’s not the purpose it can fulfill it. Hashes are used for all kinds of things like traceability or for pinning versions. They are used in a context where people depend on that a hash always has the same code behind it and SHA1 can not guarantee that anymore. A better hashing algo is needed to keep the way how people use git secure.
It’s not enough to say “you shouldn’t use it that way”. We have to accept the reality of how git is used and adapt.
If someone has access to write to a repo you are downloading code from, and you don’t trust that someone, you shouldn’t be running the code in that repo.
The only “security” vulnerability is: I have audited and verified that the code in commit 05682ab36ca. And I will use only that version.
What you do then is: download that commit and store it in a local repo, and package it so you can distribute it to your clients.
Auditing external software is tremendous effort, even if it is open source. Using your local repo instead of downloading that commit from GitHub every time is very little extra effort in comparison.
And if you really need it. You can always hash with sha256 yourself and verify that the commit with that sha1 still produces the same sh256. So you can keep downloading it each time, just need to store the sha256.
You are exactly doing what I described. You are saying “your using it wrong” instead of acknowledging that’s how people use it and and then improving that. You might not need this feature because you are “using it correctly” but that doesn’t matter. For the lived reality of many people sha256 is the correct move.
I’ve never heard of anyone relying on git’s sha1 hashed for security
I have. In some languages you can use git repos as dependencies. It’s good practice to use hashes instead if tags because tags are not immutable. SHA1 hashes are better than tags but better hases would be even better.
Also traceability. You can build a chain from your commit over ci to the artifact if you do it right. If you can change the files to a hash you can destroy that trust chain. Sha256 makes that impossible.
People use the hashes in ways you might not. It wasn’t meant as a trust anchor but it became one. And that is now being addressed. I also think that the git maintainers have put a lot of thought into backward compatability and making the change as painless as possible.
Good practice != Something that ensures security. As I said, it’s an even better practice to just host your own fork if what you want is security. The reason to use git hashes is mostly so you don’t have to trust the author following semver in there version number. It’s a matter of ensuring that your code will always compile, not a security feature.
Have you read the article? Your arguments derive from an assumption of “sha1 is mutable, sha256 is immutable”. First of all, every hashing algorithm is going to have collisions, that’s an unavoidable “feature” of hashes. And sha1 is in no way “mutable”, it takes a great amount of effort (and money) to generate a collision. Furthermore, those collisions are not arbitrary. You have to calculate them beforehand. As the article says: what is more likely? Paying 40k€ in compute time to generate a single collision? Or just paying an open source maintainer 40k€ to let you do 1 new commit that most people are going to download anyway?
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.
There are some very good points in there, I would like to hear the counter-arguments.
Which are? I’m not joking, “GitHub broken” and “Google has issues” are not arguments against a better encryption default.
The submodule argument is transitional at best.
As for the pro side (note that this is my opinion, I’m not deeply involved in the discussion - and with not deeply I mean “not at all”):
The case the author aggressively ridiculed ("I don’t use GPG to trust, I trust the GitHub authentication!) is one that anyone would have if they’d want to stay safe from centralized systems.
Another is upstream availability: once an algorithm is identified as broken (no matter how small) usage drops rapidly - there’s a reason why no one uses md5 anymore although it “would be fine” for purely collision mitigation.
And then there the simple fact that the integrity hash is a security feature, not purely anti collision (as the author also describes). Just because they (nor I!) can’t see an attack vector at the moment doesn’t make this less of an issue.
In short: it’s the other way around: you’d need way stronger arguments than “there will be a transition pain” to knowingly compromise your security.
I still like md5 for collision detection, but every damn security scanner flags it. So then you have to add the exception, then explain to auditors about the exception. It’s not worth the hassle for the increased performance.
Can it be classified as a security feature if there is no identified security benefit?
Apparently, the whole argumentation is kind of daft and making wrong assumptions: https://programming.dev/post/57383912/26317185
thats bad, i got couple of repos on sha-256, i wonder what happens if they drop it, which i think they wont, do i have to like re-create them?
I don’t think they’ll drop sha256. The breaking change is that it’s now the default instead of sha1.
