Home
last modified time | relevance | path

Searched refs:no_new_privs (Results 1 – 5 of 5) sorted by relevance

/OK3568_Linux_fs/kernel/Documentation/userspace-api/
H A Dno_new_privs.rst21 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 …]
H A Dindex.rst19 no_new_privs
/OK3568_Linux_fs/kernel/include/linux/
H A Dsched.h1653 TASK_PFA_TEST(NO_NEW_PRIVS, no_new_privs) in TASK_PFA_TEST() argument
1654 TASK_PFA_SET(NO_NEW_PRIVS, no_new_privs) in TASK_PFA_TEST()
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dproc.rst292 NoNewPrivs no_new_privs, like prctl(PR_GET_NO_NEW_PRIV, ...)
/OK3568_Linux_fs/recovery/
HDrootfs.cpio.gz107070100A8AEB0000041ED0000000000000000000000116841B48100000000000000FD0000000200000000000000000000000200000000.�07070100A8B07C000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000900000000.gitkeep��07070100A8B07D000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000B00000000.skip_fsck����07070100A8AEB10000A1FF0000000000000000000000016841B0B600000007000000FD0000000200000000000000000000000400000000bin���usr/bin�07070100A8B07E000081A400000000000000000000000168412635000001CC000000FD0000000200000000000000000000001100000000busybox. ...