#
# Security configuration
#

menu "Security options"

source security/keys/Kconfig

config SECURITY_DMESG_RESTRICT
	bool "Restrict unprivileged access to the kernel syslog"
	default n
	help
	  This enforces restrictions on unprivileged users reading the kernel
	  syslog via dmesg(8).

	  If this option is not selected, no restrictions will be enforced
	  unless the dmesg_restrict sysctl is explicitly set to (1).

	  If you are unsure how to answer this question, answer N.

config SECURITY
	bool "Enable different security models"
	depends on SYSFS
	depends on MULTIUSER
	help
	  This allows you to choose different security modules to be
	  configured into your kernel.

	  If this option is not selected, the default Linux security
	  model will be used.

	  If you are unsure how to answer this question, answer N.

config SECURITY_STACKING
	bool "Security module stacking"
	depends on SECURITY && (SECURITY_SELINUX || SECURITY_KYSEC || SECURITY_SMACK || SECURITY_APPARMOR || SECURITY_KIC)
	default y
	help
	  Allows multiple major security modules to be stacked.
	  Modules are invoked in the order registered with a
	  "bail on fail" policy, in which the infrastructure
	  will stop processing once a denial is detected. Not
	  all modules can be stacked. SELinux and Smack are
	  known to be incompatible. User space components may
	  have trouble identifying the security module providing
	  data in some cases.

	  If you select this option you will have to select which
	  of the stackable modules you wish to be active. The
	  "Default security module" will be ignored. The boot line
	  "security=" option can be used to specify that one of
	  the modules identifed for stacking should be used instead
	  of the entire stack.

	  If you are unsure how to answer this question, answer N.

config SECURITY_LSM_STACKING_MAX
	int "Max count of security modules stacked"
	depends on SECURITY_STACKING
	range 3 10
	default 6
	help
	  This defines the max count of lsm modules stacked. The
	  Capability and Yama modules are enabled by default if
	  built, so this value should be 2 at least.

	  If you are unsure how to answer this question, 6 would
	  be enough for most cases.


config SECURITY_LSM_DEBUG
	bool "Enable debugging of the LSM infrastructure"
	depends on SECURITY
	help
	  This allows you to choose debug messages related to
	  security modules configured into your kernel. These
	  messages may be helpful in determining how a security
	  module is using security blobs.

	  If you are unsure how to answer this question, answer N.

config PAGE_TABLE_ISOLATION
	bool "Remove the kernel mapping in user mode"
	default y
	depends on X86_64 && SMP
	help
	  This enforces a strict kernel and user space isolation, in order
	  to close hardware side channels on kernel address information.

	  If you are unsure how to answer this question, answer Y.

config SECURITYFS
	bool "Enable the securityfs filesystem"
	help
	  This will build the securityfs filesystem.  It is currently used by
	  the TPM bios character driver and IMA, an integrity provider.  It is
	  not used by SELinux or SMACK.

	  If you are unsure how to answer this question, answer N.

config SECURITY_NETWORK
	bool "Socket and Networking Security Hooks"
	depends on SECURITY
	help
	  This enables the socket and networking security hooks.
	  If enabled, a security module can use these hooks to
	  implement socket and networking access controls.
	  If you are unsure how to answer this question, answer N.

config SECURITY_NETWORK_XFRM
	bool "XFRM (IPSec) Networking Security Hooks"
	depends on XFRM && SECURITY_NETWORK
	help
	  This enables the XFRM (IPSec) networking security hooks.
	  If enabled, a security module can use these hooks to
	  implement per-packet access controls based on labels
	  derived from IPSec policy.  Non-IPSec communications are
	  designated as unlabelled, and only sockets authorized
	  to communicate unlabelled data can send without using
	  IPSec.
	  If you are unsure how to answer this question, answer N.

config SECURITY_PATH
	bool "Security hooks for pathname based access control"
	depends on SECURITY
	help
	  This enables the security hooks for pathname based access control.
	  If enabled, a security module can use these hooks to
	  implement pathname based access controls.
	  If you are unsure how to answer this question, answer N.

