Searched refs:CAP_SYS_PTRACE (Results 1 – 11 of 11) sorted by relevance
/linux/security/yama/ |
H A D | yama_lsm.c | 371 !ns_capable(__task_cred(child)->user_ns, CAP_SYS_PTRACE)) in yama_ptrace_access_check() 377 if (!ns_capable(__task_cred(child)->user_ns, CAP_SYS_PTRACE)) in yama_ptrace_access_check() 407 if (!has_ns_capability(parent, current_user_ns(), CAP_SYS_PTRACE)) in yama_ptrace_traceme() 442 if (write && !capable(CAP_SYS_PTRACE)) in yama_dointvec_minmax()
|
/linux/Documentation/admin-guide/LSM/ |
H A D | Yama.rst | 34 work), or with ``CAP_SYS_PTRACE`` (i.e. "gdb --pid=PID", and "strace -p PID" 49 The sysctl settings (writable only with ``CAP_SYS_PTRACE``) are: 68 only processes with ``CAP_SYS_PTRACE`` may use ptrace, either with
|
H A D | Smack.rst | 299 ``PTRACE_READ`` is not affected. Can be overridden with ``CAP_SYS_PTRACE``. 303 exception that it can't be overridden with ``CAP_SYS_PTRACE``.
|
/linux/include/uapi/linux/ |
H A D | capability.h | 236 #define CAP_SYS_PTRACE 19 macro
|
/linux/security/apparmor/ |
H A D | task.c | 273 ad->error = aa_capable(cred, &tracer->label, CAP_SYS_PTRACE, in profile_tracer_perm()
|
/linux/kernel/ |
H A D | capability.c | 500 * ptracer_capable - Determine if the ptracer holds CAP_SYS_PTRACE in the namespace in capable_wrt_inode_uidgid() 502 * @ns: The user namespace to search for CAP_SYS_PTRACE in 504 * Return true if the task that is ptracing the current task had CAP_SYS_PTRACE 515 ret = security_capable(cred, ns, CAP_SYS_PTRACE, in ptracer_capable()
|
H A D | ptrace.c | 271 return ns_capable_noaudit(ns, CAP_SYS_PTRACE); in ptrace_has_cap() 272 return ns_capable(ns, CAP_SYS_PTRACE); in ptrace_has_cap()
|
/linux/security/ |
H A D | commoncap.c | 179 if (ns_capable(child_cred->user_ns, CAP_SYS_PTRACE)) in cap_ptrace_access_check() 211 if (has_ns_capability(parent, child_cred->user_ns, CAP_SYS_PTRACE)) in cap_ptrace_traceme()
|
/linux/Documentation/admin-guide/ |
H A D | perf-security.rst | 90 So unprivileged processes provided with CAP_SYS_PTRACE capability are 92 CAP_SYS_PTRACE capability is not required and CAP_PERFMON is enough to
|
/linux/Documentation/admin-guide/mm/ |
H A D | userfaultfd.rst | 68 process needs the CAP_SYS_PTRACE capability, or the system must have 79 the same time (as e.g. granting CAP_SYS_PTRACE would do). Users who have access
|
/linux/fs/ |
H A D | userfaultfd.c | 1946 if ((features & UFFD_FEATURE_EVENT_FORK) && !capable(CAP_SYS_PTRACE)) in userfaultfd_api() 2148 if (capable(CAP_SYS_PTRACE)) in userfaultfd_syscall_allowed()
|