2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
# Security configuration
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menu "Security options"
|
|
|
|
|
|
|
|
|
|
config KEYS
|
|
|
|
|
bool "Enable access key retention support"
|
|
|
|
|
help
|
|
|
|
|
This option provides support for retaining authentication tokens and
|
|
|
|
|
access keys in the kernel.
|
|
|
|
|
|
|
|
|
|
It also includes provision of methods by which such keys might be
|
|
|
|
|
associated with a process so that network filesystems, encryption
|
|
|
|
|
support and the like can find them.
|
|
|
|
|
|
|
|
|
|
Furthermore, a special type of key is available that acts as keyring:
|
|
|
|
|
a searchable sequence of keys. Each process is equipped with access
|
|
|
|
|
to five standard keyrings: UID-specific, GID-specific, session,
|
|
|
|
|
process and thread.
|
|
|
|
|
|
|
|
|
|
If you are unsure as to whether this is required, answer N.
|
|
|
|
|
|
|
|
|
|
config KEYS_DEBUG_PROC_KEYS
|
|
|
|
|
bool "Enable the /proc/keys file by which all keys may be viewed"
|
|
|
|
|
depends on KEYS
|
|
|
|
|
help
|
|
|
|
|
This option turns on support for the /proc/keys file through which
|
|
|
|
|
all the keys on the system can be listed.
|
|
|
|
|
|
|
|
|
|
This option is a slight security risk in that it makes it possible
|
|
|
|
|
for anyone to see all the keys on the system. Normally the manager
|
|
|
|
|
pretends keys that are inaccessible to a process don't exist as far
|
|
|
|
|
as that process is concerned.
|
|
|
|
|
|
|
|
|
|
config SECURITY
|
|
|
|
|
bool "Enable different security models"
|
2005-08-22 16:20:50 +00:00
|
|
|
depends on SYSFS
|
2005-04-16 22:20:36 +00:00
|
|
|
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_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.
|
[LSM-IPSec]: Security association restriction.
This patch series implements per packet access control via the
extension of the Linux Security Modules (LSM) interface by hooks in
the XFRM and pfkey subsystems that leverage IPSec security
associations to label packets. Extensions to the SELinux LSM are
included that leverage the patch for this purpose.
This patch implements the changes necessary to the XFRM subsystem,
pfkey interface, ipv4/ipv6, and xfrm_user interface to restrict a
socket to use only authorized security associations (or no security
association) to send/receive network packets.
Patch purpose:
The patch is designed to enable access control per packets based on
the strongly authenticated IPSec security association. Such access
controls augment the existing ones based on network interface and IP
address. The former are very coarse-grained, and the latter can be
spoofed. By using IPSec, the system can control access to remote
hosts based on cryptographic keys generated using the IPSec mechanism.
This enables access control on a per-machine basis or per-application
if the remote machine is running the same mechanism and trusted to
enforce the access control policy.
Patch design approach:
The overall approach is that policy (xfrm_policy) entries set by
user-level programs (e.g., setkey for ipsec-tools) are extended with a
security context that is used at policy selection time in the XFRM
subsystem to restrict the sockets that can send/receive packets via
security associations (xfrm_states) that are built from those
policies.
A presentation available at
www.selinux-symposium.org/2005/presentations/session2/2-3-jaeger.pdf
from the SELinux symposium describes the overall approach.
Patch implementation details:
On output, the policy retrieved (via xfrm_policy_lookup or
xfrm_sk_policy_lookup) must be authorized for the security context of
the socket and the same security context is required for resultant
security association (retrieved or negotiated via racoon in
ipsec-tools). This is enforced in xfrm_state_find.
On input, the policy retrieved must also be authorized for the socket
(at __xfrm_policy_check), and the security context of the policy must
also match the security association being used.
The patch has virtually no impact on packets that do not use IPSec.
The existing Netfilter (outgoing) and LSM rcv_skb hooks are used as
before.
Also, if IPSec is used without security contexts, the impact is
minimal. The LSM must allow such policies to be selected for the
combination of socket and remote machine, but subsequent IPSec
processing proceeds as in the original case.
Testing:
The pfkey interface is tested using the ipsec-tools. ipsec-tools have
been modified (a separate ipsec-tools patch is available for version
0.5) that supports assignment of xfrm_policy entries and security
associations with security contexts via setkey and the negotiation
using the security contexts via racoon.
The xfrm_user interface is tested via ad hoc programs that set
security contexts. These programs are also available from me, and
contain programs for setting, getting, and deleting policy for testing
this interface. Testing of sa functions was done by tracing kernel
behavior.
Signed-off-by: Trent Jaeger <tjaeger@cse.psu.edu>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-12-14 07:12:27 +00:00
|
|
|
|
|
|
|
|
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.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
config SECURITY_CAPABILITIES
|
|
|
|
|
tristate "Default Linux Capabilities"
|
|
|
|
|
depends on SECURITY
|
|
|
|
|
help
|
|
|
|
|
This enables the "default" Linux capabilities functionality.
|
|
|
|
|
If you are unsure how to answer this question, answer Y.
|
|
|
|
|
|
|
|
|
|
config SECURITY_ROOTPLUG
|
|
|
|
|
tristate "Root Plug Support"
|
|
|
|
|
depends on USB && SECURITY
|
|
|
|
|
help
|
|
|
|
|
This is a sample LSM module that should only be used as such.
|
|
|
|
|
It prevents any programs running with egid == 0 if a specific
|
|
|
|
|
USB device is not present in the system.
|
|
|
|
|
|
|
|
|
|
See <http://www.linuxjournal.com/article.php?sid=6279> for
|
|
|
|
|
more information about this module.
|
|
|
|
|
|
|
|
|
|
If you are unsure how to answer this question, answer N.
|
|
|
|
|
|
|
|
|
|
config SECURITY_SECLVL
|
|
|
|
|
tristate "BSD Secure Levels"
|
|
|
|
|
depends on SECURITY
|
|
|
|
|
select CRYPTO
|
|
|
|
|
select CRYPTO_SHA1
|
|
|
|
|
help
|
|
|
|
|
Implements BSD Secure Levels as an LSM. See
|
|
|
|
|
<file:Documentation/seclvl.txt> for instructions on how to use this
|
|
|
|
|
module.
|
|
|
|
|
|
|
|
|
|
If you are unsure how to answer this question, answer N.
|
|
|
|
|
|
|
|
|
|
source security/selinux/Kconfig
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
