audit 5: the supervisor socket the panel's alone, OpenDKIM logs and oversigns From

M17: the supervisord control socket is root:supervisor 0770, a group whose
one member is the panel; OpenDKIM and Postfix keep `selfpost` for the files
under /data and no longer reach the socket.

L30, read in OpenDKIM 2.11.0~beta2's source first: it logs through
syslog(3) only and has no Logfile option, and nothing in the container
served /dev/log. internal/syslogrelay (the panel binary with
-syslog-relay=/run/syslog/log, program syslog-relay before OpenDKIM,
/dev/log a link to its socket) passes the datagrams to stdout, error and
worse marked. opendkim.conf: Syslog yes, Canonicalization relaxed/simple,
OversignHeaders From (RFC 6376 § 3.4, § 8.15). e2e: OpenDKIM's start line
reaches the container log; every program RUNNING; DKIM verifies.

Tested on the test server: go vet + go test of 26 packages, make e2e (all
pass, 626 s) on this tree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/security.md

@@ -209,7 +209,10 @@ operator can act on it.
 - Rendering goes through `html/template` with auto-escaping (queue, log,
   journal, themes).
 - The panel process is **not root** (`user=panel` in supervisord); path access
-  is granted through the `selfpost` group with minimal permissions.
+  is granted through the `selfpost` group with minimal permissions. The
+  supervisord control socket, which can stop or restart any program, is the
+  `supervisor` group's, whose one member is the panel; OpenDKIM and Postfix
+  share `selfpost` for files and do not reach it (`2.6.0`).
 
 ### Mail path (security-relevant)