Stage encrypted backups for retrieval - #110
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.
Refs aviorstudio/termcade-be#127
Risk: high — encrypted production backup handoff.
Team No Review is active. Stage only the age-encrypted archive and non-sensitive metadata in the deploy account home with mode 0400; the root-owned source directory remains non-traversable. Sealing deletes the staged copies. The preceding production attempt created and checksummed encrypted bytes but failed closed before off-host upload, restore drill, seal, or reset because every parent of the original retrieval path was root-only.