Practical (and impractical) git commit signing
summary
Argues that commit signatures can give provenance but real tooling breaks the assurances; demonstrates working code and CI checks (links and repo provided) and recommends SSH certificates over GPG or S/MIME because they allow a single CA, shortβlived certs and easy agent signing. Describes Git shelling out to external signers, GitHub marking commits via GitHub's verified flag that trusts userβadded keys or global CAs only, and favors hardware-backed keys for organizational device attestation.
AI-written summary Β· about
chapters (11)
- 0:00Introduction
- 1:02Speaker background
- 2:27Why sign Git commits
- 5:59GPG signing limitations
- 9:54X.509 certificate issues
- 13:28SSH keys for signing
- 17:27GitHub commit validation
- 21:24Enterprise key management
- 24:57SSH certificate advantages
- 26:42CI verification setup
- 27:43Q&A
related talks
34mSafe and Signed Git Commits with PGP
29mIdentity-based Source Integrity with Gitsign
37mGitsign β Keyless Git Commit Signing
06mKeynote: Signing Git Commits with Gitsign
05mIgnite β Konstantin Ryabitsev
10mSource Attestations with Gitsign
49mProtect Your Code with GitHub Security Features
25mProving Trust: Signed Supply Chains and Verifiable Deployments at the Edge
