Searched refs:setgid (Results 1 – 15 of 15) sorted by relevance
2 its parent did not have. The most obvious examples are setuid/setgid23 been done without the execve call. For example, the setuid and setgid49 escalate its privileges by directly attacking setuid, setgid, and
102 int setgid; member169 opts->setgid = 0; in parse_mount_options()206 opts->setgid = 1; in parse_mount_options()342 if (opts->setgid) in devpts_show_options()631 inode->i_gid = opts->setgid ? opts->gid : current_fsgid(); in devpts_pty_new()
75 a setgid file is written to. This is a security measure. The kernel has been78 to run mandatory lock candidates with setgid privileges.169 permissions (remove the setgid bit) before trying to read or write to it.
79 setgid bit set, in which case it takes the gid from the80 parent directory, and also gets the setgid bit set if it is
44 setgid[=gid] Same as above, but for gid.
249 setuid and setgid bits when executing programs. To ensure this
170 if (setgid(0) != 0) { in create_and_enter_userns()
116 ENTRY_SAME(setgid)
52 SYSCALL_SPU(setgid)
115 106 common setgid sys_setgid
55 46 i386 setgid sys_setgid16
193 from "pinning" vulnerable setuid/setgid files against being upgraded by
109 Cifs_mkdir and cifs_create now respect the setgid bit on parent dir.112 files (e.g. "cp -a") to Windows servers. For mkdir and create honor setgid bit
386 SYSCALL_DEFINE1(setgid, gid_t, gid) in SYSCALL_DEFINE1() argument
1382 setgid, and capset.