feat: replace private cas envelope
This commit is contained in:
parent
2dce1f41cf
commit
63ea36bb51
10 changed files with 193 additions and 89 deletions
|
|
@ -478,6 +478,10 @@ The project is structured for future multi-user local-first authorization:
|
|||
## Keyhive/BeeKEM Roadmap
|
||||
|
||||
Resource secret epochs are the v0/v1 approximation for private payload access.
|
||||
Private CAS writes use an AES-256-GCM envelope keyed from the resource, local
|
||||
secret id, and epoch with resource-bound associated data and random nonces.
|
||||
Prototype BLAKE3-XOR private blob envelopes from earlier pre-deployment builds
|
||||
are rejected and should be recreated from plaintext.
|
||||
Later designs can add Keyhive-like convergent capabilities and BeeKEM/CGKA-style
|
||||
group key evolution. The bootstrap does not implement BeeKEM and does not claim
|
||||
strong forward secrecy or post-compromise security.
|
||||
|
|
|
|||
Loading…
Reference in a new issue