Add binary OpenSSH KRL export
This commit is contained in:
parent
5751748458
commit
b9e7c61e67
11 changed files with 209 additions and 20 deletions
11
AGENTS.md
11
AGENTS.md
|
|
@ -147,9 +147,10 @@ Roadmap items should be actionable and checkable:
|
|||
Bearer access metadata can be created/listed/revoked as resource-scoped auth
|
||||
ops and must not allow trust graph mutation capabilities. Payload encryption,
|
||||
key envelopes, and bearer challenge-response are still roadmap work.
|
||||
- SSH revocations can be exported as JSONL or OpenSSH KRL specification text.
|
||||
Binary KRL generation/import is still roadmap work.
|
||||
- SSH revocations can be exported as JSONL, OpenSSH KRL specification text, or
|
||||
binary OpenSSH KRL files generated through `ssh-keygen`. Existing KRL import
|
||||
is still roadmap work.
|
||||
- Signed peer-card LAN discovery payloads, peer auth over Iroh, cr-sqlite,
|
||||
iroh-docs, iroh-blobs, Automerge sync, real auth enforcement,
|
||||
OpenSSH KRL generation, and Keyhive/BeeKEM-style authorization are future
|
||||
roadmap items unless implemented later.
|
||||
iroh-docs, iroh-blobs, Automerge sync, broader auth enforcement, KRL import,
|
||||
and Keyhive/BeeKEM-style authorization are future roadmap items unless
|
||||
implemented later.
|
||||
|
|
|
|||
Loading…
Reference in a new issue