coulomb/secrets-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Revoke leases by operator-held lease id
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
session revoke accepts exactly one of --accessor-file or --lease-id-file.
Lease ids are read from a mode-0600 out-of-repo file and fingerprinted in
evidence; the handle is never printed. Production remains fail-closed.

Assistant: grok
Assistant-Session: 01a05f07-ae72-7781-9fcb-19efd61add00
This commit is contained in:
tegwick 2026-09-02 10:08:33 +02:00
parent ce1790f267
commit 85d4548035
7 changed files with 100 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

9
SCOPE.md
View file

@ -177,11 +177,10 @@ high-risk lanes.
catalog-id confirmation; it will remain closed until the canonical
exact-action approval contract in `SECRETS-WP-0007-T04` is enforced.
These operations do not manage external workload delivery. `session revoke
--accessor-file` revokes an already-issued token by a non-secret accessor the
operator already holds; evidence is fingerprint-only. There is currently no
rotation command, compromised state, or persistent/reversible lane state
machine.
These operations do not manage external workload delivery. `session revoke`
revokes an already-issued token accessor or lease id the operator already
holds; evidence is fingerprint-only. There is currently no rotation command,
compromised state, or persistent/reversible lane state machine.
## CLI Surface