Repository navigation
fix: verify every private key and its purpose-scoped public anchors - #4
Merged
Merged
Conversation
5 tasks
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.
Deep Check stopped at the first non-empty private key and accepted any matching public anchor in the section. A valid update key could therefore hide a corrupt or mismatched license key, or a mismatched second representation of the same public key.
Evaluate each private entry, scope public anchors to its purpose and require every declared anchor to agree. Preserve the existing RPC row shape/status vocabulary, label multiple fingerprints and return safe per-entry summaries without exposing values. Also connect the product delivery handoff and feedback entry points.
Validation: reproduced four failing regressions before the fix; all 69 engine tests pass after it; backend compilation passes. Generated temporary keys only; no user vault was opened. Native hosts and release evidence remain subject to CI. Refs #1 and #3; purpose-hint UI in #2 remains separate.