Repository navigation
M5.6: tamper-evident restore receipt hash chain - #32
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 SHA-256 hash chaining to persistent restore receipts. Each receipt now carries
previous_hashandreceipt_hash; appends verify the complete existing chain and refuse to extend a broken audit log. New read-onlyGET /api/recording-archive/receipts/verifyreports validity, receipt count, chain head, and first failing receipt/index on corruption. Existing wholly unchained M5.5 receipt files are sealed once in append order during open, establishing tamper evidence from migration onward; partially hashed files are not treated as legacy. Includes chain-link, tamper-detection, append-gate, legacy-migration and verify-API tests plus README and M5.6 documentation. This is local tamper evidence, not external signing/timestamping.