keys: Update comment for restrict_link_by_key_or_keyring_chain
Subsystems (3)
PATCH RESEND 1/1 keys: Update comment for restrict_link_by_key_or_keyring_chain
Add the bit of information that makes restrict_link_by_key_or_keyring_chain different from restrict_link_by_key_or_keyring to the inline docs comment.
Signed-off-by Andrew Zaborowski <[email protected]>
--- crypto/asymmetric_keys/restrict.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
crypto/asymmetric_keys/restrict.c +4 -3
@@ -244,9 +244,10 @@ int restrict_link_by_key_or_keyring(struct key *dest_keyring,* @payload: The payload of the new key. * @trusted: A key or ring of keys that can be used to vouch for the new cert. * -* Check the new certificate only against the key or keys passed in the data -* parameter. If one of those is the signing key and validates the new -* certificate, then mark the new certificate as being ok to link. +* Check the new certificate against the key or keys passed in the data +* parameter and against the keys already linked to the destination keyring. If +* one of those is the signing key and validates the new certificate, then mark +* the new certificate as being ok to link. * * Returns 0 if the new certificate was accepted, -ENOKEY if we * couldn't find a matching parent certificate in the trusted list,
Signature · 1 line
2.20.1
Quoted 5 lines · Andrew Zaborowski
Add the bit of information that makes
restrict_link_by_key_or_keyring_chaindifferent fromrestrict_link_by_key_or_keyringto the inline docs comment.Signed-off-by Andrew Zaborowski <[email protected]>
Acked-by Jarkko Sakkinen <[email protected]>
Quoted 26 lines
--- crypto/asymmetric_keys/restrict.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)crypto/asymmetric_keys/restrict.c +4
-3@@ -244,9 +244,10 @@ int restrict_link_by_key_or_keyring(struct key *dest_keyring,* @payload: The payload of the new key. * @trusted: A key or ring of keys that can be used to vouch for the new cert. * -* Check the new certificate only against the key or keys passed in the data -* parameter. If one of those is the signing key and validates the new -* certificate, then mark the new certificate as being ok to link. +* Check the new certificate against the key or keys passed in the data +* parameter and against the keys already linked to the destination keyring. If +* one of those is the signing key and validates the new certificate, then mark +* the new certificate as being ok to link. * * Returns 0 if the new certificate was accepted, -ENOKEY if we * couldn't find a matching parent certificate in the trusted list, Signature · 1 line
2.20.1
/Jarkko