config SECURITY_SECURELEVEL
        bool "Securelevel kernel restriction interface"
	depends on SECURITY
	help
	  This enables support for adding a set of additional kernel security
	  restrictions at runtime. See Documentation/security/securelevel.txt
	  for further information.

config INTEL_TXT
	bool "Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)"
	depends on HAVE_INTEL_TXT
	help
	  This option enables support for booting the kernel with the
	  Trusted Boot (tboot) module. This will utilize
	  Intel(R) Trusted Execution Technology to perform a measured launch
	  of the kernel. If the system does not support Intel(R) TXT, this
	  will have no effect.

	  Intel TXT will provide higher assurance of system configuration and
	  initial state as well as data reset protection.  This is used to
	  create a robust initial kernel measurement and verification, which
	  helps to ensure that kernel security mechanisms are functioning
	  correctly. This level of protection requires a root of trust outside
	  of the kernel itself.

	  Intel TXT also helps solve real end user concerns about having
	  confidence that their hardware is running the VMM or kernel that
	  it was configured with, especially since they may be responsible for
	  providing such assurances to VMs and services running on it.

	  See <http://www.intel.com/technology/security/> for more information
	  about Intel(R) TXT.
	  See <http://tboot.sourceforge.net> for more information about tboot.
	  See Documentation/intel_txt.txt for a description of how to enable
	  Intel TXT support in a kernel boot.

	  If you are unsure as to whether this is required, answer N.

config LSM_MMAP_MIN_ADDR
	int "Low address space for LSM to protect from user allocation"
	depends on SECURITY && SECURITY_SELINUX
	default 32768 if ARM || (ARM64 && COMPAT)
	default 65536
	help
	  This is the portion of low virtual memory which should be protected
	  from userspace allocation.  Keeping a user from writing to low pages
	  can help reduce the impact of kernel NULL pointer bugs.

	  For most ia64, ppc64 and x86 users with lots of address space
	  a value of 65536 is reasonable and should cause no problems.
	  On arm and other archs it should not be higher than 32768.
	  Programs which use vm86 functionality or have some need to map
	  this low address space will need the permission specific to the
	  systems running LSM.
config SECURITY_CCA
	bool "KYLIN CCA"
	depends on SECURITY
	default n
	help
	  This enables the Convert Channel Analysis functionality of KYLIN .

config KYLIN_USBCTRL
	bool "Kylin usb devices control"
	default n
	help
	  This enables the control for USB devices.

config SECURITY_KYLIN_EXTEND
	bool "Kylin extend module"
	depends on SECURITY_STACKING
	default n
	help
	  This enables kylin extend module for security_add function,
	  and solves the problem when other lsm modules protected by
	  __ro_after_init then the lsm module in userspace can not load.

config KYLIN_UNEXPORT_SYMBOLS
	bool "Kylin unexported symbols"
	depends on KALLSYMS_ALL
	default n
	help
	  This enables kylin unexported symbols to filter some symbols
	  which we want not to exported.

source security/selinux/Kconfig
source security/kysec/Kconfig
source security/box/Kconfig
source security/smack/Kconfig
source security/tomoyo/Kconfig
source security/apparmor/Kconfig
source security/yama/Kconfig
source security/kic/Kconfig

source security/integrity/Kconfig

menu "Default security settings"
choice
	prompt "Default security module"

	config DEFAULT_SECURITY_SELINUX
		bool "SELinux" if SECURITY_SELINUX=y && SECURITY_STACKING!=y

	config DEFAULT_SECURITY_KYSEC
		bool "Kysec" if SECURITY_KYSEC=y && SECURITY_STACKING!=y

	config DEFAULT_SECURITY_SMACK
		bool "Simplified Mandatory Access Control" if SECURITY_SMACK=y && SECURITY_STACKING!=y

	config DEFAULT_SECURITY_TOMOYO
		bool "TOMOYO" if SECURITY_TOMOYO=y && SECURITY_STACKING!=y

	config DEFAULT_SECURITY_APPARMOR
		bool "AppArmor" if SECURITY_APPARMOR=y && SECURITY_STACKING!=y

	config DEFAULT_SECURITY_KIC
		bool "KIC" if SECURITY_KIC=y && SECURITY_STACKING!=y
		help
		  Enable Kylin integrity control by default, you need to
		  make sure that the userspace tools has been installed
		  and configured properly.

		  If you are unsure as to whether this is required, answer N.

	config DEFAULT_SECURITY_DAC
		bool "Unix Discretionary Access Controls"

	config DEFAULT_SECURITY_STACKING
		bool "Security Stacking" if SECURITY_STACKING

endchoice

menu "Default security modules for stacking"
	depends on DEFAULT_SECURITY_STACKING
	config DEFAULT_SECURITY_SELINUX_STACKED
		bool "SELinux" if SECURITY_SELINUX=y && SECURITY_STACKING=y
		help
		  Enable SELinux module as one LSM by default.

		  If you are unsure as to whether this is required, answer N.

	config DEFAULT_SECURITY_KYSEC_STACKED
		bool "Kysec" if SECURITY_KYSEC=y && SECURITY_STACKING=y
		help
		  Enable Kysec module by default for LSM stacking. You can
		  see CONFIG_SECURITY_KYSEC for details.

		  If you are unsure as to whether this is required, answer N.

	config DEFAULT_SECURITY_BOX_STACKED
		bool "Box protect" if SECURITY_BOX_PROTECT=y && SECURITY_STACKING=y
		help
		  Enable Box protect module by default for LSM stacking. You can
		  see CONFIG_SECURITY_BOX_PROTECT and CONFIG_SECURITY_STACKING
		  for details.

		  If you are unsure as to whether this is required, answer N.


	config DEFAULT_SECURITY_SMACK_STACKED
		bool "Smack" if SECURITY_SMACK=y && SECURITY_STACKING=y
		help
		  Enable Smack module by default for LSM stacking. You can
		  see CONFIG_SECURITY_SMACK and CONFIG_SECURITY_STACKING
		  for details.

		  If you are unsure as to whether this is required, answer N.

	config DEFAULT_SECURITY_TOMOYO_STACKED
		bool "TOMOYO" if SECURITY_TOMOYO=y && SECURITY_STACKING=y
		help
		  Enable Tomoyo module by default for LSM stacking. You can
		  see CONFIG_SECURITY_TOMOYO and CONFIG_SECURITY_STACKING
		  for details.

		  If you are unsure as to whether this is required, answer N.

	config DEFAULT_SECURITY_APPARMOR_STACKED
		bool "AppArmor" if SECURITY_APPARMOR=y && SECURITY_STACKING=y
		help
		  Enable Apparmor module by default for LSM stacking. You can
		  see CONFIG_SECURITY_APPARMOR and CONFIG_SECURITY_STACKING
		  for details.

		  If you are unsure as to whether this is required, answer N.

	config DEFAULT_SECURITY_KIC_STACKED
		bool "KIC" if SECURITY_KIC=y && SECURITY_STACKING=y
		help
		  Enable Kylin Integrity Control module by default for LSM
		  stacking. You can see CONFIG_SECURITY_KIC and
		  CONFIG_SECURITY_STACKING for details.

		  If you are unsure as to whether this is required, answer N.

endmenu
endmenu

config DEFAULT_SECURITY
	string
	default "selinux" if DEFAULT_SECURITY_SELINUX
	default "kysec" if DEFAULT_SECURITY_KYSEC
	default "smack" if DEFAULT_SECURITY_SMACK
	default "tomoyo" if DEFAULT_SECURITY_TOMOYO
	default "apparmor" if DEFAULT_SECURITY_APPARMOR
	default "kic" if DEFAULT_SECURITY_KIC
	default "" if DEFAULT_SECURITY_DAC
	default "stacking" if DEFAULT_SECURITY_STACKING
endmenu
