1 .\" Copyright (c) 2002 by Michael Kerrisk <mtk.manpages@gmail.com>
3 .\" %%%LICENSE_START(VERBATIM)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
25 .\" 6 Aug 2002 - Initial Creation
26 .\" Modified 2003-05-23, Michael Kerrisk, <mtk.manpages@gmail.com>
27 .\" Modified 2004-05-27, Michael Kerrisk, <mtk.manpages@gmail.com>
28 .\" 2004-12-08, mtk Added O_NOATIME for CAP_FOWNER
29 .\" 2005-08-16, mtk, Added CAP_AUDIT_CONTROL and CAP_AUDIT_WRITE
30 .\" 2008-07-15, Serge Hallyn <serue@us.bbm.com>
31 .\" Document file capabilities, per-process capability
32 .\" bounding set, changed semantics for CAP_SETPCAP,
33 .\" and other changes in 2.6.2[45].
34 .\" Add CAP_MAC_ADMIN, CAP_MAC_OVERRIDE, CAP_SETFCAP.
36 .\" Add text describing circumstances in which CAP_SETPCAP
37 .\" (theoretically) permits a thread to change the
38 .\" capability sets of another thread.
39 .\" Add section describing rules for programmatically
40 .\" adjusting thread capability sets.
41 .\" Describe rationale for capability bounding set.
42 .\" Document "securebits" flags.
43 .\" Add text noting that if we set the effective flag for one file
44 .\" capability, then we must also set the effective flag for all
45 .\" other capabilities where the permitted or inheritable bit is set.
46 .\" 2011-09-07, mtk/Serge hallyn: Add CAP_SYSLOG
48 .TH CAPABILITIES 7 2014-04-09 "Linux" "Linux Programmer's Manual"
50 capabilities \- overview of Linux capabilities
52 For the purpose of performing permission checks,
53 traditional UNIX implementations distinguish two categories of processes:
55 processes (whose effective user ID is 0, referred to as superuser or root),
58 processes (whose effective UID is nonzero).
59 Privileged processes bypass all kernel permission checks,
60 while unprivileged processes are subject to full permission
61 checking based on the process's credentials
62 (usually: effective UID, effective GID, and supplementary group list).
64 Starting with kernel 2.2, Linux divides the privileges traditionally
65 associated with superuser into distinct units, known as
67 which can be independently enabled and disabled.
68 Capabilities are a per-thread attribute.
71 The following list shows the capabilities implemented on Linux,
72 and the operations or behaviors that each capability permits:
74 .BR CAP_AUDIT_CONTROL " (since Linux 2.6.11)"
75 Enable and disable kernel auditing; change auditing filter rules;
76 retrieve auditing status and filtering rules.
78 .BR CAP_AUDIT_WRITE " (since Linux 2.6.11)"
79 Write records to kernel auditing log.
81 .BR CAP_BLOCK_SUSPEND " (since Linux 3.5)"
82 Employ features that can block system suspend
85 .IR /proc/sys/wake_lock ).
88 Make arbitrary changes to file UIDs and GIDs (see
92 Bypass file read, write, and execute permission checks.
93 (DAC is an abbreviation of "discretionary access control".)
95 .B CAP_DAC_READ_SEARCH
99 Bypass file read permission checks and
100 directory read and execute permission checks;
103 .BR open_by_handle_at (2).
112 Bypass permission checks on operations that normally
113 require the filesystem UID of the process to match the UID of
117 excluding those operations covered by
120 .BR CAP_DAC_READ_SEARCH ;
122 set extended file attributes (see
126 set Access Control Lists (ACLs) on arbitrary files;
128 ignore directory sticky bit on file deletion;
132 for arbitrary files in
140 Don't clear set-user-ID and set-group-ID permission
141 bits when a file is modified;
142 set the set-group-ID bit for a file whose GID does not match
143 the filesystem or any of the supplementary GIDs of the calling process.
146 .\" FIXME As at Linux 3.2, there are some strange uses of this capability
147 .\" in other places; they probably should be replaced with something else.
155 Bypass permission checks for operations on System V IPC objects.
158 Bypass permission checks for sending signals (see
160 This includes use of the
164 .\" FIXME CAP_KILL also has an effect for threads + setting child
165 .\" termination signal to other than SIGCHLD: without this
166 .\" capability, the termination signal reverts to SIGCHLD
167 .\" if the child does an exec(). What is the rationale
170 .BR CAP_LEASE " (since Linux 2.4)"
171 Establish leases on arbitrary files (see
174 .B CAP_LINUX_IMMUTABLE
179 .\" These attributes are now available on ext2, ext3, Reiserfs, XFS, JFS
183 .BR CAP_MAC_ADMIN " (since Linux 2.6.25)"
184 Override Mandatory Access Control (MAC).
185 Implemented for the Smack Linux Security Module (LSM).
187 .BR CAP_MAC_OVERRIDE " (since Linux 2.6.25)"
188 Allow MAC configuration or state changes.
189 Implemented for the Smack LSM.
191 .BR CAP_MKNOD " (since Linux 2.4)"
192 Create special files using
196 Perform various network-related operations:
200 interface configuration;
202 administration of IP firewall, masquerading, and accounting;
204 modify routing tables;
206 bind to any address for transparent proxying;
208 set type-of-service (TOS)
210 clear driver statistics;
212 set promiscuous mode;
214 enabling multicasting;
218 to set the following socket options:
222 (for a priority outside the range 0 to 6),
229 .B CAP_NET_BIND_SERVICE
230 Bind a socket to Internet domain privileged ports
231 (port numbers less than 1024).
234 (Unused) Make socket broadcasts, and listen to multicasts.
240 use RAW and PACKET sockets;
242 bind to any address for transparent proxying.
245 .\" Also various IP options and setsockopt(SO_BINDTODEVICE)
248 Make arbitrary manipulations of process GIDs and supplementary GID list;
249 forge GID when passing socket credentials via UNIX domain sockets.
251 .BR CAP_SETFCAP " (since Linux 2.6.24)"
252 Set file capabilities.
255 If file capabilities are not supported:
256 grant or remove any capability in the
257 caller's permitted capability set to or from any other process.
260 is not available when the kernel is configured to support
261 file capabilities, since
263 has entirely different semantics for such kernels.)
265 If file capabilities are supported:
266 add any capability from the calling thread's bounding set
267 to its inheritable set;
268 drop capabilities from the bounding set (via
270 .BR PR_CAPBSET_DROP );
276 Make arbitrary manipulations of process UIDs
281 make forged UID when passing socket credentials via UNIX domain sockets.
282 .\" FIXME CAP_SETUID also an effect in exec(); document this.
288 Perform a range of system administration operations including:
296 .BR setdomainname (2);
300 operations (since Linux 2.6.37,
302 should be used to permit such operations);
313 operations on arbitrary System V IPC objects;
315 perform operations on
319 Extended Attributes (see
323 .BR lookup_dcookie (2);
329 and (before Linux 2.6.25)
331 I/O scheduling classes;
333 forge UID when passing socket credentials;
336 .IR /proc/sys/fs/file-max ,
337 the system-wide limit on the number of open files,
338 in system calls that open files (e.g.,
346 flags that create new namespaces with
352 .BR perf_event_open (2);
362 .BR fanotify_init (2);
379 to insert characters into the input queue of a terminal other than
380 the caller's controlling terminal.
390 perform various privileged block-device
394 perform various privileged filesystem
398 perform administrative operations on many device drivers.
413 Load and unload kernel modules
417 .BR delete_module (2));
418 in kernels before 2.6.25:
419 drop capabilities from the system-wide capability bounding set.
425 Raise process nice value
428 and change the nice value for arbitrary processes;
430 set real-time scheduling policies for calling process,
431 and set scheduling policies and priorities for arbitrary processes
432 .RB ( sched_setscheduler (2),
433 .BR sched_setparam (2));
435 set CPU affinity for arbitrary processes
436 .RB ( sched_setaffinity (2));
438 set I/O scheduling class and priority for arbitrary processes
439 .RB ( ioprio_set (2));
442 .BR migrate_pages (2)
443 to arbitrary processes and allow processes
444 to be migrated to arbitrary nodes;
445 .\" FIXME CAP_SYS_NICE also has the following effect for
446 .\" migrate_pages(2):
447 .\" do_migrate_pages(mm, &old, &new,
448 .\" capable(CAP_SYS_NICE) ? MPOL_MF_MOVE_ALL : MPOL_MF_MOVE);
452 to arbitrary processes;
468 Trace arbitrary processes using
471 .BR get_robust_list (2)
472 to arbitrary processes;
473 inspect processes using
480 Perform I/O port operations
493 open devices for accessing x86 model-specific registers (MSRs, see
497 .IR /proc/sys/vm/mmap_min_addr ;
499 create memory mappings at addresses below the value specified by
500 .IR /proc/sys/vm/mmap_min_addr ;
510 perform various SCSI device commands;
512 perform certain operations on
518 perform a range of device-specific operations on other devices.
526 Use reserved space on ext2 filesystems;
530 calls controlling ext3 journaling;
532 override disk quota limits;
534 increase resource limits (see
541 override maximum number of consoles on console allocation;
543 override maximum number of keymaps;
545 allow more than 64hz interrupts from the real-time clock;
549 limit for a System V message queue above the limit in
550 .I /proc/sys/kernel/msgmnb
557 .I /proc/sys/fs/pipe-size-max
558 limit when setting the capacity of a pipe using the
565 to increase the capacity of a pipe above the limit specified by
566 .IR /proc/sys/fs/pipe-max-size ;
569 .I /proc/sys/fs/mqueue/queues_max
570 limit when creating POSIX message queues (see
571 .BR mq_overview (7));
579 .IR /proc/PID/oom_score_adj
580 to a value lower than the value last set by a process with
581 .BR CAP_SYS_RESOURCE .
587 .RB ( settimeofday (2),
590 set real-time (hardware) clock.
592 .B CAP_SYS_TTY_CONFIG
595 employ various privileged
597 operations on virtual terminals.
599 .BR CAP_SYSLOG " (since Linux 2.6.37)"
606 for information on which operations require privilege.
608 View kernel addresses exposed via
610 and other interfaces when
611 .IR /proc/sys/kernel/kptr_restrict
613 (See the discussion of the
618 .BR CAP_WAKE_ALARM " (since Linux 3.0)"
619 Trigger something that will wake up the system (set
620 .B CLOCK_REALTIME_ALARM
622 .B CLOCK_BOOTTIME_ALARM
625 .SS Past and current implementation
626 A full implementation of capabilities requires that:
628 For all privileged operations,
629 the kernel must check whether the thread has the required
630 capability in its effective set.
632 The kernel must provide system calls allowing a thread's capability sets to
633 be changed and retrieved.
635 The filesystem must support attaching capabilities to an executable file,
636 so that a process gains those capabilities when the file is executed.
638 Before kernel 2.6.24, only the first two of these requirements are met;
639 since kernel 2.6.24, all three requirements are met.
641 .SS Thread capability sets
642 Each thread has three capability sets containing zero or more
643 of the above capabilities:
646 This is a limiting superset for the effective
647 capabilities that the thread may assume.
648 It is also a limiting superset for the capabilities that
649 may be added to the inheritable set by a thread that does not have the
651 capability in its effective set.
653 If a thread drops a capability from its permitted set,
654 it can never reacquire that capability (unless it
656 either a set-user-ID-root program, or
657 a program whose associated file capabilities grant that capability).
660 This is a set of capabilities preserved across an
662 It provides a mechanism for a process to assign capabilities
663 to the permitted set of the new program during an
667 This is the set of capabilities used by the kernel to
668 perform permission checks for the thread.
672 inherits copies of its parent's capability sets.
673 See below for a discussion of the treatment of capabilities during
678 a thread may manipulate its own capability sets (see below).
680 Since Linux 3.2, the file
681 .I /proc/sys/kernel/cap_last_cap
682 .\" commit 73efc0394e148d0e15583e13712637831f926720
683 exposes the numerical value of the highest capability
684 supported by the running kernel;
685 this can be used to determine the highest bit
686 that may be set in a capability set.
688 .SS File capabilities
689 Since kernel 2.6.24, the kernel supports
690 associating capability sets with an executable file using
692 The file capability sets are stored in an extended attribute (see
695 .IR "security.capability" .
696 Writing to this extended attribute requires the
699 The file capability sets,
700 in conjunction with the capability sets of the thread,
701 determine the capabilities of a thread after an
704 The three file capability sets are:
706 .IR Permitted " (formerly known as " forced ):
707 These capabilities are automatically permitted to the thread,
708 regardless of the thread's inheritable capabilities.
710 .IR Inheritable " (formerly known as " allowed ):
711 This set is ANDed with the thread's inheritable set to determine which
712 inheritable capabilities are enabled in the permitted set of
717 This is not a set, but rather just a single bit.
718 If this bit is set, then during an
720 all of the new permitted capabilities for the thread are
721 also raised in the effective set.
722 If this bit is not set, then after an
724 none of the new permitted capabilities is in the new effective set.
726 Enabling the file effective capability bit implies
727 that any file permitted or inheritable capability that causes a
728 thread to acquire the corresponding permitted capability during an
730 (see the transformation rules described below) will also acquire that
731 capability in its effective set.
732 Therefore, when assigning capabilities to a file
734 .BR cap_set_file (3),
736 if we specify the effective flag as being enabled for any capability,
737 then the effective flag must also be specified as enabled
738 for all other capabilities for which the corresponding permitted or
739 inheritable flags is enabled.
741 .SS Transformation of capabilities during execve()
745 the kernel calculates the new capabilities of
746 the process using the following algorithm:
750 P'(permitted) = (P(inheritable) & F(inheritable)) |
751 (F(permitted) & cap_bset)
753 P'(effective) = F(effective) ? P'(permitted) : 0
755 P'(inheritable) = P(inheritable) [i.e., unchanged]
762 denotes the value of a thread capability set before the
765 denotes the value of a capability set after the
768 denotes a file capability set
770 is the value of the capability bounding set (described below).
773 .SS Capabilities and execution of programs by root
774 In order to provide an all-powerful
776 using capability sets, during an
779 If a set-user-ID-root program is being executed,
780 or the real user ID of the process is 0 (root)
781 then the file inheritable and permitted sets are defined to be all ones
782 (i.e., all capabilities enabled).
784 If a set-user-ID-root program is being executed,
785 then the file effective bit is defined to be one (enabled).
787 The upshot of the above rules,
788 combined with the capabilities transformations described above,
789 is that when a process
791 a set-user-ID-root program, or when a process with an effective UID of 0
794 it gains all capabilities in its permitted and effective capability sets,
795 except those masked out by the capability bounding set.
796 .\" If a process with real UID 0, and nonzero effective UID does an
797 .\" exec(), then it gets all capabilities in its
798 .\" permitted set, and no effective capabilities
799 This provides semantics that are the same as those provided by
800 traditional UNIX systems.
801 .SS Capability bounding set
802 The capability bounding set is a security mechanism that can be used
803 to limit the capabilities that can be gained during an
805 The bounding set is used in the following ways:
809 the capability bounding set is ANDed with the file permitted
810 capability set, and the result of this operation is assigned to the
811 thread's permitted capability set.
812 The capability bounding set thus places a limit on the permitted
813 capabilities that may be granted by an executable file.
816 The capability bounding set acts as a limiting superset for
817 the capabilities that a thread can add to its inheritable set using
819 This means that if a capability is not in the bounding set,
820 then a thread can't add this capability to its
821 inheritable set, even if it was in its permitted capabilities,
822 and thereby cannot have this capability preserved in its
823 permitted set when it
825 a file that has the capability in its inheritable set.
827 Note that the bounding set masks the file permitted capabilities,
828 but not the inherited capabilities.
829 If a thread maintains a capability in its inherited set
830 that is not in its bounding set,
831 then it can still gain that capability in its permitted set
832 by executing a file that has the capability in its inherited set.
834 Depending on the kernel version, the capability bounding set is either
835 a system-wide attribute, or a per-process attribute.
837 .B "Capability bounding set prior to Linux 2.6.25"
839 In kernels before 2.6.25, the capability bounding set is a system-wide
840 attribute that affects all threads on the system.
841 The bounding set is accessible via the file
842 .IR /proc/sys/kernel/cap-bound .
843 (Confusingly, this bit mask parameter is expressed as a
844 signed decimal number in
845 .IR /proc/sys/kernel/cap-bound .)
849 process may set capabilities in the capability bounding set;
850 other than that, the superuser (more precisely: programs with the
852 capability) may only clear capabilities from this set.
854 On a standard system the capability bounding set always masks out the
857 To remove this restriction (dangerous!), modify the definition of
860 .I include/linux/capability.h
861 and rebuild the kernel.
863 The system-wide capability bounding set feature was added
864 to Linux starting with kernel version 2.2.11.
867 .B "Capability bounding set from Linux 2.6.25 onward"
869 From Linux 2.6.25, the
870 .I "capability bounding set"
871 is a per-thread attribute.
872 (There is no longer a system-wide capability bounding set.)
874 The bounding set is inherited at
876 from the thread's parent, and is preserved across an
879 A thread may remove capabilities from its capability bounding set using the
882 operation, provided it has the
885 Once a capability has been dropped from the bounding set,
886 it cannot be restored to that set.
887 A thread can determine if a capability is in its bounding set using the
892 Removing capabilities from the bounding set is supported only if file
893 capabilities are compiled into the kernel.
894 In kernels before Linux 2.6.33,
895 file capabilities were an optional feature configurable via the
896 CONFIG_SECURITY_FILE_CAPABILITIES
898 Since Linux 2.6.33, the configuration option has been removed
899 and file capabilities are always part of the kernel.
900 When file capabilities are compiled into the kernel, the
902 process (the ancestor of all processes) begins with a full bounding set.
903 If file capabilities are not compiled into the kernel, then
905 begins with a full bounding set minus
907 because this capability has a different meaning when there are
908 no file capabilities.
910 Removing a capability from the bounding set does not remove it
911 from the thread's inherited set.
912 However it does prevent the capability from being added
913 back into the thread's inherited set in the future.
916 .SS Effect of user ID changes on capabilities
917 To preserve the traditional semantics for transitions between
918 0 and nonzero user IDs,
919 the kernel makes the following changes to a thread's capability
920 sets on changes to the thread's real, effective, saved set,
921 and filesystem user IDs (using
926 If one or more of the real, effective or saved set user IDs
927 was previously 0, and as a result of the UID changes all of these IDs
928 have a nonzero value,
929 then all capabilities are cleared from the permitted and effective
932 If the effective user ID is changed from 0 to nonzero,
933 then all capabilities are cleared from the effective set.
935 If the effective user ID is changed from nonzero to 0,
936 then the permitted set is copied to the effective set.
938 If the filesystem user ID is changed from 0 to nonzero (see
940 then the following capabilities are cleared from the effective set:
942 .BR CAP_DAC_OVERRIDE ,
943 .BR CAP_DAC_READ_SEARCH ,
946 .B CAP_LINUX_IMMUTABLE
947 (since Linux 2.6.30),
948 .BR CAP_MAC_OVERRIDE ,
951 (since Linux 2.6.30).
952 If the filesystem UID is changed from nonzero to 0,
953 then any of these capabilities that are enabled in the permitted set
954 are enabled in the effective set.
956 If a thread that has a 0 value for one or more of its user IDs wants
957 to prevent its permitted capability set being cleared when it resets
958 all of its user IDs to nonzero values, it can do so using the
963 .SS Programmatically adjusting capability sets
964 A thread can retrieve and change its capability sets using the
972 .BR cap_set_proc (3),
976 is preferred for this purpose.
977 The following rules govern changes to the thread capability sets:
979 If the caller does not have the
982 the new inheritable set must be a subset of the combination
983 of the existing inheritable and permitted sets.
986 The new inheritable set must be a subset of the combination of the
987 existing inheritable set and the capability bounding set.
989 The new permitted set must be a subset of the existing permitted set
990 (i.e., it is not possible to acquire permitted capabilities
991 that the thread does not currently have).
993 The new effective set must be a subset of the new permitted set.
994 .SS The securebits flags: establishing a capabilities-only environment
995 .\" For some background:
996 .\" see http://lwn.net/Articles/280279/ and
997 .\" http://article.gmane.org/gmane.linux.kernel.lsm/5476/
998 Starting with kernel 2.6.26,
999 and with a kernel in which file capabilities are enabled,
1000 Linux implements a set of per-thread
1002 flags that can be used to disable special handling of capabilities for UID 0
1004 These flags are as follows:
1007 Setting this flag allows a thread that has one or more 0 UIDs to retain
1008 its capabilities when it switches all of its UIDs to a nonzero value.
1009 If this flag is not set,
1010 then such a UID switch causes the thread to lose all capabilities.
1011 This flag is always cleared on an
1013 (This flag provides the same functionality as the older
1018 .B SECBIT_NO_SETUID_FIXUP
1019 Setting this flag stops the kernel from adjusting capability sets when
1020 the threads's effective and filesystem UIDs are switched between
1021 zero and nonzero values.
1023 .IR "Effect of User ID Changes on Capabilities" .)
1026 If this bit is set, then the kernel does not grant capabilities
1027 when a set-user-ID-root program is executed, or when a process with
1028 an effective or real UID of 0 calls
1031 .IR "Capabilities and execution of programs by root" .)
1033 Each of the above "base" flags has a companion "locked" flag.
1034 Setting any of the "locked" flags is irreversible,
1035 and has the effect of preventing further changes to the
1036 corresponding "base" flag.
1037 The locked flags are:
1038 .BR SECBIT_KEEP_CAPS_LOCKED ,
1039 .BR SECBIT_NO_SETUID_FIXUP_LOCKED ,
1041 .BR SECBIT_NOROOT_LOCKED .
1045 flags can be modified and retrieved using the
1047 .B PR_SET_SECUREBITS
1049 .B PR_GET_SECUREBITS
1053 capability is required to modify the flags.
1057 flags are inherited by child processes.
1060 all of the flags are preserved, except
1062 which is always cleared.
1064 An application can use the following call to lock itself,
1065 and all of its descendants,
1066 into an environment where the only way of gaining capabilities
1067 is by executing a program with associated file capabilities:
1071 prctl(PR_SET_SECUREBITS,
1072 SECBIT_KEEP_CAPS_LOCKED |
1073 SECBIT_NO_SETUID_FIXUP |
1074 SECBIT_NO_SETUID_FIXUP_LOCKED |
1076 SECBIT_NOROOT_LOCKED);
1081 No standards govern capabilities, but the Linux capability implementation
1082 is based on the withdrawn POSIX.1e draft standard; see
1083 .UR http://wt.tuxomania.net\:/publications\:/posix.1e/
1086 Since kernel 2.5.27, capabilities are an optional kernel component,
1087 and can be enabled/disabled via the CONFIG_SECURITY_CAPABILITIES
1088 kernel configuration option.
1091 .I /proc/PID/task/TID/status
1092 file can be used to view the capability sets of a thread.
1095 file shows the capability sets of a process's main thread.
1096 Before Linux 3.8, nonexistent capabilities were shown as being
1097 enabled (1) in these sets.
1099 .\" 7b9a7ec565505699f503b4fcf61500dceb36e744
1100 all nonexistent capabilities (above
1102 are shown as disabled (0).
1106 package provides a suite of routines for setting and
1107 getting capabilities that is more comfortable and less likely
1108 to change than the interface provided by
1112 This package also provides the
1119 .UR http://www.kernel.org\:/pub\:/linux\:/libs\:/security\:/linux-privs
1122 Before kernel 2.6.24, and since kernel 2.6.24 if
1123 file capabilities are not enabled, a thread with the
1125 capability can manipulate the capabilities of threads other than itself.
1126 However, this is only theoretically possible,
1127 since no thread ever has
1129 in either of these cases:
1131 In the pre-2.6.25 implementation the system-wide capability bounding set,
1132 .IR /proc/sys/kernel/cap-bound ,
1133 always masks out this capability, and this can not be changed
1134 without modifying the kernel source and rebuilding.
1136 If file capabilities are disabled in the current implementation, then
1138 starts out with this capability removed from its per-process bounding
1139 set, and that bounding set is inherited by all other processes
1140 created on the system.
1147 .BR cap_copy_ext (3),
1148 .BR cap_from_text (3),
1149 .BR cap_get_file (3),
1150 .BR cap_get_proc (3),
1155 .BR credentials (7),
1160 .I include/linux/capability.h
1161 in the Linux kernel source tree
1163 This page is part of release 3.65 of the Linux
1166 A description of the project,
1167 and information about reporting bugs,
1169 \%http://www.kernel.org/doc/man\-pages/.