2005-04-16 15:20:36 -07:00
|
|
|
config SECURITY_SELINUX
|
|
|
|
|
bool "NSA SELinux Support"
|
selinux: don't require auditing
Audit is bad. It affects performance under all circumstances. It's also
dirty.
From LWN: "Andy submitted a patch to fix this particular problem, but he
didn't stop there. He has come to the conclusion that the audit
subsystem is beyond repair, so his patch marks the whole thing as being
broken, making it generally inaccessible. He cited a number of problems
beyond this security issue: it hurts performance even when it is not
being used, it is not (in his mind) reliable, it has problems with
various architectures, and "its approach to freeing memory is
terrifying." All told, Andy said, we're better off without it"
Signed-off-by: kdrag0n <dragon@khronodragon.com>
Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com>
(cherry picked from commit 2af6b94e4a6ec4b82db3a0fb9d9e408134988b26)
selinux: don't require auditing
Audit is bad. It affects performance under all circumstances. It's also
dirty.
From LWN: "Andy submitted a patch to fix this particular problem, but he
didn't stop there. He has come to the conclusion that the audit
subsystem is beyond repair, so his patch marks the whole thing as being
broken, making it generally inaccessible. He cited a number of problems
beyond this security issue: it hurts performance even when it is not
being used, it is not (in his mind) reliable, it has problems with
various architectures, and "its approach to freeing memory is
terrifying." All told, Andy said, we're better off without it"
Signed-off-by: kdrag0n <dragon@khronodragon.com>
Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com>
v
(cherry picked from commit ec3f662b38ed90a9f88941374b5f4d125193aeee)
2020-05-05 16:05:35 +02:00
|
|
|
depends on SECURITY_NETWORK && 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 00:33:33 -07:00
|
|
|
select NETWORK_SECMARK
|
2005-04-16 15:20:36 -07:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This selects NSA Security-Enhanced Linux (SELinux).
|
|
|
|
|
You will also need a policy configuration and a labeled filesystem.
|
|
|
|
|
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.
|
|
|
|
|
|
2023-01-10 23:21:17 +03:00
|
|
|
config SECURITY_SELINUX_CUSTOM_ENFORCE
|
|
|
|
|
bool "NSA SELinux Custom Enforcing"
|
|
|
|
|
depends on SECURITY_SELINUX_DEVELOP
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option will pick SELinux setting from kernel command line via custom_enforcing.
|
|
|
|
|
|
2022-11-27 18:55:28 +03:00
|
|
|
config SECURITY_SELINUX_NEVER_ENFORCE
|
|
|
|
|
bool "NSA SELinux Never Enforcing"
|
|
|
|
|
depends on SECURITY_SELINUX_DEVELOP
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option will prevent anything from setting SELinux to enforcing.
|
|
|
|
|
|
2023-01-10 23:21:17 +03:00
|
|
|
config SECURITY_SELINUX_FAKE_ENFORCE_SUPPORT
|
|
|
|
|
bool "NSA SELinux Fake Enforcing Support"
|
|
|
|
|
depends on SECURITY_SELINUX_DEVELOP
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option will give faking SELinux to enforcing.
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
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
|
2015-10-21 17:44:25 -04:00
|
|
|
default 0
|
2005-04-16 15:20:36 -07:00
|
|
|
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.
|
|
|
|
|
|
2015-10-21 17:44:25 -04:00
|
|
|
If you are unsure how to answer this question, answer 0.
|
