| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 23 Apr 2013 09:04:06 -0700 From: Casey Schaufler <casey@...aufler-ca.com> To: LSM <linux-security-module@...r.kernel.org>, LKLM <linux-kernel@...r.kernel.org>, SE Linux <selinux@...ho.nsa.gov>, James Morris <jmorris@...ei.org> CC: John Johansen <john.johansen@...onical.com>, Eric Paris <eparis@...hat.com>, Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>, Kees Cook <keescook@...omium.org>, Casey Schaufler <casey@...aufler-ca.com> Subject: [PATCH v13 0/9] LSM: Multiple concurrent LSMs Subject: [PATCH v13 0/9] LSM: Multiple concurrent LSMs Change the infrastructure for Linux Security Modules (LSM)s from a single vector of hook handlers to a list based method for handling multiple concurrent modules. The "security=" boot option takes a comma separated list of LSMs, registering them in the order presented. The LSM hooks will be executed in the order registered. Hooks that return errors are not short circuited. All hooks are called even if one of the LSM hooks fails. The result returned will be that of the last LSM hook that failed. All behavior from security/capability.c has been moved into the hook handling. The security/commoncap functions used to get called from the LSM specific code. The handling of the capability functions has been moved out of the LSMs and into the hook handling. A level of indirection has been introduced in the handling of security blobs. LSMs no longer access ->security fields directly, instead they use an abstraction provided by lsm_[gs]et field functions. The notion that "the security context" can be represented as a single u32 "secid" does not scale to the case where multiple LSMs want to provide "the security context". There are two types of use for secids, logging and networking. Logging is addressed by replacing the secid with a set of secids. Networking is addressed by allocating each scheme to a specific LSM. The NetLabel, XFRM and secmark facilities are restricted to use by one LSM at a time. This is due to limitations of the underlying networking mechanisms. The good news is that viable configurations can be created. The bad news is that the complexity of configuring a system is necessarily increased. The /proc/*/attr interfaces are given to one LSM. This can be done by setting CONFIG_SECURITY_PRESENT. Additional interfaces have been created in /proc/*/attr so that each LSM has its own named interfaces. A "security context" may now contrain information processed by more than one LSM. The proper form of a security context identifies the information it contains by LSM: smack='Pop'selinux='system_u:object_r:etc_r:s0' A security context without the LSM identifying lsm='<text>' gets passed through to all of the LSMs that use a security context. This maintains compatability in the case where there is only one LSM using the security context. Signed-off-by: Casey Schaufler <casey@...aufler-ca.com> --- Documentation/security/LSM.txt | 39 +- drivers/usb/core/devio.c | 10 +- fs/proc/base.c | 29 +- fs/sysfs/dir.c | 3 +- fs/sysfs/inode.c | 5 +- fs/sysfs/sysfs.h | 7 +- fs/xattr.c | 8 +- include/linux/audit.h | 9 +- include/linux/cred.h | 3 +- include/linux/lsm.h | 167 ++ include/linux/sched.h | 2 +- include/linux/security.h | 378 +++- include/net/af_unix.h | 3 +- include/net/netlabel.h | 3 +- include/net/scm.h | 8 +- include/net/xfrm.h | 4 +- kernel/audit.c | 94 +- kernel/audit.h | 4 +- kernel/auditfilter.c | 21 +- kernel/auditsc.c | 80 +- kernel/cred.c | 6 +- kernel/signal.c | 6 +- net/ipv4/ip_sockglue.c | 8 +- .../netfilter/nf_conntrack_l3proto_ipv4_compat.c | 11 +- net/netfilter/nf_conntrack_netlink.c | 24 +- net/netfilter/nf_conntrack_standalone.c | 11 +- net/netfilter/xt_SECMARK.c | 4 +- net/netlabel/netlabel_kapi.c | 37 +- net/netlabel/netlabel_unlabeled.c | 22 +- net/netlabel/netlabel_user.c | 4 +- net/netlabel/netlabel_user.h | 61 +- net/unix/af_unix.c | 17 +- net/xfrm/xfrm_user.c | 16 +- security/Kconfig | 176 +- security/Makefile | 3 +- security/apparmor/context.c | 10 +- security/apparmor/domain.c | 19 +- security/apparmor/include/context.h | 13 +- security/apparmor/lsm.c | 68 +- security/capability.c | 1105 ----------- security/commoncap.c | 6 - security/inode.c | 79 +- security/integrity/ima/ima_policy.c | 7 +- security/security.c | 2014 ++++++++++++++++---- security/selinux/hooks.c | 412 ++-- security/selinux/include/objsec.h | 2 + security/selinux/include/xfrm.h | 2 +- security/selinux/netlabel.c | 17 +- security/selinux/selinuxfs.c | 6 +- security/selinux/xfrm.c | 9 +- security/smack/smack.h | 15 +- security/smack/smack_access.c | 2 +- security/smack/smack_lsm.c | 474 +++-- security/smack/smackfs.c | 56 +- security/tomoyo/common.h | 6 +- security/tomoyo/domain.c | 2 +- security/tomoyo/securityfs_if.c | 9 +- security/tomoyo/tomoyo.c | 49 +- security/yama/Kconfig | 7 - security/yama/yama_lsm.c | 35 +- 60 files changed, 3357 insertions(+), 2350 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists