nntrivi2001
84e2a9f0ac
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>
28 lines
1.2 KiB
Bash
28 lines
1.2 KiB
Bash
#!/bin/bash
|
|
# @file pane-launch.sh
|
|
# @description Server mode, one Linux user per account (S3): installed as
|
|
# /opt/agenthub/libexec/pane-launch. A member's pane starts as
|
|
# `pane-launch <launch file>`: the dashboard creates the session AS the member
|
|
# through sudo, and sudo logs its whole command line — so the pane's
|
|
# environment (a pane token, a pool account's token) and its argv (the prompt)
|
|
# are not in that command line but in the launch file, which `write-as`
|
|
# wrote as the member (0600) from stdin. This reads it, deletes it, exports
|
|
# the environment and execs the command; no shell ever parses a value.
|
|
#
|
|
# The file is NUL-separated: the number of environment entries, the
|
|
# NAME=value entries, then the argv (none = a login shell).
|
|
# @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
|
|
set -eu
|
|
f=${1:?usage: pane-launch <launch file>}
|
|
mapfile -d '' -t parts <"$f"
|
|
rm -f -- "$f"
|
|
n=${parts[0]}
|
|
[[ "$n" =~ ^[0-9]+$ ]] || { echo "pane-launch: malformed launch file" >&2; exit 2; }
|
|
for kv in "${parts[@]:1:n}"; do
|
|
[[ "$kv" =~ ^[A-Za-z_][A-Za-z0-9_]*= ]] || { echo "pane-launch: bad variable" >&2; exit 2; }
|
|
export "$kv"
|
|
done
|
|
argv=("${parts[@]:n+1}")
|
|
if [ ${#argv[@]} -eq 0 ]; then exec -l "${SHELL:-/bin/bash}"; fi
|
|
exec "${argv[@]}"
|