Skip to content

v0.6.1 — the operator's blind spots, found by unbriefed agents

Choose a tag to compare

@xezpeleta xezpeleta released this 05 Oct 18:20
· 18 commits to main since this release

v0.6.1 — the operator's blind spots, found by unbriefed agents

Every fix in this revision came out of a live blind test: real
agents with no briefing, a real enforcing host, and an operator
who could only watch. The agents behaved — the tools around them
had the blind spots.

sysh (host)

sysh-result says WHICH no-result it is

"pending, expired, or never approved" was one message for three
different situations. An agent that cannot tell pending from
expired waits out the full TTL for a request that is already
dead. The builtin now asks the drop box and answers precisely:
pending says "wait and re-check"; expired says "re-run the
command to file a fresh request"; a bad id says so. The audit
event carries the same classification, so the operator's wall
reads it too.

Live result: an unbriefed agent, told its request had expired,
re-filed unprompted and completed the task on the next approval.

doctor: PermitTTY is a choice, not drift

doctor demanded permittty no while the shipped sshd drop-in
sets yes for the argv console — a fresh 0.6.0 install failed
its own doctor. Both values are legitimate (yes = console,
no = -c only); doctor accepts either and fails on anything
else.

sy watch (operator)

Expired requests leave; every row counts down

The waiting panel kept expired rows around, faded, with buttons
that answered nothing. Expired rows now leave the moment they
expire (a countdown shows the TTL — m:ss, amber in the last two
minutes, red in the last one) and one quiet line says how many
went that way. Refuse-by-default, visible by default.

The ceremony tells you what to type, and recovers from a miss

The typed-argument challenge highlights the exact argv element
to type — the proof is reading the argv, never guessing. A
mistyped attempt used to consume the ceremony and leave a dead
modal; it now fetches a fresh one immediately. An expired
request can no longer open a ceremony at all.

Agent state: is it waiting for me? did it get the answer?

New per-request correlation of journal events (filed, every
sysh-result poll with its classification, the approval, the
fetch): each pending row reads like "agent waiting · 6 polls ·
last check 12s ago", and answered requests are listed with
their outcome. /api/agents exposes the same table.

The answer lands everywhere at once

Approving used to clear the modal instantly but leave the
waiting row for the next poll cycle (~10s with a down host).
The row is now answered the moment the ceremony returns, the
approvals poller skips hosts the follower reports down, the
root channel runs with ConnectTimeout everywhere, and static
assets ship Cache-Control: no-store (a stale cached UI is a
support case wearing a disguise).

Upgrade

Same package, same config, no contract change — argv rules,
exits, and the approval ceremony are untouched.

sudo apt install ./sysh_0.6.1_amd64.deb

Verify with sysh doctor (now clean on fresh installs) and
sysh approvals as root.