diff --git a/docs/decisions/0002-baseline-restricts-namespaces.md b/docs/decisions/0002-baseline-restricts-namespaces.md index 0c397e3..8d714a9 100644 --- a/docs/decisions/0002-baseline-restricts-namespaces.md +++ b/docs/decisions/0002-baseline-restricts-namespaces.md @@ -26,5 +26,6 @@ a restriction it did not have. - **Jobs that fail on `baseline`:** any job that creates namespaces. That covers rootless containers, `unshare`, `bwrap` and some test harnesses. They need `userns`, chosen per profile. -- **Not yet verified:** that the GitHub runner itself works under - `RestrictNamespaces=yes`. This is checked on the test VM before Alpha. +- **Verified on the ARM64 test VM:** the GitHub runner registers and runs + jobs under `RestrictNamespaces=yes`, and `unshare -U` is refused inside + them ([verification.md](../verification.md), assumption 1). diff --git a/docs/threat-model.md b/docs/threat-model.md index c9ad022..fff2dac 100644 --- a/docs/threat-model.md +++ b/docs/threat-model.md @@ -8,9 +8,13 @@ one Linux host that also does other work. This document says: - which mechanism each protection rests on; - how `runner-slice check` proves that mechanism on the running host. -Every claim here is SYNTHETICALLY TESTED unless it says otherwise. Nothing in -this document has yet been observed on a real host running this code. The -evidence levels are defined in [verification.md](verification.md). +Every claim here is SYNTHETICALLY TESTED by the drills. The boundary was also +observed on one real host, an Ubuntu 24.04 aarch64 VM with systemd 255 and two +real GitHub runners, at RUNTIME VERIFIED and REBOOT VERIFIED. It was observed +both by `check` and from inside real jobs +([acceptance/2026-10-arm64.md](acceptance/2026-10-arm64.md)). On any other +host, these claims are unverified. The evidence levels are defined in +[verification.md](verification.md). ## Who is trusted