diff options
author | Liav A <liavalb@gmail.com> | 2022-11-04 19:20:11 +0200 |
---|---|---|
committer | Andrew Kaster <andrewdkaster@gmail.com> | 2022-11-26 12:42:15 -0700 |
commit | 718ae6862181b09dd13c8bb34917fe26048ff90a (patch) | |
tree | ed811919d704264535edec43544b8a214b664613 /Documentation | |
parent | 35efdb17f9c3856d1c241d9f63619a4d1174a509 (diff) | |
download | serenity-718ae6862181b09dd13c8bb34917fe26048ff90a.zip |
Kernel+LibCore+LibC: Implement support for forcing unveil on exec
To accomplish this, we add another VeilState which is called
LockedInherited. The idea is to apply exec unveil data, similar to
execpromises of the pledge syscall, on the current exec'ed program
during the execve sequence. When applying the forced unveil data, the
veil state is set to be locked but the special state of LockedInherited
ensures that if the new program tries to unveil paths, the request will
silently be ignored, so the program will continue running without
receiving an error, but is still can only use the paths that were
unveiled before the exec syscall. This in turn, allows us to use the
unveil syscall with a special utility to sandbox other userland programs
in terms of what is visible to them on the filesystem, and is usable on
both programs that use or don't use the unveil syscall in their code.
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions