advanced40 minby DevFox

Securing Your History with Signed Commits

Make every commit cryptographically attributable. SSH and GPG signing, allowed_signers, signed tags, host-side enforcement, and an honest account of what signing does not prove.

Security
Git

You have spent this course taking Git apart — objects, bisect, history rewrites, merge drivers, worktrees, scale. Every one of those lessons assumed the history in front of you is the history someone actually wrote. Git does nothing by default to earn it.

By the end of this lesson every commit you push carries a cryptographic signature tied to a key only you hold, your repository rejects anything that does not, and you can say what that guarantee covers and where it stops.

Anyone can commit as anyone

A commit's author and committer fields are plain strings. Git copies them out of your config into the object without checking anything. Three commands is the whole demonstration:

bash

git config user.name "Ada Lovelace"       # free text
git config user.email "ada@example.com"   # also free text
git commit --allow-empty -m "Looks official"

That commit is now, as far as every tool is concerned, authored by Ada, and a host will render her name beside the avatar of whichever account owns that email. Nothing is broken: the fields were never a claim of identity. They are a label, like the return address on an envelope, and signing turns that label into evidence.

What a signature actually is

Recall from the object-model lesson that a commit object is a short block of text: a tree hash, parents, author and committer lines, a blank line, the message. A signature is a detached signature over exactly those bytes, folded back into the object as a gpgsig header.

bash

git commit -S -m "Add rate limiter"
git cat-file -p HEAD

text

tree 4b825dc642cb6eb9a060e54bf8d69288fbee4904
parent a1c3f9e0b7d2e6f81a4c5b9d0e3f7a2c6b8d1e40
author Maya Iqbal <maya@example.com> 1753500000 +0000
committer Maya Iqbal <maya@example.com> 1753500000 +0000
gpgsig -----BEGIN SSH SIGNATURE-----
 U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgvJ9k2Qp...
 -----END SSH SIGNATURE-----

Add rate limiter

The signature lives inside the commit, on continuation lines indented by one space. The header is therefore part of the object, so signing changes the bytes and the hash changes with them: a signed commit and its unsigned twin are different commits. Verification reverses the trick — pull the header out, rebuild the commit text without it, check the signature against that. One changed byte and it fails.

Signing with the SSH key you already have

Since Git 2.34 you can sign with an SSH key instead of a GPG key. For most developers that is the right default: the key is already on your machine, already on your hosting account, and already unlocked by your agent.

Note the .pub — with SSH signing, user.signingkey points at the public half; Git finds the private key through your agent or the matching file. The gpgsign settings mean you never type -S again. That is the easy half, and where most write-ups stop: on its own it makes signatures nobody can check yet.

Teaching Git whom to trust

A signature is only meaningful against a list of keys you have decided to believe. For SSH signing that is an allowed signers file, and without one, local verification cannot succeed no matter how correctly you signed.

Each line is a principal, optional options, then the key. Keys are truncated here; real lines are unwrapped:

The principal is matched against the committer's email, and namespaces="git" scopes the key to Git signing, so a key you also use elsewhere cannot be replayed into your history. Now verification works:

For machines, --show-signature is unwieldy. The %G? placeholder gives one status letter per commit:

For a hard pass or fail, prefer exit codes: git verify-commit and git verify-tag return non-zero on failure.

GPG signing when your team requires it

Some organisations standardise on GPG, often because the same key backs package or email signing. The flow is longer, not harder.

Use ed25519 instead if your tooling accepts it. The ID follows the algorithm on the sec line, after the slash:

Give keys an expiry — a year or two is common. An expired key stops being usable without invalidating what it already signed. Generate a revocation certificate the day you create the key (gpg --output revoke.asc --gen-revoke <id>) and publish it if the key is compromised: that is how you say "stop trusting anything new from this key".

Signed tags, the highest-value habit

If you adopt one practice from this lesson, adopt this one. A signed tag is a tag object carrying its own signature over the commit it points at, its name, and its message:

A release is where a repository turns into an artefact someone downloads and runs, and a signed tag is one small statement about it: this exact tree is what we shipped as 1.0.0, and a named human said so. Consumers check one object instead of a thousand commits, and a build system can gate on git tag -v before publishing.

Enforcement, or none of this counts

Signing is a claim; verification is the check. A repository that accepts unsigned commits gains nothing from everyone signing.

Three layers, in increasing order of strength. Your host verifies signatures against keys registered to an account and shows a Verified badge, which says only that the host was satisfied. Branch protection rules can require signed commits on main and refuse anything else; start here, because it is one checkbox and it is server-side. Strongest is a pre-receive hook on a self-hosted server, or a CI job on every pull request, walking the incoming range:

This is where the intermediate hooks lesson's distinction bites. A local pre-commit hook lives in a directory contributors control and is skipped with --no-verify — a convenience, not a control. Enforcement happens on a machine the contributor does not own.

What a signature does not prove

Be precise about the guarantee.

What it proves

The holder of a key created these exact bytes.

Change one character of the message, the tree or a parent hash and the signature fails.

What it does not

Anything at all about the code.

Not that it is correct, not that it was reviewed, not that the author's laptop was uncompromised that morning.

Malware with an unlocked signing key produces perfectly valid signatures.

Signing is attribution, not quality control

There is also a mechanical wrinkle. Any operation that re-creates a commit produces a new object, and the old signature does not survive it: rebase, amend, cherry-pick, squash-merge. When a host squashes or rebases for you, it builds new commits and either signs them with its own web-flow key or leaves them unsigned. Merge commits the host creates are signed by the host, not you.

So in a repository requiring signed commits, "every commit is signed" and "every commit is signed by a human contributor" are different policies. Teams resolve it three ways: allow the host's key in the trust list, use merge commits so contributor commits arrive intact, or verify only the pull request branch rather than everything on main. Pick one and write it down.

The protections that travel with signing

Signing is one control in a set, and the rest are cheaper. Protected branches with required reviews mean no single key, compromised or not, lands code alone. Prefer git push --force-with-lease over --force: the lease checks the remote is where you last saw it, so you overwrite your own work rather than a colleague's.

Turn on your host's secret scanning and push protection so a leaked token is caught at push time, not at incident time. Pin dependencies — CI actions especially — by full commit hash rather than tag, because a tag is a movable pointer, as the tags lesson showed; a hash is the content.

Finally, git fsck --full checks that every object hashes to its own name and that the graph has no broken links. Setting transfer.fsckObjects, receive.fsckObjects and fetch.fsckObjects to true applies those checks to data in motion, rejecting malformed objects on push and fetch.

A cheat sheet to keep

Where to go next

You can now attribute every commit you create to a key you hold, verify anyone else's, and enforce that where it actually binds. You can also explain what a Verified badge does and does not mean, which is rarer than it should be.

The next lesson, Git in CI/CD pipelines, makes this routine: shallow and partial clones in pipelines, signature and tag verification as a build gate, release automation driven by signed tags, and workflows that hold up at team size.

Before you move on, do the small thing. Turn on SSH signing, write an allowed_signers file with your own key in it, and run git log --show-signature until a G beside your commits looks ordinary. Then tag a release with git tag -s and verify it. The habit is worth more than the theory.