Enforce SSH workflow capabilities locally
This commit is contained in:
parent
c9803ea7f2
commit
f7e85960f7
8 changed files with 328 additions and 62 deletions
26
README.md
26
README.md
|
|
@ -112,16 +112,16 @@ The bootstrap implementation provides:
|
|||
pub <topic> <message> --node <node-id>` publishes to an authorized peer;
|
||||
`geth pubsub sub <topic> --node <node-id>` reads an authorized peer snapshot
|
||||
- SSH certificate flow metadata:
|
||||
- `geth ssh cert request --public-key <path> --principal <name>`
|
||||
- `geth ssh cert requests`
|
||||
- `geth ssh cert approve <request-id> --ca-key <path>`
|
||||
- `geth ssh cert import <request-id> --cert <path>`
|
||||
- `geth ssh cert list`
|
||||
- `geth ssh cert request --public-key <path> --principal <name> [--subject <principal>]`
|
||||
- `geth ssh cert requests [--subject <principal>]`
|
||||
- `geth ssh cert approve <request-id> --ca-key <path> [--subject <principal>]`
|
||||
- `geth ssh cert import <request-id> --cert <path> [--subject <principal>]`
|
||||
- `geth ssh cert list [--subject <principal>]`
|
||||
- `geth ssh cert sync <node-id>`
|
||||
- `geth ssh revocation add <kind> <target>`
|
||||
- `geth ssh revocation list`
|
||||
- `geth ssh revocation export --out <path> [--format jsonl|openssh-krl-spec|openssh-krl]`
|
||||
- `geth ssh revocation import <path> [--format jsonl|openssh-krl-spec]`
|
||||
- `geth ssh revocation add <kind> <target> [--subject <principal>]`
|
||||
- `geth ssh revocation list [--subject <principal>]`
|
||||
- `geth ssh revocation export --out <path> [--format jsonl|openssh-krl-spec|openssh-krl] [--subject <principal>]`
|
||||
- `geth ssh revocation import <path> [--format jsonl|openssh-krl-spec] [--subject <principal>]`
|
||||
- `geth ssh revocation sync <node-id>`
|
||||
- pipe registry/connect commands: `geth pipe listen <name>` and
|
||||
`geth pipe connect <name> [--node <node-id>]`
|
||||
|
|
@ -203,7 +203,13 @@ specific resource capabilities but do not create trusted node identity. The auth
|
|||
evaluator supports scoped KV write grants such as `kv.write_prefix:apps/foo/`
|
||||
for `kv.write_key:apps/foo/config` explain checks. `geth kv set --subject
|
||||
<principal>` enforces those local grants for test callers; the local node/agent
|
||||
still has owner access for local administration.
|
||||
still has owner access for local administration. SSH certificate and revocation
|
||||
commands also accept `--subject <principal>` on local metadata operations to
|
||||
exercise the same capability checks: certificate requests/read/approval/import
|
||||
use `ssh_cert.request`, `ssh_cert.read`, `ssh_cert.approve`, and
|
||||
`ssh_cert.import` on `resource:ssh:certs`, while revocation publish/read/import
|
||||
use `ssh_revocation.publish`, `ssh_revocation.read`, and
|
||||
`ssh_revocation.import` on `resource:ssh:revocations`.
|
||||
|
||||
## Local State
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue