mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-19 02:04:19 +08:00
e6123c5240
Acked-by: Kees Cook <keescook@chromium.org> Fix Documentation location reference for where LSM descriptions should be placed. Suggested-by: Kees Cook <keescook@chromium.org> Signed-off-by: Randy 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: James Morris <james.morris@microsoft.com>
15 lines
655 B
ReStructuredText
15 lines
655 B
ReStructuredText
=================================
|
|
Linux Security Module Development
|
|
=================================
|
|
|
|
Based on https://lkml.org/lkml/2007/10/26/215,
|
|
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
|
|
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
|
|
that end users and distros can make a more informed decision about which
|
|
LSMs suit their requirements.
|
|
|
|
For extensive documentation on the available LSM hook interfaces, please
|
|
see ``include/linux/lsm_hooks.h``.
|