Commit adf31eeb authored by Josh Holland's avatar Josh Holland Committed by Jonathan Corbet

docs: Fix paths in security/keys

Several paths in the security/keys documentation were incorrect.
Signed-off-by: default avatarJosh Holland <anowlcalledjosh@gmail.com>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 8ac5ac1b
......@@ -443,7 +443,7 @@ The main syscalls are:
/sbin/request-key will be invoked in an attempt to obtain a key. The
callout_info string will be passed as an argument to the program.
See also Documentation/security/keys-request-key.txt.
See also Documentation/security/keys/request-key.rst.
The keyctl syscall functions are:
......@@ -973,7 +973,7 @@ payload contents" for more information.
If successful, the key will have been attached to the default keyring for
implicitly obtained request-key keys, as set by KEYCTL_SET_REQKEY_KEYRING.
See also Documentation/security/keys-request-key.txt.
See also Documentation/security/keys/request-key.rst.
* To search for a key, passing auxiliary data to the upcaller, call::
......
......@@ -3,7 +3,7 @@ Key Request Service
===================
The key request service is part of the key retention service (refer to
Documentation/security/keys.txt). This document explains more fully how
Documentation/security/core.rst). This document explains more fully how
the requesting algorithm works.
The process starts by either the kernel requesting a service by calling
......
......@@ -172,4 +172,4 @@ Other uses for trusted and encrypted keys, such as for disk and file encryption
are anticipated. In particular the new format 'ecryptfs' has been defined in
in order to use encrypted keys to mount an eCryptfs filesystem. More details
about the usage can be found in the file
``Documentation/security/keys-ecryptfs.txt``.
``Documentation/security/keys/ecryptfs.rst``.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment