Skip to content

v0.5.0 — agent key hygiene, root mode, GPLv3

Choose a tag to compare

@xezpeleta xezpeleta released this 04 Oct 22:50
· 31 commits to main since this release

v0.5.0 — agent key hygiene, root mode, GPLv3

New

Agent keys expire (hygiene without a CA)

keys.map entries take an optional third field — expires: in
RFC3339. The gateway refuses an expired key before argv is even
parsed, with a denial that names the key and says how to fix it:

sysh auth add --ttl 7d sy/engagement-2025-06-12 ~/.ssh/id_ed25519.pub
sysh auth rotate sy/old --ttl 30d
sysh auth list            # shows expiry, flags EXPIRED
sysh doctor               # warns on expired + expiring-soon keys

No certificate authority to run or protect: expiry is root-owned
host data, checked where every other decision is checked. Rotation
adds the new key before removing the old one, and refuses to
"rotate" to the same key material.

Root mode — the explicit opt-out

mode = "root" (with a required timeout) is for a custom host you
consider disposable: deny rules still hold, everything else runs as
root through one wildcard sudoers grant sysh policy install
generates. Every exec keeps its PATH resolution, argv checks,
timeout, and pre/post journal events with PRIV=1.

Honest by construction: allow/approval rules in root mode are lint
errors (they gate nothing), install requires sudo and active auditd
rules, sysh doctor warns about root mode on every run. After the
first root exec the agent can mint access the journal never sees —
the docs say so everywhere the mode is named.

Browser alerts in sy watch (BETA)

Click the bell in the header; the browser asks for notification
permission and you answer. New approval requests then pop as native
alerts — argv, key, host — like calendar invites, click to focus the
pending panel. The ceremony never leaves the server.

Beta: not yet battle-tested. The pending banner and the terminal
ceremony remain the reliable channels.

Changed

  • Relicensed MIT → GPLv3. The vendored Apache-2.0 pi-replay.js
    keeps its notice (one-way compatible).
  • Docs: the "not root-without-approval" claim now names the
    mechanism — exact-argv sudoers grants generated by the operator's
    own sysh policy install; the agent invoking sudo itself is
    denied like any other argv.

Install

curl -LO https://github.com/xezpeleta/sysh/releases/download/v0.5.0/sysh_0.5.0_amd64.deb
sudo apt install ./sysh_0.5.0_amd64.deb

Or build from source: go build ./cmd/sysh && go build ./cmd/sy.
Docs: https://xezpeleta.github.io/sysh/