2005-04-17 06:20:36 +08:00
|
|
|
config SECURITY_SELINUX
|
|
|
|
|
bool "NSA SELinux Support"
|
2006-02-08 04:58:51 +08:00
|
|
|
depends on SECURITY_NETWORK && AUDIT && NET && INET
|
[SECMARK]: Add new packet controls to SELinux
Add new per-packet access controls to SELinux, replacing the old
packet controls.
Packets are labeled with the iptables SECMARK and CONNSECMARK targets,
then security policy for the packets is enforced with these controls.
To allow for a smooth transition to the new controls, the old code is
still present, but not active by default. To restore previous
behavior, the old controls may be activated at runtime by writing a
'1' to /selinux/compat_net, and also via the kernel boot parameter
selinux_compat_net. Switching between the network control models
requires the security load_policy permission. The old controls will
probably eventually be removed and any continued use is discouraged.
With this patch, the new secmark controls for SElinux are disabled by
default, so existing behavior is entirely preserved, and the user is
not affected at all.
It also provides a config option to enable the secmark controls by
default (which can always be overridden at boot and runtime). It is
also noted in the kconfig help that the user will need updated
userspace if enabling secmark controls for SELinux and that they'll
probably need the SECMARK and CONNMARK targets, and conntrack protocol
helpers, although such decisions are beyond the scope of kernel
configuration.
Signed-off-by: James Morris <jmorris@namei.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-06-09 15:33:33 +08:00
|
|
|
select NETWORK_SECMARK
|
2005-04-17 06:20:36 +08:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This selects NSA Security-Enhanced Linux (SELinux).
|
|
|
|
|
You will also need a policy configuration and a labeled filesystem.
|
|
|
|
|
You can obtain the policy compiler (checkpolicy), the utility for
|
|
|
|
|
labeling filesystems (setfiles), and an example policy configuration
|
|
|
|
|
from <http://www.nsa.gov/selinux/>.
|
|
|
|
|
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.
|
[SECMARK]: Add new packet controls to SELinux
Add new per-packet access controls to SELinux, replacing the old
packet controls.
Packets are labeled with the iptables SECMARK and CONNSECMARK targets,
then security policy for the packets is enforced with these controls.
To allow for a smooth transition to the new controls, the old code is
still present, but not active by default. To restore previous
behavior, the old controls may be activated at runtime by writing a
'1' to /selinux/compat_net, and also via the kernel boot parameter
selinux_compat_net. Switching between the network control models
requires the security load_policy permission. The old controls will
probably eventually be removed and any continued use is discouraged.
With this patch, the new secmark controls for SElinux are disabled by
default, so existing behavior is entirely preserved, and the user is
not affected at all.
It also provides a config option to enable the secmark controls by
default (which can always be overridden at boot and runtime). It is
also noted in the kconfig help that the user will need updated
userspace if enabling secmark controls for SELinux and that they'll
probably need the SECMARK and CONNMARK targets, and conntrack protocol
helpers, although such decisions are beyond the scope of kernel
configuration.
Signed-off-by: James Morris <jmorris@namei.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-06-09 15:33:33 +08:00
|
|
|
|
|
|
|
|
config SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT
|
|
|
|
|
bool "NSA SELinux enable new secmark network controls by default"
|
|
|
|
|
depends on SECURITY_SELINUX
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option determines whether the new secmark-based network
|
|
|
|
|
controls will be enabled by default. If not, the old internal
|
|
|
|
|
per-packet controls will be enabled by default, preserving
|
|
|
|
|
old behavior.
|
|
|
|
|
|
|
|
|
|
If you enable the new controls, you will need updated
|
|
|
|
|
SELinux userspace libraries, tools and policy. Typically,
|
|
|
|
|
your distribution will provide these and enable the new controls
|
|
|
|
|
in the kernel they also distribute.
|
|
|
|
|
|
2006-10-04 04:34:14 +08:00
|
|
|
Note that this option can be overridden at boot with the
|
[SECMARK]: Add new packet controls to SELinux
Add new per-packet access controls to SELinux, replacing the old
packet controls.
Packets are labeled with the iptables SECMARK and CONNSECMARK targets,
then security policy for the packets is enforced with these controls.
To allow for a smooth transition to the new controls, the old code is
still present, but not active by default. To restore previous
behavior, the old controls may be activated at runtime by writing a
'1' to /selinux/compat_net, and also via the kernel boot parameter
selinux_compat_net. Switching between the network control models
requires the security load_policy permission. The old controls will
probably eventually be removed and any continued use is discouraged.
With this patch, the new secmark controls for SElinux are disabled by
default, so existing behavior is entirely preserved, and the user is
not affected at all.
It also provides a config option to enable the secmark controls by
default (which can always be overridden at boot and runtime). It is
also noted in the kconfig help that the user will need updated
userspace if enabling secmark controls for SELinux and that they'll
probably need the SECMARK and CONNMARK targets, and conntrack protocol
helpers, although such decisions are beyond the scope of kernel
configuration.
Signed-off-by: James Morris <jmorris@namei.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-06-09 15:33:33 +08:00
|
|
|
selinux_compat_net parameter, and after boot via
|
|
|
|
|
/selinux/compat_net. See Documentation/kernel-parameters.txt
|
|
|
|
|
for details on this parameter.
|
|
|
|
|
|
|
|
|
|
If you enable the new network controls, you will likely
|
|
|
|
|
also require the SECMARK and CONNSECMARK targets, as
|
|
|
|
|
well as any conntrack helpers for protocols which you
|
|
|
|
|
wish to control.
|
|
|
|
|
|
2006-10-04 04:36:44 +08:00
|
|
|
If you are unsure what to do here, select N.
|
[SECMARK]: Add new packet controls to SELinux
Add new per-packet access controls to SELinux, replacing the old
packet controls.
Packets are labeled with the iptables SECMARK and CONNSECMARK targets,
then security policy for the packets is enforced with these controls.
To allow for a smooth transition to the new controls, the old code is
still present, but not active by default. To restore previous
behavior, the old controls may be activated at runtime by writing a
'1' to /selinux/compat_net, and also via the kernel boot parameter
selinux_compat_net. Switching between the network control models
requires the security load_policy permission. The old controls will
probably eventually be removed and any continued use is discouraged.
With this patch, the new secmark controls for SElinux are disabled by
default, so existing behavior is entirely preserved, and the user is
not affected at all.
It also provides a config option to enable the secmark controls by
default (which can always be overridden at boot and runtime). It is
also noted in the kconfig help that the user will need updated
userspace if enabling secmark controls for SELinux and that they'll
probably need the SECMARK and CONNMARK targets, and conntrack protocol
helpers, although such decisions are beyond the scope of kernel
configuration.
Signed-off-by: James Morris <jmorris@namei.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-06-09 15:33:33 +08:00
|
|
|
|
2006-09-26 14:31:58 +08:00
|
|
|
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
|
2007-05-09 13:12:20 +08:00
|
|
|
and set the value via the next option. For Fedora Core 5 and later,
|
2006-09-26 14:31:58 +08:00
|
|
|
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
|
2008-01-29 21:38:19 +08:00
|
|
|
range 15 22
|
2006-09-26 14:31:58 +08:00
|
|
|
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.
|
|
|
|
|
|