aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/prctl/no_new_privs.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/prctl/no_new_privs.txt')
-rw-r--r--Documentation/prctl/no_new_privs.txt7
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
25add to the permitted set, and LSMs will not relax constraints after 25add to the permitted set, and LSMs will not relax constraints after
26execve. 26execve.
27 27
28To set no_new_privs, use prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0).
29
30Be careful, though: LSMs might also not tighten constraints on exec
31in no_new_privs mode. (This means that setting up a general-purpose
32service launcher to set no_new_privs before execing daemons may
33interfere with LSM-based sandboxing.)
34
28Note that no_new_privs does not prevent privilege changes that do not 35Note that no_new_privs does not prevent privilege changes that do not
29involve execve. An appropriately privileged task can still call 36involve execve. An appropriately privileged task can still call
30setuid(2) and receive SCM_RIGHTS datagrams. 37setuid(2) and receive SCM_RIGHTS datagrams.