diff options
| author | Andy Lutomirski | 2012-07-05 20:23:24 +0200 |
|---|---|---|
| committer | James Morris | 2012-07-07 16:25:48 +0200 |
| commit | c540521bba5d2f24bd2c0417157bfaf8b85e2eee (patch) | |
| tree | 64d387e5910f377b178bb168659684a0f09b20c2 /Documentation/prctl | |
| parent | Merge tag 'ecryptfs-3.5-rc6-fixes' of git://git.kernel.org/pub/scm/linux/kern... (diff) | |
| download | kernel-qcow2-linux-c540521bba5d2f24bd2c0417157bfaf8b85e2eee.tar.gz kernel-qcow2-linux-c540521bba5d2f24bd2c0417157bfaf8b85e2eee.tar.xz kernel-qcow2-linux-c540521bba5d2f24bd2c0417157bfaf8b85e2eee.zip | |
security: Minor improvements to no_new_privs documentation
The documentation didn't actually mention how to enable no_new_privs.
This also adds a note about possible interactions between
no_new_privs and LSMs (i.e. why teaching systemd to set no_new_privs
is not necessarily a good idea), and it references the new docs
from include/linux/prctl.h.
Suggested-by: Rob Landley <rob@landley.net>
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Acked-by: Kees Cook <keescook@chromium.org>
Signed-off-by: James Morris <james.l.morris@oracle.com>
Diffstat (limited to 'Documentation/prctl')
| -rw-r--r-- | Documentation/prctl/no_new_privs.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/prctl/no_new_privs.txt b/Documentation/prctl/no_new_privs.txt index cb705ec69abe..f7be84fba910 100644 --- a/Documentation/prctl/no_new_privs.txt +++ b/Documentation/prctl/no_new_privs.txt @@ -25,6 +25,13 @@ bits will no longer change the uid or gid; file capabilities will not add to the permitted set, and LSMs will not relax constraints after execve. +To set no_new_privs, use prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0). + +Be careful, though: LSMs might also not tighten constraints on exec +in no_new_privs mode. (This means that setting up a general-purpose +service launcher to set no_new_privs before execing daemons may +interfere with LSM-based sandboxing.) + Note that no_new_privs does not prevent privilege changes that do not involve execve. An appropriately privileged task can still call setuid(2) and receive SCM_RIGHTS datagrams. |