diff options
| author | Kees Cook | 2017-05-13 04:51:48 -0700 |
|---|---|---|
| committer | Jonathan Corbet | 2017-05-18 10:33:12 -0600 |
| commit | 30da4f77aae99bf9ae5905d0ef89668391eea315 (patch) | |
| tree | 6bdbb0f745969dc954b849c9d488c40842b6ae21 /Documentation/security | |
| parent | 90bb766440f2147486a2acc3e793d7b8348b0c22 (diff) | |
doc: ReSTify LoadPin.txt
Adjusts for ReST markup and moves under LSM admin guide.
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/security')
| -rw-r--r-- | Documentation/security/LoadPin.txt | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/Documentation/security/LoadPin.txt b/Documentation/security/LoadPin.txt deleted file mode 100644 index e11877f5d3d4..000000000000 --- a/Documentation/security/LoadPin.txt +++ /dev/null @@ -1,17 +0,0 @@ -LoadPin is a Linux Security Module that ensures all kernel-loaded files -(modules, firmware, etc) all originate 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. - -The LSM is selectable at build-time with CONFIG_SECURITY_LOADPIN, and -can be controlled at boot-time with the kernel command line option -"loadpin.enabled". By default, it is enabled, but can be disabled at -boot ("loadpin.enabled=0"). - -LoadPin starts pinning when it sees the first file loaded. If the -block device backing the filesystem is not read-only, a sysctl is -created to toggle pinning: /proc/sys/kernel/loadpin/enabled. (Having -a mutable filesystem means pinning is mutable too, but having the -sysctl allows for easy testing on systems with a mutable filesystem.) |