Linux Sandboxing with Landlock
summary
Landlock lets unprivileged processes declare and enforce least‑privilege policies at runtime by creating a ruleset, adding file and resource rules tied to open file descriptors, then sealing the process with landlock_create_ruleset + landlock_restrict_self. Policies scope to the process and its children and cannot be removed; setuid execution does not lift restrictions. Current controls cover fine‑grained file read/write/exec and port bind/connect filtering, with upcoming IPC scoping and UDP/egress options; distributions and helper libraries already ship support and real applications (archive viewers, package tools) are adopting it.
AI-written summary · about
chapters (10)
- 0:00The need for sandboxing
- 2:39Existing security mechanisms
- 7:41Introducing Landlock
- 10:48Landlock use cases
- 14:32How Landlock works
- 16:41Implementing Landlock
- 19:25Adoption and ecosystem
- 22:10Security insights and tests
- 24:31Future roadmap and contribution
- 26:46Q&A session
related talks
32mLinux Sandboxing with Landlock
37mSandboxing Applications with Landlock
36mHow to Safely Restrict Access to Files in a Programmatic Way with Landlock?
40mUpdate on Landlock: Lifting the File Reparenting Limits and Supporting Network Rules
01h 17mLandlock Workshop: Sandboxing Application for Fun and Protection
40mLandlock Config
23mUpdate on Landlock: Audit, Debugging and Metrics
38mSandboxing in Linux with zero lines of code