Repository navigation
artifact verify: fix ephemeral CI attestations with --identity-bundle - #380
Merged
Merged
Conversation
…ure and anchors trust through the bundle-evidenced commit leg Auths-Id: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Device: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Anchor-Seq: 1
Auths-Id: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Device: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Anchor-Seq: 1
Auths Commit Verification
Result: ✅ 1/1 commits verified |
Auths Commit Verification
Result: ✅ 2/2 commits verified |
bordumb
changed the title
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.
The v0.1.6 Release jobs fail at
artifact verify <tarball> --identity-bundle .auths/ci-bundle.jsonwith a bare "Verification failed". Root cause: this gate (added in #375) had never run before, and the combination it exercises was broken by construction —resolve_identity_keyforced the BUNDLE root as the chain key even for an ephemeral (did:key) CI attestation, which the maintainer's key never signed. The chain leg failed, so the commit-anchor leg (where the trust actually lives) never ran.Fix, fail-closed on every leg:
commit_trusted_via_bundlereuses the exactauths verify <sha> --identity-bundledoctrine — pinned.auths/rootsare the anchor, the bundle is KEL evidence only (RT-005), offline freshness graded as the commit command grades it. (verify HEAD --identity-bundlealready passes in the same CI job, which is why the trust chain artifact ← ephemeral key ← commit ← maintainer is provable there.)Getting v0.1.6 binaries out after this merges
This changes the shipped
authsbinary, so the tag must move to include it (crates/sdk/PyPI/verifier already shipped and are unaffected by this file — only Release + its gate need the new tree):git push origin :refs/tags/v0.1.6 git tag -fs v0.1.6 origin/main -m "v0.1.6" git push origin v0.1.6Merging #379 first is recommended — its skip-if-published guards silence the republish noise on the re-fired channels.
🤖 Generated with Claude Code