The table of special key IDs stops at KEY_SPEC_REQKEY_AUTH_KEY. Fill in all the new ones.
Suggested-by: Christian Brauner (Amutable) <[email protected]> Signed-off-by: Andrew Halaney <[email protected]> --- Documentation/security/keys/core.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/Documentation/security/keys/core.rst b/Documentation/security/keys/core.rst index 326b8a973828..37ed42382f16 100644 --- a/Documentation/security/keys/core.rst +++ b/Documentation/security/keys/core.rst @@ -372,6 +372,19 @@ process making the call:: KEY_SPEC_GROUP_KEYRING -6 GID-specific keyring KEY_SPEC_REQKEY_AUTH_KEY -7 assumed request_key() authorisation key + KEY_SPEC_REQUESTOR_KEYRING -8 request_key() destination + keyring + +There are also values that refer to a specific kernel keyring rather than to +anything belonging to the caller. These keyrings are not linked into any +keyring, so a search cannot reach them and the ID is the only way to name +one:: + + CONSTANT VALUE KEY REFERENCED + ============================== ====== =========================== + KEY_SPEC_BPF_KEYRING -9 the ".bpf" keyring + KEY_SPEC_DM_VERITY_KEYRING -10 the ".dm-verity" keyring + KEY_SPEC_FS_VERITY_KEYRING -11 the ".fs-verity" keyring The main syscalls are: -- 2.55.0
