Kees Cook | 504f231 | 2017-05-13 04:51:43 -0700 | [diff] [blame] | 1 | ================================= |
| 2 | Linux Security Module Development |
| 3 | ================================= |
| 4 | |
| 5 | Based on https://lkml.org/lkml/2007/10/26/215, |
| 6 | a new LSM is accepted into the kernel when its intent (a description of |
| 7 | what it tries to protect against and in what cases one would expect to |
| 8 | use it) has been appropriately documented in ``Documentation/security/LSM``. |
| 9 | This allows an LSM's code to be easily compared to its goals, and so |
| 10 | that end users and distros can make a more informed decision about which |
| 11 | LSMs suit their requirements. |
| 12 | |
| 13 | For extensive documentation on the available LSM hook interfaces, please |
| 14 | see ``include/linux/lsm_hooks.h``. |