Encryption crypto core: age content decorator (v0.3, probe PR1) #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/encryption"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First of two PRs building Manuel's per-user / keys-in-IdP encryption model (see
ENCRYPTION-COMPARISON.md). This is the crypto core only — no IdP, no wiring yet, so it's inert until PR2 mounts it.internal/storage/encrypt: an age encrypting decorator aroundstorage.Driver.Writeencrypts to the request's recipients;Opendecrypts with the request's identities; everything else passes through (content-only — names/sizes/tree not encrypted).KeyProviderinterface resolves keys per request from the user incontext— so per-user ↔ per-deployment ↔ KMS custody is a provider swap, not a decorator rewrite (the cheap-pivot insurance from the decision record).Opendecrypts to a temp file (removed on Close) to satisfyhttp.ServeContent— the honest "full-object read in encrypted mode" trade; the seekable-STREAM reader is a documented follow-up.filippo.io/age v1.3.1(pure-Go, audited — the §1.4 pedigree).Honest boundaries (in the decision record, restated): server-side transparent encryption, not client-side E2E; age is not post-quantum.