| 1 | =================================
|
| 2 | Linux Security Module Development
|
| 3 | =================================
|
| 4 |
|
| 5 | Based on https://lore.kernel.org/r/[email protected],
|
| 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/admin-guide/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 ``security/security.c`` and associated structures:
|
| 15 |
|
| 16 | .. kernel-doc:: security/security.c
|
| 17 | :export:
|