Searched refs:setuid (Results 1 – 25 of 46) sorted by relevance
12
15 例子就是setuid/setgid控制程序和文件的能力。为了避免父程序也获得这些权限，内18 - 程序在setuid后，动态装载器处理 ``LD_*`` 环境变量的不同方式。29 不会授予权限去做任何没有execve调用就不能做的事情。比如， setuid 和 setgid42 适当权限的任务仍然可以调用 ``setuid(2)`` 并接收 SCM_RIGHTS 数据报。50 运行的程序都设置了 ``no_new_privs`` ，那么那个 uid 将无法通过攻击 setuid，
6 its parent did not have. The most obvious examples are setuid/setgid13 a program is setuid.27 been done without the execve call. For example, the setuid and setgid43 ``setuid(2)`` and receive SCM_RIGHTS datagrams.55 escalate its privileges by directly attacking setuid, setgid, and
76 int setuid; member234 opts->setuid = 0; in parse_mount_options()266 opts->setuid = 1; in parse_mount_options()390 if (opts->setuid) in devpts_show_options()561 inode->i_uid = opts->setuid ? opts->uid : current_fsuid(); in devpts_pty_new()
19 if (setuid(TEST_UID)) in do_migration_fn()35 if (setuid(TEST_UID)) in do_controller_fn()
277 if (setuid(child_uid) < 0) in test_setuid()492 if (setuid(NO_POLICY_UGID) < 0) in main()507 if (setuid(RESTRICTED_PARENT_UGID) < 0) in main()
27 especially since programs often only call setuid() to drop privileges to a30 switch to through setuid() beyond allowing a switch to any user on the system.39 do any unapproved actions (e.g. setuid to uid 0 or create/enter new user92 "Since setuid only affects the current process, and since the SELinux controls
171 ASSERT_EQ(setuid(65534), 0); in TEST()
67 if (setuid(user) < 0) in fork_child()
108 if (setuid(0) != 0) in create_and_enter_ns()
175 if (setuid(0) != 0) { in create_and_enter_userns()
136 if (setuid(USHRT_MAX)) in run_tests()
104 if (setuid(0)) in create_and_enter_userns()
228 if (setuid(1000) < 0) { in main()
98 COND_SYSCALL(setuid);
37 23 32 setuid sys_setuid1638 23 64 setuid sys_setuid
31 23 32 setuid - sys_setuid16221 213 64 setuid sys_setuid -
208 if (setuid(0)) in setid_userns_root()
197 from "pinning" vulnerable setuid/setgid files against being upgraded by247 This value can be used to query and set the core dump mode for setuid
208 program (fusermount) is needed, which is installed setuid root.233 setuid and setgid bits when executing programs. To ensure this
113 103 n64 setuid sys_setuid
33 21 common setuid sys_setuid
81 will run with root permissions when a setuid binary owned by root
116 105 common setuid sys_setuid