Datasets:
memorylost731
/
linux_man_pages_library

Dataset card Data Studio Files Community
1
text
stringlengths
0
234
char *otherinfo; /* sp800\-56a otherinfo */
__u32 otherinfolen; /* length of otherinfo data */
__u32 __spare[8]; /* reserved */
};
.ee
.in
.ip
the
.i hashname
field is a null-terminated string which specifies a hash name
(available in the kernel's crypto api; the list of the hashes available
is rather tricky to observe; please refer to the
.ur https://www.kernel.org\:/doc\:/html\:/latest\:/crypto\:/architecture.html
"kernel crypto api architecture"
.ue
documentation for the information regarding how hash names are constructed and
your kernel's source and configuration regarding what ciphers
and templates with type
.b crypto_alg_type_shash
are available)
to be applied to dh result in kdf operation.
.ip
the
.i otherinfo
field is an
.i otherinfo
data as described in sp800-56a section 5.8.1.2 and is algorithm-specific.
this data is concatenated with the result of dh operation and is provided as
an input to the kdf operation.
its size is provided in the
.i otherinfolen
field and is limited by
.b keyctl_kdf_max_oi_len
constant that defined in
.i security/keys/internal.h
to a value of 64.
.ip
the
.b __spare
field is currently unused.
.\" commit 4f9dabfaf8df971f8a3b6aa324f8f817be38d538
it was ignored until linux 4.13 (but still should be
user-addressable since it is copied to the kernel),
and should contain zeros since linux 4.13.
.ip
the kdf implementation complies with sp800-56a as well
as with sp800-108 (the counter kdf).
.ip
.\" keyutils commit 742c9d7b94051d3b21f9f61a73ed6b5f3544cb82
.\" keyutils commit d68a981e5db41d059ac782071c35d1e8f3aaf61c
this operation is exposed by
.i libkeyutils
(from version 1.5.10 onwards) via the functions
.br keyctl_dh_compute (3)
and
.br keyctl_dh_compute_alloc (3).
.tp
.br keyctl_restrict_keyring " (since linux 4.12)"
.\" commit 6563c91fd645556c7801748f15bc727c77fcd311
.\" commit 7228b66aaf723a623e578aa4db7d083bb39546c9
apply a key-linking restriction to the keyring with the id provided in
.ir arg2
(cast to
.ir key_serial_t ).
the caller must have
.ir setattr
permission on the key.
if
.i arg3
is null, any attempt to add a key to the keyring is blocked;
otherwise it contains a pointer to a string with a key type name and
.i arg4
contains a pointer to string that describes the type-specific restriction.
as of linux 4.12, only the type "asymmetric" has restrictions defined:
.rs
.tp
.b builtin_trusted
allows only keys that are signed by a key linked to the built-in keyring
(".builtin_trusted_keys").
.tp
.b builtin_and_secondary_trusted
allows only keys that are signed by a key linked to the secondary keyring
(".secondary_trusted_keys") or, by extension, a key in a built-in keyring,
as the latter is linked to the former.
.tp
.bi key_or_keyring: key
.tq
.bi key_or_keyring: key :chain
if
.i key
specifies the id of a key of type "asymmetric",
then only keys that are signed by this key are allowed.
.ip
if
.i key
specifies the id of a keyring,
then only keys that are signed by a key linked
to this keyring are allowed.
.ip
if ":chain" is specified, keys that are signed by a keys linked to the