| Personal website | https://digikod.net |
| Landlock | https://landlock.io |
| Bluesky | https://bsky.app/profile/l0kod.bsky.social |
| https://twitter.com/l0kod |
Landlock is an unprivileged kernel feature that enables all Linux users to sandbox their processes. Complementary to seccomp, developers can leverage Landlock to restrict their programs in a fine-grained way. While Landlock can be used by end users through sandboxer tools, there is currently no well-integrated solution to define security policies tailored to system services. Although AppArmor and seccomp security policies can already be tied to a system unit, we aim to provide a more dynamic, standalone, and unprivileged option with Landlock. In this talk, we'll briefly explain what Landlock is and highlight its differences from other Linux security features (e.g., namespaces, seccomp, other LSMs). We'll then focus on the new configuration format we are designing for Landlock security policies, its characteristics, and how it could extend systemd units by taking into account runtime context (e.g., XDG variables). See https://github.com/systemd/systemd/pull/39174
A security model for systemd by @pid_eins at #AllSystemsGo
https://cfp.all-systems-go.io/all-systems-go-2025/talk/FE98ZY/
I gave a (2nd) talk at #linuxsecuritysummit on a new configuration format, #Landlock Config, to define sandboxing security policies. The provided library (Rust and C for now) can also compose configurations to ease sharing and maintenance. This is especially useful to sandbox programs without modifying them, and to easily manage and audit Landlock policies. It could also be part of other configuration formats such as the OCI runtime specification.
https://lsseu2025.sched.com/event/25GET
Greg K-H
Simon Josefsson
Linux Security Summit 🐧 