Skip to content

Pin release attestations to the workflow and tag - #550

Merged
hbrodin merged 2 commits into
mainfrom
security/pin-release-attestation-signer
Oct 6, 2026
Merged

hbrodin merged 2 commits into
mainfrom
security/pin-release-attestation-signer

Conversation

@hbrodin

@hbrodin hbrodin commented Oct 6, 2026

Copy link
Copy Markdown
Collaborator

Change

Pin installer and updater attestation verification to trailofbits/coop's release.yml workflow at the selected release tag. Both the published bundle and GitHub API fallback now require the exact certificate identity, source ref, and a GitHub-hosted runner. Checksum verification and the existing fail-closed fallback behavior remain in place.

Verification

  • cargo fmt -- --check; workspace clippy with -D warnings; cargo build --workspace.
  • Workspace tests: 1,210 passed with a private temp directory and umask 077; the one file-mode test excluded from that run passed separately with the normal mask. Proxy and CLI tests passed in the same workspace runs.
  • tests/integration-install.sh: 12 passed. tests/integration-update.sh: 8 passed.
  • Removing --source-ref made the installer regression test fail.
  • The proposed gh flags successfully verified the published v0.7.0 bundle and tarball with gh 2.101.0.
  • VM integration was not run; this change does not alter guest or lifecycle behavior.

Adapted from chr33s's contribution. Commit co-authored with chr33s.

hbrodin and others added 2 commits October 6, 2026 19:47
Require the release workflow identity, selected source ref, and GitHub-hosted runner for bundle and API verification in both installer and updater.

Adapted from chr33s/coop@0241a27.

Co-authored-by: chris <chr33s@icloud.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant