Repository navigation
v0.6.0
ASM v0.6.0
Image: ghcr.io/eltomato89/asm:0.6.0 (also 0.6, latest; linux/amd64)
New
- Standing approval per device. Let a device use secrets without asking every time, within limits you set on the devices page:
- Until a date, at most
ASM_STANDING_APPROVAL_MAX_DAYS(default 90) days ahead. - Scope: all secrets, selected vaults (including secrets added later), or a list of secrets. Optionally, secrets the device creates in its default vault are added to the list.
- Reads only by default; a per-device switch also allows changes (
update_secret) without asking. - After expiry: ask every time again, or ask once and extend by a preset number of days when you approve. Denying only rejects that request.
- Standing approvals take precedence over auto mode. They show up in the request list ("via standing approval"), on the push approve page (renewal note) and in the audit log. MCP
whoamitells the agent whether it is covered (no secret list).
- Until a date, at most
- Default vault per device. Secrets a device creates without naming a vault go to its default vault: your personal vault unless you change it on the devices page.
Security
- Setting a standing approval or a device's default vault requires a recent sign-in, as does approving a renewal in the browser (the push page already requires Face ID / a passkey).
- Revoking a device, losing access to a vault, or deleting a secret removes the corresponding coverage.
ASM_STANDING_APPROVAL_MAX_DAYS=0turns the feature off and removes existing standing approvals.
Upgrade notes
- New optional environment variable:
ASM_STANDING_APPROVAL_MAX_DAYS(default90,0disables, max3650). - A database migration runs automatically on start (new tables for standing approvals, a default vault column on devices).
- New personal vaults are unaffected; existing devices default to their owner's personal vault.