Datentresor: encrypted-vault folder (fallback to whole-backend encryption) #32

Open
opened 2026-07-25 17:44:10 +00:00 by Cordy · 0 comments
Owner

Manuel's escape hatch if transparent whole-backend encryption proves too heavy or too entangled with the OIDC/WebDAV pillar: ship without whole-backend encryption and instead offer an encrypted vault — a designated folder/area that is encrypted, rather than the entire tree.

  • Lower scope; the transparent-decryption tension only applies inside the vault.
  • Could satisfy the "don't-trust-Hetzner" threat model for the data that matters, without re-plumbing every read path.

Spike / product decision. Alternative framing of the whole encryption feature.

Manuel's escape hatch if transparent whole-backend encryption proves too heavy or too entangled with the OIDC/WebDAV pillar: ship **without** whole-backend encryption and instead offer an **encrypted vault** — a designated folder/area that is encrypted, rather than the entire tree. - Lower scope; the transparent-decryption tension only applies inside the vault. - Could satisfy the "don't-trust-Hetzner" threat model for the data that matters, without re-plumbing every read path. Spike / product decision. Alternative framing of the whole encryption feature.
Sign in to join this conversation.
No labels
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#32
No description provided.