Searched refs:no_new_privs (Results 1 – 4 of 4) sorted by relevance
| /linux-5.19.10/Documentation/userspace-api/ |
| D | no_new_privs.rst | 21 These are all ad-hoc fixes. The ``no_new_privs`` bit (since Linux 3.5) is a
24 can set ``no_new_privs``. Once the bit is set, it is inherited across fork,
25 clone, and execve and cannot be unset. With ``no_new_privs`` set, ``execve()``
32 To set ``no_new_privs``, use::
37 in ``no_new_privs`` mode. (This means that setting up a general-purpose
38 service launcher to set ``no_new_privs`` before execing daemons may
41 Note that ``no_new_privs`` does not prevent privilege changes that do not
45 There are two main use cases for ``no_new_privs`` so far:
50 if ``no_new_privs`` is set.
52 - By itself, ``no_new_privs`` can be used to reduce the attack surface
[all …]
|
| D | index.rst | 19 no_new_privs
|
| /linux-5.19.10/include/linux/ |
| D | sched.h | 1779 TASK_PFA_TEST(NO_NEW_PRIVS, no_new_privs) in TASK_PFA_TEST() argument
1780 TASK_PFA_SET(NO_NEW_PRIVS, no_new_privs) in TASK_PFA_TEST()
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | proc.rst | 293 NoNewPrivs no_new_privs, like prctl(PR_GET_NO_NEW_PRIV, ...)
|