blob: beb86b500adffd406e65b26d0cf9abeab3891703 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Security configuration
3#
4
5menu "Security options"
6
David Howellsf0894942012-05-11 10:56:56 +01007source security/keys/Kconfig
Linus Torvalds1da177e2005-04-16 15:20:36 -07008
Dan Rosenbergeaf06b22010-11-11 14:05:18 -08009config SECURITY_DMESG_RESTRICT
10 bool "Restrict unprivileged access to the kernel syslog"
11 default n
12 help
13 This enforces restrictions on unprivileged users reading the kernel
14 syslog via dmesg(8).
15
16 If this option is not selected, no restrictions will be enforced
17 unless the dmesg_restrict sysctl is explicitly set to (1).
18
19 If you are unsure how to answer this question, answer N.
20
Linus Torvalds1da177e2005-04-16 15:20:36 -070021config SECURITY
22 bool "Enable different security models"
Adrian Bunk2c405792005-08-22 18:20:50 +020023 depends on SYSFS
Linus Torvalds1da177e2005-04-16 15:20:36 -070024 help
25 This allows you to choose different security modules to be
26 configured into your kernel.
27
28 If this option is not selected, the default Linux security
29 model will be used.
30
31 If you are unsure how to answer this question, answer N.
32
Eric Parisda318942008-08-22 11:35:57 -040033config SECURITYFS
34 bool "Enable the securityfs filesystem"
35 help
36 This will build the securityfs filesystem. It is currently used by
Mimi Zohar3323eec2009-02-04 09:06:58 -050037 the TPM bios character driver and IMA, an integrity provider. It is
38 not used by SELinux or SMACK.
Eric Parisda318942008-08-22 11:35:57 -040039
40 If you are unsure how to answer this question, answer N.
41
Linus Torvalds1da177e2005-04-16 15:20:36 -070042config SECURITY_NETWORK
43 bool "Socket and Networking Security Hooks"
44 depends on SECURITY
45 help
46 This enables the socket and networking security hooks.
47 If enabled, a security module can use these hooks to
48 implement socket and networking access controls.
49 If you are unsure how to answer this question, answer N.
50
Trent Jaegerdf718372005-12-13 23:12:27 -080051config SECURITY_NETWORK_XFRM
52 bool "XFRM (IPSec) Networking Security Hooks"
53 depends on XFRM && SECURITY_NETWORK
54 help
55 This enables the XFRM (IPSec) networking security hooks.
56 If enabled, a security module can use these hooks to
57 implement per-packet access controls based on labels
58 derived from IPSec policy. Non-IPSec communications are
59 designated as unlabelled, and only sockets authorized
60 to communicate unlabelled data can send without using
61 IPSec.
62 If you are unsure how to answer this question, answer N.
63
Kentaro Takedabe6d3e52008-12-17 13:24:15 +090064config SECURITY_PATH
65 bool "Security hooks for pathname based access control"
66 depends on SECURITY
67 help
68 This enables the security hooks for pathname based access control.
69 If enabled, a security module can use these hooks to
70 implement pathname based access controls.
71 If you are unsure how to answer this question, answer N.
72
Joseph Cihula31625342009-06-30 19:30:59 -070073config INTEL_TXT
74 bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
Shane Wang69575d32009-09-01 18:25:07 -070075 depends on HAVE_INTEL_TXT
Joseph Cihula31625342009-06-30 19:30:59 -070076 help
77 This option enables support for booting the kernel with the
78 Trusted Boot (tboot) module. This will utilize
79 Intel(R) Trusted Execution Technology to perform a measured launch
80 of the kernel. If the system does not support Intel(R) TXT, this
81 will have no effect.
82
Arnaldo Carvalho de Melo3c556e42009-08-12 12:00:40 -030083 Intel TXT will provide higher assurance of system configuration and
Joseph Cihula31625342009-06-30 19:30:59 -070084 initial state as well as data reset protection. This is used to
85 create a robust initial kernel measurement and verification, which
86 helps to ensure that kernel security mechanisms are functioning
87 correctly. This level of protection requires a root of trust outside
88 of the kernel itself.
89
90 Intel TXT also helps solve real end user concerns about having
91 confidence that their hardware is running the VMM or kernel that
Arnaldo Carvalho de Melo3c556e42009-08-12 12:00:40 -030092 it was configured with, especially since they may be responsible for
Joseph Cihula31625342009-06-30 19:30:59 -070093 providing such assurances to VMs and services running on it.
94
95 See <http://www.intel.com/technology/security/> for more information
96 about Intel(R) TXT.
97 See <http://tboot.sourceforge.net> for more information about tboot.
98 See Documentation/intel_txt.txt for a description of how to enable
99 Intel TXT support in a kernel boot.
100
101 If you are unsure as to whether this is required, answer N.
102
Eric Paris788084a2009-07-31 12:54:11 -0400103config LSM_MMAP_MIN_ADDR
Andreas Schwab024e6cb2009-08-18 22:14:29 +0200104 int "Low address space for LSM to protect from user allocation"
Eric Paris788084a2009-07-31 12:54:11 -0400105 depends on SECURITY && SECURITY_SELINUX
Colin Cross530b0992014-02-04 02:15:32 +0000106 default 32768 if ARM || (ARM64 && COMPAT)
Dave Jonesa58578e2009-08-18 13:47:37 -0400107 default 65536
Eric Paris788084a2009-07-31 12:54:11 -0400108 help
109 This is the portion of low virtual memory which should be protected
110 from userspace allocation. Keeping a user from writing to low pages
111 can help reduce the impact of kernel NULL pointer bugs.
112
113 For most ia64, ppc64 and x86 users with lots of address space
114 a value of 65536 is reasonable and should cause no problems.
115 On arm and other archs it should not be higher than 32768.
116 Programs which use vm86 functionality or have some need to map
117 this low address space will need the permission specific to the
118 systems running LSM.
119
Linus Torvalds1da177e2005-04-16 15:20:36 -0700120source security/selinux/Kconfig
Casey Schauflere114e472008-02-04 22:29:50 -0800121source security/smack/Kconfig
Kentaro Takeda00d7d6f2009-02-05 17:18:17 +0900122source security/tomoyo/Kconfig
John Johansenf9ad1af2010-07-29 14:48:08 -0700123source security/apparmor/Kconfig
Kees Cook2d514482011-12-21 12:17:04 -0800124source security/yama/Kconfig
Linus Torvalds1da177e2005-04-16 15:20:36 -0700125
Mimi Zoharf381c272011-03-09 14:13:22 -0500126source security/integrity/Kconfig
Mimi Zohar3323eec2009-02-04 09:06:58 -0500127
John Johansen6e65f922009-11-05 17:03:20 -0800128choice
129 prompt "Default security module"
130 default DEFAULT_SECURITY_SELINUX if SECURITY_SELINUX
131 default DEFAULT_SECURITY_SMACK if SECURITY_SMACK
132 default DEFAULT_SECURITY_TOMOYO if SECURITY_TOMOYO
John Johansenf9ad1af2010-07-29 14:48:08 -0700133 default DEFAULT_SECURITY_APPARMOR if SECURITY_APPARMOR
Kees Cook2d514482011-12-21 12:17:04 -0800134 default DEFAULT_SECURITY_YAMA if SECURITY_YAMA
John Johansen6e65f922009-11-05 17:03:20 -0800135 default DEFAULT_SECURITY_DAC
136
137 help
138 Select the security module that will be used by default if the
139 kernel parameter security= is not specified.
140
141 config DEFAULT_SECURITY_SELINUX
142 bool "SELinux" if SECURITY_SELINUX=y
143
144 config DEFAULT_SECURITY_SMACK
145 bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y
146
147 config DEFAULT_SECURITY_TOMOYO
148 bool "TOMOYO" if SECURITY_TOMOYO=y
149
John Johansenf9ad1af2010-07-29 14:48:08 -0700150 config DEFAULT_SECURITY_APPARMOR
151 bool "AppArmor" if SECURITY_APPARMOR=y
152
Kees Cook2d514482011-12-21 12:17:04 -0800153 config DEFAULT_SECURITY_YAMA
154 bool "Yama" if SECURITY_YAMA=y
155
John Johansen6e65f922009-11-05 17:03:20 -0800156 config DEFAULT_SECURITY_DAC
157 bool "Unix Discretionary Access Controls"
158
159endchoice
160
161config DEFAULT_SECURITY
162 string
163 default "selinux" if DEFAULT_SECURITY_SELINUX
164 default "smack" if DEFAULT_SECURITY_SMACK
165 default "tomoyo" if DEFAULT_SECURITY_TOMOYO
John Johansenf9ad1af2010-07-29 14:48:08 -0700166 default "apparmor" if DEFAULT_SECURITY_APPARMOR
Kees Cook2d514482011-12-21 12:17:04 -0800167 default "yama" if DEFAULT_SECURITY_YAMA
John Johansen6e65f922009-11-05 17:03:20 -0800168 default "" if DEFAULT_SECURITY_DAC
169
Linus Torvalds1da177e2005-04-16 15:20:36 -0700170endmenu
171