web: the roster is the only source of witness keys#1
Open
bordumb wants to merge 1 commit into
Open
Conversation
Both surfaces verified statements against issuer keys carried in the same untrusted payload — any server or node could mint a key and verify itself. Now the admissions key is pinned in the app bundle at build time; the roster document re-checks under that pinned key AND its bytes must hash to the rid its attestation signed; entry keys reach the pages only from a roster that passed both. The node console judges a build statement solely by the roster key for the node's claimed did (unlisted node: withheld, fail closed), ignoring any issuer_key the node serves. READMEs stop naming a CLI command that does not exist. Auths-Id: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Device: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd Auths-Anchor-Seq: 13
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
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.
Closes the trust circularity found in the witness-network review: both surfaces verified statements against issuer keys carried in the same untrusted payload, so any server or node could mint a key and verify itself.
/directory.jsonbecomes a roster document: its attestation must re-check under the pinned key AND its exact roster bytes must hash to theridthe attestation signed (content binding, checked with WebCrypto before any entry is parsed).issuer_keythe node serves is ignored.🤖 Generated with Claude Code