Commit e6123c52 authored by Randy Dunlap's avatar Randy Dunlap Committed by James Morris

security: fix LSM description location

Acked-by: default avatarKees Cook <keescook@chromium.org>

Fix Documentation location reference for where LSM descriptions should
be placed.
Suggested-by: default avatarKees Cook <keescook@chromium.org>
Signed-off-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Cc: James Morris <jmorris@namei.org>
Cc: "Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-security-module@vger.kernel.org
Signed-off-by: default avatarJames Morris <james.morris@microsoft.com>
parent 2ecefa0a
...@@ -5,7 +5,7 @@ Linux Security Module Development ...@@ -5,7 +5,7 @@ Linux Security Module Development
Based on https://lkml.org/lkml/2007/10/26/215, Based on https://lkml.org/lkml/2007/10/26/215,
a new LSM is accepted into the kernel when its intent (a description of a new LSM is accepted into the kernel when its intent (a description of
what it tries to protect against and in what cases one would expect to what it tries to protect against and in what cases one would expect to
use it) has been appropriately documented in ``Documentation/security/LSM.rst``. use it) has been appropriately documented in ``Documentation/admin-guide/LSM/``.
This allows an LSM's code to be easily compared to its goals, and so This allows an LSM's code to be easily compared to its goals, and so
that end users and distros can make a more informed decision about which that end users and distros can make a more informed decision about which
LSMs suit their requirements. LSMs suit their requirements.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment