Blame view

security/selinux/Kconfig 5.1 KB
1da177e4c   Linus Torvalds   Linux-2.6.12-rc2
1
2
  config SECURITY_SELINUX
  	bool "NSA SELinux Support"
99f6d61bd   Stephen Smalley   [PATCH] selinux: ...
3
  	depends on SECURITY_NETWORK && AUDIT && NET && INET
4e5ab4cb8   James Morris   [SECMARK]: Add ne...
4
  	select NETWORK_SECMARK
1da177e4c   Linus Torvalds   Linux-2.6.12-rc2
5
6
7
8
  	default n
  	help
  	  This selects NSA Security-Enhanced Linux (SELinux).
  	  You will also need a policy configuration and a labeled filesystem.
1da177e4c   Linus Torvalds   Linux-2.6.12-rc2
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
  	  If you are unsure how to answer this question, answer N.
  
  config SECURITY_SELINUX_BOOTPARAM
  	bool "NSA SELinux boot parameter"
  	depends on SECURITY_SELINUX
  	default n
  	help
  	  This option adds a kernel parameter 'selinux', which allows SELinux
  	  to be disabled at boot.  If this option is selected, SELinux
  	  functionality can be disabled with selinux=0 on the kernel
  	  command line.  The purpose of this option is to allow a single
  	  kernel image to be distributed with SELinux built in, but not
  	  necessarily enabled.
  
  	  If you are unsure how to answer this question, answer N.
  
  config SECURITY_SELINUX_BOOTPARAM_VALUE
  	int "NSA SELinux boot parameter default value"
  	depends on SECURITY_SELINUX_BOOTPARAM
  	range 0 1
  	default 1
  	help
  	  This option sets the default value for the kernel parameter
  	  'selinux', which allows SELinux to be disabled at boot.  If this
  	  option is set to 0 (zero), the SELinux kernel parameter will
  	  default to 0, disabling SELinux at bootup.  If this option is
  	  set to 1 (one), the SELinux kernel parameter will default to 1,
  	  enabling SELinux at bootup.
  
  	  If you are unsure how to answer this question, answer 1.
  
  config SECURITY_SELINUX_DISABLE
  	bool "NSA SELinux runtime disable"
  	depends on SECURITY_SELINUX
  	default n
  	help
  	  This option enables writing to a selinuxfs node 'disable', which
  	  allows SELinux to be disabled at runtime prior to the policy load.
  	  SELinux will then remain disabled until the next boot.
  	  This option is similar to the selinux=0 boot parameter, but is to
  	  support runtime disabling of SELinux, e.g. from /sbin/init, for
  	  portability across platforms where boot parameters are difficult
  	  to employ.
  
  	  If you are unsure how to answer this question, answer N.
  
  config SECURITY_SELINUX_DEVELOP
  	bool "NSA SELinux Development Support"
  	depends on SECURITY_SELINUX
  	default y
  	help
  	  This enables the development support option of NSA SELinux,
  	  which is useful for experimenting with SELinux and developing
  	  policies.  If unsure, say Y.  With this option enabled, the
  	  kernel will start in permissive mode (log everything, deny nothing)
  	  unless you specify enforcing=1 on the kernel command line.  You
  	  can interactively toggle the kernel between enforcing mode and
  	  permissive mode (if permitted by the policy) via /selinux/enforce.
  
  config SECURITY_SELINUX_AVC_STATS
  	bool "NSA SELinux AVC Statistics"
  	depends on SECURITY_SELINUX
  	default y
  	help
  	  This option collects access vector cache statistics to
  	  /selinux/avc/cache_stats, which may be monitored via
  	  tools such as avcstat.
  
  config SECURITY_SELINUX_CHECKREQPROT_VALUE
  	int "NSA SELinux checkreqprot default value"
  	depends on SECURITY_SELINUX
  	range 0 1
  	default 1
  	help
  	  This option sets the default value for the 'checkreqprot' flag
  	  that determines whether SELinux checks the protection requested
  	  by the application or the protection that will be applied by the
  	  kernel (including any implied execute for read-implies-exec) for
  	  mmap and mprotect calls.  If this option is set to 0 (zero),
  	  SELinux will default to checking the protection that will be applied
  	  by the kernel.  If this option is set to 1 (one), SELinux will
  	  default to checking the protection requested by the application.
  	  The checkreqprot flag may be changed from the default via the
  	  'checkreqprot=' boot parameter.  It may also be changed at runtime
  	  via /selinux/checkreqprot if authorized by policy.
  
  	  If you are unsure how to answer this question, answer 1.
4e5ab4cb8   James Morris   [SECMARK]: Add ne...
96

016b9bdb8   Stephen Smalley   [PATCH] selinux: ...
97
98
99
100
101
102
103
104
105
106
107
108
109
  config SECURITY_SELINUX_POLICYDB_VERSION_MAX
  	bool "NSA SELinux maximum supported policy format version"
  	depends on SECURITY_SELINUX
  	default n
  	help
  	  This option enables the maximum policy format version supported
  	  by SELinux to be set to a particular value.  This value is reported
  	  to userspace via /selinux/policyvers and used at policy load time.
  	  It can be adjusted downward to support legacy userland (init) that
  	  does not correctly handle kernels that support newer policy versions.
  
  	  Examples:
  	  For the Fedora Core 3 or 4 Linux distributions, enable this option
3dde6ad8f   David Sterba   Fix trivial typos...
110
  	  and set the value via the next option. For Fedora Core 5 and later,
016b9bdb8   Stephen Smalley   [PATCH] selinux: ...
111
112
113
114
115
116
117
  	  do not enable this option.
  
  	  If you are unsure how to answer this question, answer N.
  
  config SECURITY_SELINUX_POLICYDB_VERSION_MAX_VALUE
  	int "NSA SELinux maximum supported policy format version value"
  	depends on SECURITY_SELINUX_POLICYDB_VERSION_MAX
64dbf0747   Eric Paris   selinux: introduc...
118
  	range 15 23
016b9bdb8   Stephen Smalley   [PATCH] selinux: ...
119
120
121
122
123
124
125
126
127
128
129
130
131
132
  	default 19
  	help
  	  This option sets the value for the maximum policy format version
  	  supported by SELinux.
  
  	  Examples:
  	  For Fedora Core 3, use 18.
  	  For Fedora Core 4, use 19.
  
  	  If you are unsure how to answer this question, look for the
  	  policy format version supported by your policy toolchain, by
  	  running 'checkpolicy -V'. Or look at what policy you have
  	  installed under /etc/selinux/$SELINUXTYPE/policy, where
  	  SELINUXTYPE is defined in your /etc/selinux/config.