Repository navigation
Released 2026-11-08.
Two things a local gateway should have had from the start: it stops being
readable from its own uid, and its README stops being a manual.
One operational note: on Linux serve is no longer dumpable, so you cannot
attach a debugger to it as the same user any more — use root, and expect no
core dump from that process. Drop-in otherwise — no config or storage changes.
Security
servecallsprctl(PR_SET_DUMPABLE, 0)at startup on Linux, so a process
running as the same user can no longer read the gateway's memory through
/proc/<pid>/memor attach a debugger to pull real keys out of it
(PTRACE_ATTACHand/proc/<pid>/{environ,mem,maps}now fail withEPERM
for same-uid readers, whateverkernel.yama.ptrace_scopesays). Only the
process holding the keys can do this:execve(2)resets the flag, so a
launcher cannot do it on someone else's behalf. Best effort — a kernel that
refuses logs a warning instead of stopping the gateway. It does not protect
the vault files:vault.keyis still only as private as its file mode
(seedeploy)
Docs
- The README is now the front page — what it is, what it protects and does not,
install, a five-minute quick start — and the rest moved todocs/:usage.md
(routing, commands, health fields, vault, FAQ),service.md(deploy),
security.md(threat model, audit log, bounds),performance.md. Nothing was
dropped; the Chinese README mirrors the new shape and points at the same docs - The README gains a "same user, not same process" section: an agent runs as
your uid, so the channels a local gateway does not close by itself are your
files (vault.key→ offline decrypt) and your/proc. Both hitkeysink
standalone;deploycloses the file one - The self-scored comparison table is gone. It lined keysink up against tools
that solve different problems, on rows keysink chose, and won every row; a
reader learns nothing from that. "What this is not" stays and now names the
alternative per bullet, including the case where a plain.envis the
simpler answer docs/perf-test-plan.mdnow exists: the scenario matrix, metric
definitions and aggregation behindscripts/perf.shlived only in script
comments, and two of those comments pointed at this file before it was
ever committed- The README gains a measured performance baseline (one machine, one run;
scripts/perf.shreproduces it on your own hardware) and a pre-1.0 note
that the CLI surface may still change between releases; the Chinese README
picks up the docs.rs and Platforms badges the English one already had