feat: deploy cloud-only RMM and verify audited APT diagnostics
Rust development slice / linux (push) Failing after 7s

This commit is contained in:
2026-11-13 13:49:11 +01:00
parent 6c3203d725
commit fbef0e4e2f
48 changed files with 3125 additions and 34 deletions
+8 -4
View File
@@ -4,7 +4,10 @@ After=local-fs.target
[Service]
Type=simple
User=root
# System services default to root. Avoid explicit User=root: systemd 255's
# seccomp setup otherwise drops CAP_SETUID and retains setup inheritable caps.
# Controller verification still requires euid 0, the exact capability sets,
# zero inherited/ambient caps, NNP and the full sandbox below.
Group=rmm-agent
Environment=RMM_HELPER_CONFIG=/etc/rmm/apt-helper.json
ExecStartPre=/usr/local/libexec/rmm-privileged-helper --probe-native
@@ -38,9 +41,10 @@ CapabilityBoundingSet=CAP_CHOWN CAP_DAC_OVERRIDE CAP_FOWNER CAP_FSETID CAP_SETGI
# Trusted setup needs mount/unshare/fork/capset/prctl/seccomp. There is deliberately
# no outer @mount deny; the irreversible worker filter denies it after setup.
SystemCallFilter=~@reboot @module @raw-io @swap @clock @debug
# Existing helper clock trust reads adjtimex(modes=0). Mutating adjtimex still
# requires CAP_SYS_TIME, absent from the bounding set; other @clock calls denied.
SystemCallFilter=adjtimex
# glibc implements the read-only adjtimex(modes=0) query via clock_adjtime on
# Ubuntu. Neither syscall can change time without CAP_SYS_TIME (not bounded).
# Keep all other @clock operations denied; never bypass trusted-clock checks.
SystemCallFilter=adjtimex clock_adjtime
SystemCallErrorNumber=EPERM
ReadWritePaths=/var/lib/dpkg /var/lib/rmm-helper /var/lib/rmm-apt-transaction /usr/share/rmm-mvp-test
Restart=on-failure