chore: pin the Gateway trust policy to v0.1.61 - #7
Merged
Conversation
The two pinned releases were built from commits that no longer exist in the public repository, so a verifier following deploy/nitro/verify-build.sh could not check out either revision. Both also predate the fix for unreproducible enclave builds, so their measurements could not be reproduced even with the source in hand. Pin v0.1.61 instead. It is the first release whose published measurements have been independently reproduced from public source: verify-build.sh reports PASS for 893f4c9f, and the signed manifest verifies against the release workflow's Sigstore identity. Only one release is listed. The usual rollout window, where the outgoing and incoming releases are both accepted, is not available here because the outgoing release is not verifiable. Clients therefore fail closed against any Gateway other than v0.1.61, which is the correct outcome while the older measurements cannot be checked against source. Verified against production: TestLiveAttestation and TestLiveGatewayCompletion both pass against nexus-api-tee.dappnode.com running v0.1.61. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repoints
nexus-gateway-policy.jsonat Gateway v0.1.61 (893f4c9f), replacing the two previously pinned releases.Why both old entries had to go
7207defa…(v0.1.58)bda15a35…(v0.1.57)deploy/nitro/verify-build.shdoesgit cat-file -e <revision>and thengit archive <revision>, so a verifier could not check out either one. Both also predate dappnode-nexus-gateway#1, which fixed enclave builds being unreproducible — their measurements could not have been reproduced even with the source in hand.Why only one release is listed
policy.gonormally expects the outgoing and incoming releases to both be listed so clients do not fail closed during a rollout. That is not possible here: the outgoing release is not verifiable, and listing an uncheckablesource_revisionwould hand verifiers a revision that fails by construction.Clients therefore fail closed against any Gateway other than v0.1.61. That is the correct outcome while older measurements cannot be checked against source. v0.1.61 is already deployed to production, so there is no gap.
Verification
cosign verify-blobagainst the release workflow identityverify-build.shon published v0.1.61LoadPolicyvalidationgo build ./...andgo test ./...TestLiveAttestationvsnexus-api-tee.dappnode.comTestLiveGatewayCompletionvs productionLive production attestation reports
source_revision: 893f4c9f306707b83f3b41782f25eb05adbc4f30, matching this policy.🤖 Generated with Claude Code