Add canonical signed operation envelopes
This commit is contained in:
parent
bfc5df698c
commit
373ff53d5c
12 changed files with 255 additions and 11 deletions
|
|
@ -108,6 +108,11 @@ identity.
|
|||
The authorization plane is `geth-auth`: resource-local signed operation logs,
|
||||
grants, revocations, groups, and `auth explain`.
|
||||
|
||||
Both keychain and auth operations use `geth-codec` canonical envelopes for
|
||||
signature payloads. The envelope includes a version, an explicit signature
|
||||
namespace, and the operation payload encoded with postcard. JSON remains useful
|
||||
for CLI/control output, but it is not the signed representation.
|
||||
|
||||
The payload access plane is `geth-secrets`: resource master secrets, epochs,
|
||||
key envelopes, bearer secrets, and rotation. Revocation for private data is
|
||||
modeled initially as secret epoch rotation.
|
||||
|
|
|
|||
|
|
@ -132,7 +132,7 @@ geth-to-geth connections without granting trust from discovery alone.
|
|||
Goal: replace stubs with signed, reducible keychain/auth operation logs and
|
||||
resource-scoped capability decisions.
|
||||
|
||||
- `[ ]` Canonical signed operation envelope.
|
||||
- `[x]` Canonical signed operation envelope.
|
||||
Acceptance criteria:
|
||||
- Keychain and auth ops use deterministic canonical encoding for signatures.
|
||||
- JSON is not used as the signed representation.
|
||||
|
|
|
|||
Loading…
Reference in a new issue