Skip to content

fix(backup): detect content replacement during offline verification - #249

Draft
Adam-Ghanem wants to merge 4 commits into
feat/backup-verifier-hardening-20261107from
fix/backup-verifier-content-race-20261117
Draft

Adam-Ghanem wants to merge 4 commits into
feat/backup-verifier-hardening-20261107from
fix/backup-verifier-content-race-20261117

Conversation

@Adam-Ghanem

@Adam-Ghanem Adam-Ghanem commented Nov 17, 2026 •

Copy link
Copy Markdown
Owner

Scope

Stacked on #199; do not merge before its verifier baseline is reviewed. Rehash the SQLite snapshot after read-only integrity/schema/count checks, rejecting content changes even when file size and mtime remain unchanged. Add a deterministic regression test and document the immutable-offline-snapshot requirement.

Evidence

Commits: 6d61096 (guard), 3df524c (regression), 7411449 (docs).

  • Security CI: run #44013305118 completed success (checked job steps: dependency audit, secret boundaries, security analysis, Python compile, frontend JS, Compose, production container build, privilege boundary and test suite).
  • GitHub commit-associated run lookup for 74114498a9a46f7978bc11252ad080db676f4f87 returned this Security CI run. Python CI was not returned and remains unverified; no local pytest run. A commit-associated PR run may check out a generated merge ref rather than raw branch HEAD.
  • No production restore or network activity.

Review gates / limitations

Two hashes narrow but cannot eliminate races on mutable files; operators must verify an offline immutable snapshot. No audit HMAC, authenticated staging restore, or RTO/RPO proof is claimed. Keep draft pending Python CI verification and review of #199 stack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant