3 ms·
This goes straight into my reference list. Sandboxing a process is confusing on Linux. I appreciate that the article focuses on approaches that drop privileges
by aktau 1y ago
This goes straight into my reference list. Sandboxing a process is confusing on Linux.
I appreciate that the article focuses on approaches that drop privileges without having root oneself. I've seen landlock referenced at time (https://lwn.net/Articles/859908/ https://lwn.net/Articles/859908/), but never so clearly illustrated (the verbosity feels like Vulkan).
Out of curiosity, I'd wish even more approaches were compared, even if they require root. I was about to mention seccomp-bpf as an approach that requires root, but skimming the LWN article I posted above I find: "Like seccomp(), Landlock is an unprivileged sandboxing mechanism; it allows a process to confine itself". It seems like I was wrong, and seccomp could be compared/contrasted.
- gnoack 1y agoAbsolutely, seccomp is also an unprivileged sandboxing mechanism in Linux. It does have the drawback however that the policies are defined in terms of system call numbers and their (register value) arguments, which complicates things, as it is a moving target. The problem was also recently discussed at https://lssna2025.sched.com/event/1zam9/handling-new-syscalls-in-seccomp-filters-tom-hromatka-oracle-corporate-paul-moore-microsoft https://lssna2025.sched.com/event/1zam9/handling-new-syscall...