Separate bearer ids from private tokens

This commit is contained in:
Eric Wendland 2026-05-20 13:10:34 +02:00
commit 460acab67b
9 changed files with 198 additions and 62 deletions

View file

@ -182,9 +182,9 @@ Roadmap items should be actionable and checkable:
ops and must not allow trust graph mutation capabilities. Bearer
challenge/proof/verify commands exist for resource-scoped possession checks.
Remote module authorization paths can accept optional bearer proofs without
enrolling the caller as a trusted node. Payload encryption, key envelopes, and
separating public bearer ids from private bearer tokens are still roadmap
work.
enrolling the caller as a trusted node. Bearer creation separates the public
bearer id stored in auth logs from the private bearer token returned to the
caller once. Payload encryption and key envelopes are still roadmap work.
- SSH revocations can be exported as JSONL, OpenSSH KRL specification text, or
binary OpenSSH KRL files generated through `ssh-keygen`. JSONL and OpenSSH KRL
specification imports are supported; binary KRL import is unsupported because