Documentation: fix security related doc refs
Make security document refs valid. Signed-off-by: Tom Saeger <tom.saeger@oracle.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Родитель
1752118d48
Коммит
c7f66400f5
|
@ -18,6 +18,6 @@ Description:
|
||||||
in the initramfs, which has already been measured as part
|
in the initramfs, which has already been measured as part
|
||||||
of the trusted boot. For more information on creating and
|
of the trusted boot. For more information on creating and
|
||||||
loading existing trusted/encrypted keys, refer to:
|
loading existing trusted/encrypted keys, refer to:
|
||||||
Documentation/keys-trusted-encrypted.txt. (A sample dracut
|
Documentation/security/keys/trusted-encrypted.rst. (A sample
|
||||||
patch, which loads the trusted/encrypted key and enables
|
dracut patch, which loads the trusted/encrypted key and enables
|
||||||
EVM, is available from http://linux-ima.sourceforge.net/#EVM.)
|
EVM, is available from http://linux-ima.sourceforge.net/#EVM.)
|
||||||
|
|
|
@ -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``.
|
use it) has been appropriately documented in ``Documentation/security/LSM.rst``.
|
||||||
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.
|
||||||
|
|
|
@ -196,7 +196,7 @@ The Linux kernel supports the following types of credentials:
|
||||||
When a process accesses a key, if not already present, it will normally be
|
When a process accesses a key, if not already present, it will normally be
|
||||||
cached on one of these keyrings for future accesses to find.
|
cached on one of these keyrings for future accesses to find.
|
||||||
|
|
||||||
For more information on using keys, see Documentation/security/keys.txt.
|
For more information on using keys, see ``Documentation/security/keys/*``.
|
||||||
|
|
||||||
5. LSM
|
5. LSM
|
||||||
|
|
||||||
|
|
|
@ -3,7 +3,7 @@ Key Request Service
|
||||||
===================
|
===================
|
||||||
|
|
||||||
The key request service is part of the key retention service (refer to
|
The key request service is part of the key retention service (refer to
|
||||||
Documentation/security/core.rst). This document explains more fully how
|
Documentation/security/keys/core.rst). This document explains more fully how
|
||||||
the requesting algorithm works.
|
the requesting algorithm works.
|
||||||
|
|
||||||
The process starts by either the kernel requesting a service by calling
|
The process starts by either the kernel requesting a service by calling
|
||||||
|
|
Загрузка…
Ссылка в новой задаче