3 ms·
One interesting application of the idea of capabilities to an existing POSIX system is FreeBSD's Capsicum. (There is also a Linux port of Capsicum, but it has
by loeg 9y ago
One interesting application of the idea of capabilities to an existing POSIX system is FreeBSD's Capsicum. (There is also a Linux port of Capsicum, but it has not been integrated into Torvalds' tree.)
In Capsicum, capabilities are tracked on a per file descriptor basis.
A typical program opens any input paths, restricts capabilities on open fds (including stdio), and then enters sandbox mode.
Once the capability mode sandbox is entered, no additional capabilities can be granted, and filesystem access via absolute paths is revoked. (Sandbox mode programs are expected to access files they already have open, or to use relative accesses to walk file trees.)
Erroneous system calls generate ECAPMODE or ENOTCAPABLE errors if they attempt to perform actions they do not have permission to do.
- Majora320 9y agoWhat prevents a Sandbox mode program from just using a chain of `··`s to access the root?
- ithkuil 9y agoIIRC openat(2) honours the sandboxing rules
- loeg 9y agoAccess to ".." above the "root" of a given dirfd are disallowed in the sandbox. So for example, if you have an open dirfd with the LOOKUP capability when you enter the sandbox, you can access the following relative paths: ".", "./foo/bar", "./foo/.." But you cannot access these relative paths: "..", "./foo/../..", etc.