Repository navigation
fix(backup): verify Visitaki photo integrity before restore receipt - #69
Open
idilsaglam wants to merge 1 commit into
Open
idilsaglam wants to merge 1 commit into
idilsaglam wants to merge 1 commit into
Conversation
idilsaglam
marked this pull request as ready for review
October 18, 2026 22:47
This branch has not been deployed
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.
Summary
Extend the existing Visitaki encrypted restore with an optional exact photo-migration digest and a less-than-24-hour backup requirement. Verify photo ownership, encoding/size, operation revisions and erasure trigger in the network-isolated restore. Publish success only after container and plaintext cleanup.
Verification
Seven local unit tests passed, including cleanup failure preventing a success receipt. These use mocked Docker/Restic; no live restore or production activation is claimed. Existing CI invokes this suite. Kaan will run the host check and supply sanitized operational evidence after review and installation.
Companion Visitaki stack #541 prepares readiness and evidence-bound activation. User-controlled merge; no database credential expansion.