Local code intelligence for developers and AI agents. Connect code, docs and infrastructure in a persistent graph, with CBM Lens, MCP tools, agent integrations and change-aware test selection.
C aiderastclaude-codecode-analysiscode-intelligencecodexcursorcypherdeveloper-toolsgemini-cligraph-visualizationkilocodeknowledge-graphmcpmcp-servermodel-context-protocolopencodesqlitetree-sitterwindsurf
fix(daemon): reword the overflow-uid note so the security audit stops blocking it
Martin Vogel085017ab2172
diff --git a/src/daemon/ipc.c b/src/daemon/ipc.cindex f8d7d70b4..a92befb08 100644--- a/src/daemon/ipc.c+++ b/src/daemon/ipc.c@@ -1596,9 +1596,12 @@ static uid_t posix_compute_ancestor_overflow_uid(void) {* DERIVED FRESH ON EVERY CALL, deliberately. This used to memoise via* pthread_once behind a comment claiming "immutable /proc state". That claim* was false in both halves: unshare(CLONE_NEWUSER) rewrites- * /proc/self/uid_map, and pthread_once state survives fork() already marked- * done -- so a process that forked and then changed namespace kept the parent- * answer and refused a directory it should have accepted. It happened to be+ * /proc/self/uid_map, and pthread_once state survives a forked child already+ * marked done -- so a process that forked and then changed namespace kept the+ * parent answer and refused a directory it should have accepted.+ * (Spelled without the call syntax on purpose: scripts/security-audit.sh+ * blocks that literal in src/, and an allow-list entry to let a COMMENT pass+ * would weaken a real check on a real file.) It happened to be* harmless because every caller today runs in a freshly exec'd process, but* that made a security decision depend on an invariant nothing enforced, and* the next fork-without-exec caller would have silently inherited a stale