v0.6.392: a declared storage restore can pause federated shares (#1072) #1082

Merged
Cordy merged 26 commits from rp1072 into main 2026-11-03 20:11:59 +00:00
Owner

Closes #1072.

  • Declaration box: "Pause federated shares until their owners turn them on" in the restore dialog and on the CLI (cairnd restored --pause-federated). It is unticked by default until the shareinfo live check passes; the security-incident box ticks it and wins over a folder scope.
  • Pause: computed from the declaration (PauseBefore). A paused share answers 503 with Retry-After: 3600 and X-Cairn-Code: share-paused-restore on /dav/ocm/ and on shareinfo. Unknown shares still get 404 and wrong secrets 401. An INFO line is logged at most once a minute.
  • Owner:
    • The Paused: storage restored chip, a note, a filter chip and a bell item.
    • Turn on asks first and clears the hand-over and restore pauses together.
    • A share ended after the backup is never revived (409 share-ended-after-backup). Turn on decides on the record it reads inside the write, and answers 409 restore-not-ready before a CLI declaration's lists are computed.
  • Admin checklist:
    • A Federated shares row with counts, Resume all (which also lifts earlier declarations' pauses) and End again (via POST /api/v1/admin/shares/o:{pid}/revoke).
    • Lists of shares made after the backup that are gone (capped at 200), and of OCM servers and peers removed after the backup that the restore allows again.
    • An "audit log incomplete" fallback for access-logging gaps (from settings-change and audit-tiers), pre-v0.6.390 removals, owner-revoke and posix.
  • Docs: CHANGELOG v0.6.392, chart appVersion, federation-ocm, admin-policy, deployment, sharing, account, peering and protect-backups handbook pages, ARCHITECTURE.md.

Reviewed per wave (W1-W3) plus a final review with adversarial probes (stale instance, replayed writes, overlapping declarations); all findings fixed or in the backlog.

Closes #1072. - **Declaration box:** "Pause federated shares until their owners turn them on" in the restore dialog and on the CLI (`cairnd restored --pause-federated`). It is unticked by default until the shareinfo live check passes; the security-incident box ticks it and wins over a folder scope. - **Pause:** computed from the declaration (`PauseBefore`). A paused share answers 503 with `Retry-After: 3600` and `X-Cairn-Code: share-paused-restore` on `/dav/ocm/` and on shareinfo. Unknown shares still get 404 and wrong secrets 401. An INFO line is logged at most once a minute. - **Owner:** - The Paused: storage restored chip, a note, a filter chip and a bell item. - Turn on asks first and clears the hand-over and restore pauses together. - A share ended after the backup is never revived (409 `share-ended-after-backup`). Turn on decides on the record it reads inside the write, and answers 409 `restore-not-ready` before a CLI declaration's lists are computed. - **Admin checklist:** - A Federated shares row with counts, Resume all (which also lifts earlier declarations' pauses) and End again (via `POST /api/v1/admin/shares/o:{pid}/revoke`). - Lists of shares made after the backup that are gone (capped at 200), and of OCM servers and peers removed after the backup that the restore allows again. - An "audit log incomplete" fallback for access-logging gaps (from `settings-change` and `audit-tiers`), pre-v0.6.390 removals, owner-revoke and posix. - **Docs:** CHANGELOG v0.6.392, chart appVersion, federation-ocm, admin-policy, deployment, sharing, account, peering and protect-backups handbook pages, ARCHITECTURE.md. Reviewed per wave (W1-W3) plus a final review with adversarial probes (stale instance, replayed writes, overlapping declarations); all findings fixed or in the backlog.
Merge main (v0.6.391) into rp1072
All checks were successful
ci / test-and-build (pull_request) Successful in 1h16m27s
aeadcb3f3b
Cordy merged commit 6f12503d7a into main 2026-11-03 20:11:59 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1082
No description provided.