(disclosure: I'm a maintainer for gitsign)
14 karma · joined September 17, 2014
(disclosure: I'm a maintainer for gitsign)
https://docs.sigstore.dev/fulcio/certificate-issuing-overvie... has a good overview of how the certificate issuing works.
With Gitsign, by default a new keypair is generated per signing event (i.e. per commit) and never hits disk. The cert in the commit signature holds the public key, which we can check against Rekor (https://docs.sigstore.dev/rekor/overview) to verify it was valid at the time of signing.
If you have the time, https://www.youtube.com/watch?v=PVhRQFS9Njg is a great deep dive into how Sigstore works in general!
The main piece that's platform specific is the Verified badges that you see in the UI + any CI checks.
Disclosure: I'm the creator of gitsign and wrote this blog post.