Sign release images keyless, with SBOMs and build provenance (K-S7) #492

Merged
jcoffey-dev merged 1 commits from feat/sign-images into main 2026-11-19 22:47:31 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 8850a3f110 Sign release images keyless, with SBOMs and build provenance (K-S7)
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 14m26s
.github/workflows/sign.yml, called by ci.yml on every v* tag once the
images, their index and the release exist:

- cosign signs the server's and inbuxa Relay's multi-arch index by
  digest, keyless (this workflow's GitHub identity, recorded in Sigstore's
  public log), in the registry and on the GHCR copy, then verifies the
  signature as a user would.
- syft writes an SPDX SBOM per architecture; GitHub's attest-sbom attests
  each against that architecture's image, and they are attached to the
  Gitea release.
- attest-build-provenance attests the build against each index, only
  from the run that built it.

Run by hand from main with an existing release's tag, it signs and
attests the SBOMs of a version published before signing (or whose
signing failed), and attests no build: that run built nothing.

The attestations live in GitHub's store, keyed by digest, so nothing
depends on what the registry keeps beside an image. cosign v3.1.4 and
syft v1.55.0 are downloaded at pinned versions and checked against
pinned SHA-256 sums; the actions are pinned to commit SHAs.

ci.yml: the sign job is part of the report, so the tag's check on Gitea
fails when signing does. A GHCR failure only leaves the copy unsigned.
2026-11-19 14:42:41 -07:00