sec: AppArmor v0.6 stub — load profiles in complain mode #11
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/sec-apparmor-v06-stubs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
v0.6 hardening tier 2 item 1 per docs/research/2026-05-05-agent-wave/04-hardening-tier-2.md.
Adds apparmor-parser/utils/profiles to both ks files, scripts/40-apparmor.sh (idempotent, complain-mode only), and 1-line firefox+thunderbird stubs at overlay/etc/apparmor.d/veilor.d/. Wired into install %post chain after 30-apply-v03-theme.sh.
v0.6 scope: 'loaded, present, nothing breaks'. Real policy authoring is v0.7+.
Per docs/research/2026-05-05-agent-wave/04-hardening-tier-2.md (v0.6 scope item 1). Adds: - apparmor-parser apparmor-utils apparmor-profiles to %packages in BOTH kickstart/veilor-os.ks (live ks) and overlay/usr/local/bin/ veilor-installer (generated install ks heredoc). - scripts/40-apparmor.sh — wires aa-complain on every veilor-shipped profile. Idempotent. "loaded, present, nothing breaks". - overlay/etc/apparmor.d/veilor.d/firefox — 1-liner stub (binary confinement marker only; full policy post-v0.6). - overlay/etc/apparmor.d/veilor.d/thunderbird — same pattern. - Wired 40-apparmor.sh into install %post chain after 30-apply-v03-theme.sh. Complain mode means: profiles loaded, kernel logs syscall denials but does NOT enforce. Operator can review audit.log post-install to inform v0.7 policy authoring.