You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Security: gominimal/min-zed
Security
docs/security.md
What never leaves the host
Only the public key enters the box. Each session gets its own ed25519
key under ~/.local/state/min-zed/sessions/NAME, and the box gets it in
~/.ssh/min-zed/authorized_keys.
~/.ssh/config is yours. Nothing under ~/.ssh is touched until
min-zed ssh-config runs. That adds two marked lines at the top of
~/.ssh/config and keeps the stanzas in ~/.ssh/min-zed.conf;
--remove restores ~/.ssh/config byte for byte. A dated backup is taken
before every write.
Zed's files are yours. Nothing in ~/.config/zed is touched until
min-zed config runs; then only the min-zed.* entries of
ssh_connections (and the key, if you had none) and the marked blocks in
tasks.json and keymap.json change, with a backup first. A file that
does not parse is refused, not repaired.
Tasks run one fixed program. Each Minimal task runs
$HOME/.local/bin/min-zed with fixed arguments. None puts a $ZED_*
variable in its command (Zed pastes those in unquoted), so a folder or
file name never becomes part of a shell command.
What the box reports is checked. The user name, home, sshd path and
host key a box prints are validated before any of them reaches
known_hosts, a stanza or an ssh option.
The box's host key is pinned (StrictHostKeyChecking=yes, never
accept-new), and re-pinned by _proxy on every connect, so only the box
min itself reaches can present it.
Destroy always asks [y/N], default No; -y is the only way past it.
gc asks for each session.
No agent or X11 forwarding. Each stanza sets ForwardAgent no,
ForwardX11 no, ForwardX11Trusted no before any Host * of yours can
turn them on, and the box's sshd runs with AllowAgentForwarding=no and
X11Forwarding=no. An explicit ssh -A min-zed.NAME still wins on the
client; then only the box's sshd refuses it (defence in depth, not a
boundary). Port forwards work.
Agent logins stay in the box. Claude Agent in a box window signs in
inside the box; that login is destroyed with the box.
Boxes are never woken to be asked.gc and status read the host's
process table to tell what is in use; no box is contacted to find out.