Files
AgentHub/scripts/server/write-as.sh
T
nntrivi2001 84e2a9f0ac feat(server-s3): one Linux user per account (S3) — experimental
Server mode can now run each account as its own Linux user (ah-<name>)
when `agenthub server install-system` has set S3 up. The dashboard
reaches a member only through sudo -u / write-as / pane-launch, reads a
member's files only through owner- and type-checked opens, and hooks
are authenticated by peer uid. Local mode and server mode without S3
are unchanged.

EXPERIMENTAL: tested with fake sudo and fake accounts only. It has not
yet been verified on a real install with real member accounts, sudo or
a real Codex login. Do not offer it to real users yet.

- S3 core: provisioning, per-member tmux servers, the proxy key
  gateway, shared tools in /opt, dropped capabilities for children
  (P0–P5)
- P4: plan and quota per member home
- P6: ~/.claude.json seed; opt-in plugin baseline installed as the
  member; managed-settings spike script (not run)
- P7: Codex account pool (`agenthub accounts add --tool codex`)
- Roles merged with main's admin / analyst / developer: analysts write
  only their own rows, under S3 as well
- Per-account prefs: one implementation (Chat UI + onboarding)
- Security reviews F1–F49 (five rounds), each fix with a regression
  test: symlink/TOCTOU-safe member reads, no host writes in a member
  home, credentials and the data dir never served, owner and folder
  account must agree, pane tokens bound to the pane's uid, bounded
  sudo/tmux/git calls and member reads (no hang or crash from a member),
  async route rejections answer 500 instead of exiting
- Docs: docs/SERVER-MODE.md (S3 model, accepted ceilings, operator
  runbook), docs/plans/server-mode/S3-PLAN.md, CLAUDE.md S3 rules

Tests: server 2838/2841 (3 need 127.0.0.1:3000, held on this box);
client 1162/1162; tsc clean; headers check passes.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-10-09 14:57:10 +07:00

42 lines
1.7 KiB
Bash

#!/bin/sh
# @file write-as.sh
# @description Server mode, one Linux user per account (S3): installed as
# /opt/agenthub/libexec/write-as. The dashboard runs it AS a member through
# sudo (`sudo -n -u ah-<name> /opt/agenthub/libexec/write-as <path> [mode]`)
# for every change it makes inside that member's home — the file editor, a
# `.gitignore` line, the files a pane reads (prompt, proxy settings, context
# copies, drops, a session's launch file) — because the dashboard itself may
# never write, chmod or delete there: the member can swap any name in their
# own home, and a write by another account would follow the swap. As the
# member this can only do what the member could. Content comes on stdin,
# never in argv (sudo logs argv). Modes:
# (none) stdin into the file in place (keeps its mode and owner)
# append stdin appended
# replace stdin into a new 0644 file renamed over the path (atomic)
# private same, 0600
# mkdir the directory, 0755, parents included
# remove the path, recursively (rm never follows a symlink it removes)
# @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
set -eu
if [ $# -lt 1 ] || [ $# -gt 2 ]; then
echo "usage: write-as <absolute path> [append|replace|private|mkdir|remove]" >&2
exit 2
fi
case "$1" in
/*) ;;
*) echo "write-as: an absolute path is required" >&2; exit 2 ;;
esac
swap() {
t=$(mktemp "$1.XXXXXX")
cat >"$t" && chmod "$2" "$t" && mv -f "$t" "$1" || { rm -f "$t"; exit 1; }
}
case "${2:-}" in
"") exec cat >"$1" ;;
append) exec cat >>"$1" ;;
replace) swap "$1" 0644 ;;
private) swap "$1" 0600 ;;
mkdir) exec mkdir -p -m 0755 -- "$1" ;;
remove) exec rm -rf -- "$1" ;;
*) echo "write-as: unknown mode: $2" >&2; exit 2 ;;
esac