Repository navigation
M5.7: external restore receipt chain anchors - #33
Merged
Merged
Conversation
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.
Adds deterministic external anchors for the M5.6 restore receipt hash chain.
GET /api/recording-archive/receipts/anchordownloads a versioned JSON anchor containing onlyreceipt_countandhead_hash.POST /api/recording-archive/receipts/anchor/verifystrictly validates an uploaded anchor and verifies it against the exact historical chain prefix, so a trusted old anchor remains valid after legitimate later receipts are appended. The verifier first requires the complete local receipt chain to be valid, rejects unsupported versions, malformed hashes, future counts, unknown JSON fields and trailing JSON, and returnsmatchorextendedfor valid anchors. Includes exact/extended/mismatch/API tests, README and M5.7 docs. No external provider, signing service, API key or automatic network publishing is introduced; the security benefit depends on retaining an independent copy outside the appliance trust boundary.