commit | 18076dbcb31ffcc1636d5a703591d81f21705f27 | [log] [tgz] |
---|---|---|
author | Alistair Delva <[email protected]> | Fri Oct 28 10:43:59 2022 -0700 |
committer | Frederick Mayle <[email protected]> | Fri Mar 03 15:45:40 2023 -0800 |
tree | bc1ce8880b80c1291f6b864f47711d6bfbe242c7 | |
parent | 3c6795b8906b224736c9eb914dd9bf50204f52c7 [diff] |
CHERRY-PICK: Fix "Extend host glibc workaround to clone3" The workaround was applied inside a conditional for __NR_rseq which meant it would not take effect if used against a glibc with rseq but not clone3, such as the one in Debian 10. Test: local Bug: 246990922 Change-Id: I52e5be3d489c08e527211ab48848e73aabbbca2a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/minijail/+/3989233 Auto-Submit: Alistair Delva <[email protected]> Tested-by: Alistair Delva <[email protected]> Commit-Queue: Alistair Delva <[email protected]> Reviewed-by: Allen Webb <[email protected]> Reviewed-by: Frederick Mayle <[email protected]>
The Minijail homepage is https://google.github.io/minijail/.
The main source repo is https://chromium.googlesource.com/chromiumos/platform/minijail.
There might be other copies floating around, but this is the official one!
Minijail is a sandboxing and containment tool used in ChromeOS and Android. It provides an executable that can be used to launch and sandbox other programs, and a library that can be used by code to sandbox itself.
You're one git clone
away from happiness.
$ git clone https://chromium.googlesource.com/chromiumos/platform/minijail $ cd minijail
Releases are tagged as linux-vXX
: https://chromium.googlesource.com/chromiumos/platform/minijail/+refs
See the HACKING.md document for more details.
See the RELEASE.md document for more details.
See the tools/README.md document for more details.
We've got a couple of contact points.
The following talk serves as a good introduction to Minijail and how it can be used.
The ChromiumOS project has a comprehensive sandboxing document that is largely based on Minijail.
After you play with the simple examples below, you should check that out.
# id uid=0(root) gid=0(root) groups=0(root),128(pkcs11) # minijail0 -u jorgelo -g 5000 /usr/bin/id uid=72178(jorgelo) gid=5000(eng) groups=5000(eng)
# minijail0 -u jorgelo -c 3000 -- /bin/cat /proc/self/status Name: cat ... CapInh: 0000000000003000 CapPrm: 0000000000003000 CapEff: 0000000000003000 CapBnd: 0000000000003000
Q. “Why is it called minijail0?”
A. It is minijail0 because it was a rewrite of an earlier program named minijail, which was considerably less mini, and in particular had a dependency on libchrome (the ChromeOS packaged version of Chromium's //base). We needed a new name to not collide with the deprecated one.
We didn‘t want to call it minijail2 or something that would make people start using it before we were ready, and it was also concretely less since it dropped libbase, etc. Technically, we needed to be able to fork/preload with minimal extra syscall noise which was too hard with libbase at the time (onexit handlers, etc that called syscalls we didn’t want to allow). Also, Elly made a strong case that C would be the right choice for this for linking and ease of controlled surprise system call use.
https://crrev.com/c/4585/ added the original implementation.
Source: Conversations with original authors, ellyjones@ and wad@.