blob: ac53e5065f79ed209d92da38382cf0eea281cb31 [file] [log] [blame]
Kees Cook504f2312017-05-13 04:51:43 -07001=================================
2Linux Security Module Development
3=================================
4
Joe Perches05a5f512021-01-10 12:41:44 -08005Based on https://lore.kernel.org/r/20071026073721.618b4778@laptopd505.fenrus.org,
Kees Cook504f2312017-05-13 04:51:43 -07006a new LSM is accepted into the kernel when its intent (a description of
7what it tries to protect against and in what cases one would expect to
Randy Dunlape6123c52018-10-08 17:46:04 -07008use it) has been appropriately documented in ``Documentation/admin-guide/LSM/``.
Kees Cook504f2312017-05-13 04:51:43 -07009This allows an LSM's code to be easily compared to its goals, and so
10that end users and distros can make a more informed decision about which
11LSMs suit their requirements.
12
13For extensive documentation on the available LSM hook interfaces, please
Kees Cook80fcc982019-02-17 14:19:01 -080014see ``include/linux/lsm_hooks.h`` and associated structures:
15
16.. kernel-doc:: include/linux/lsm_hooks.h
17 :internal: