LSM: LoadPin for kernel file loading restrictions
authorKees Cook <keescook@chromium.org>
Wed, 20 Apr 2016 22:46:28 +0000 (15:46 -0700)
committerJames Morris <james.l.morris@oracle.com>
Thu, 21 Apr 2016 00:47:27 +0000 (10:47 +1000)
commit9b091556a073a9f5f93e2ad23d118f45c4796a84
tree075fffff80b5caad9738f633c83333dea9e04efd
parent1284ab5b2dcb927d38e4f3fbc2e307f3d1af9262
LSM: LoadPin for kernel file loading restrictions

This LSM enforces that kernel-loaded files (modules, firmware, etc)
must all come from the same filesystem, with the expectation that
such a filesystem is backed by a read-only device such as dm-verity
or CDROM. This allows systems that have a verified and/or unchangeable
filesystem to enforce module and firmware loading restrictions without
needing to sign the files individually.

Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Serge Hallyn <serge.hallyn@canonical.com>
Signed-off-by: James Morris <james.l.morris@oracle.com>
Documentation/security/LoadPin.txt [new file with mode: 0644]
MAINTAINERS
include/linux/lsm_hooks.h
security/Kconfig
security/Makefile
security/loadpin/Kconfig [new file with mode: 0644]
security/loadpin/Makefile [new file with mode: 0644]
security/loadpin/loadpin.c [new file with mode: 0644]
security/security.c