Searched refs:setuid (Results 1 – 23 of 23) sorted by relevance
| /Linux-v4.19/Documentation/userspace-api/ |
| D | no_new_privs.rst | 6 its parent did not have. The most obvious examples are setuid/setgid
13 a program is setuid.
27 been done without the execve call. For example, the setuid and setgid
43 ``setuid(2)`` and receive SCM_RIGHTS datagrams.
55 escalate its privileges by directly attacking setuid, setgid, and
|
| /Linux-v4.19/fs/devpts/ |
| D | inode.c | 97 int setuid; member
255 opts->setuid = 0; in parse_mount_options()
287 opts->setuid = 1; in parse_mount_options()
411 if (opts->setuid) in devpts_show_options()
581 inode->i_uid = opts->setuid ? opts->uid : current_fsuid(); in devpts_pty_new()
|
| /Linux-v4.19/tools/testing/selftests/mount/ |
| D | unprivileged-remount-test.c | 175 if (setuid(0) != 0) { in create_and_enter_userns()
|
| /Linux-v4.19/kernel/ |
| D | sys_ni.c | 171 COND_SYSCALL(setuid);
|
| D | sys.c | 608 SYSCALL_DEFINE1(setuid, uid_t, uid) in SYSCALL_DEFINE1() argument
|
| /Linux-v4.19/tools/perf/arch/s390/entry/syscalls/ |
| D | syscall.tbl | 31 23 32 setuid - compat_sys_s390_setuid16
221 213 64 setuid sys_setuid -
|
| /Linux-v4.19/arch/s390/kernel/syscalls/ |
| D | syscall.tbl | 31 23 32 setuid - compat_sys_s390_setuid16
221 213 64 setuid sys_setuid -
|
| /Linux-v4.19/arch/powerpc/include/asm/ |
| D | systbl.h | 30 SYSCALL_SPU(setuid)
|
| /Linux-v4.19/arch/parisc/kernel/ |
| D | syscall_table.S | 87 ENTRY_SAME(setuid)
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | fuse.txt | 222 program (fusermount) is needed, which is installed setuid root.
249 setuid and setgid bits when executing programs. To ensure this
|
| D | affs.txt | 41 setuid[=uid] This sets the owner of all files and directories in the file
|
| /Linux-v4.19/Documentation/sysctl/ |
| D | fs.txt | 213 from "pinning" vulnerable setuid/setgid files against being upgraded by
263 This value can be used to query and set the core dump mode for setuid
|
| D | kernel.txt | 426 a setuid binary) then %pK will not leak kernel pointers to unprivileged
|
| /Linux-v4.19/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 116 105 common setuid __x64_sys_setuid
|
| D | syscall_32.tbl | 37 23 i386 setuid sys_setuid16 __ia32_sys_setuid16
|
| /Linux-v4.19/tools/perf/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 116 105 common setuid __x64_sys_setuid
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | binfmt-misc.rst | 81 will run with root permissions when a setuid binary owned by root
|
| D | kernel-parameters.txt | 2834 is to be setuid root or executed by root.
|
| /Linux-v4.19/arch/arm/tools/ |
| D | syscall.tbl | 37 23 common setuid sys_setuid16
|
| /Linux-v4.19/arch/um/drivers/ |
| D | Kconfig | 323 privleges, setuid binaries, or SLIP devices on the host. This
|
| /Linux-v4.19/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 901 preconfigured device, allowing it to avoid using the setuid uml_net
1000 You will likely need the setuid helper, or the switch daemon, or both.
1010 to be setuid root.
1203 The easiest way to get up and running is to let the setuid uml_net
1208 the setuid helper, use it to get up and running, then read the next
1511 setuid root if you're not running UML as root. This is because the
1691 root access or setuid binaries on the host.
|
| /Linux-v4.19/Documentation/filesystems/cifs/ |
| D | README | 279 is configured setuid for user mounts) unless the "uid="
|
| /Linux-v4.19/init/ |
| D | Kconfig | 1176 system calls related to UIDs, GIDs, and capabilities, such as setuid,
|
