On Wed, 14 Feb 2024 07:28:35 -0800 "H. Peter Anvin" <hpa@xxxxxxxxx> wrote: > On February 14, 2024 6:52:53 AM PST, Dave Hansen <dave.hansen@xxxxxxxxx> wrote: > >On 2/14/24 03:35, Petr Tesarik wrote: > >> This patch series implements x86_64 arch hooks for the generic SandBox > >> Mode infrastructure. > > > >I think I'm missing a bit of context here. What does one _do_ with > >SandBox Mode? Why is it useful? > > Seriously. On the surface it looks like a really bad idea – basically an ad hoc, *more* privileged version of user shave. Hi hpa, I agree that it kind of tries to do "user mode without user mode". There are some differences from actual user mode: First, from a process management POV, sandbox mode appears to be running in kernel mode. So, there is no way to use ptrace(2), send malicious signals or otherwise interact with the sandbox. In fact, the process can have three independent contexts: user mode, kernel mode and sandbox mode. Second, a sandbox can run unmodified kernel code and interact directly with other parts of the kernel. It's not really possible with this initial patch series, but the plan is that sandbox mode can share locks with the kernel. Third, sandbox code can be trusted for operations like parsing keys for the trusted keychain if the kernel is locked down, i.e. when even a process with UID 0 is not on the same trust level as kernel mode. HTH Petr T
