diff options
author | Eric Snowberg <eric.snowberg@oracle.com> | 2023-03-02 17:46:50 +0100 |
---|---|---|
committer | Jarkko Sakkinen <jarkko@kernel.org> | 2023-04-24 15:15:53 +0200 |
commit | 567671281a751b80918a4531c4ba84b90a2a42c0 (patch) | |
tree | 7ba5b47c220649c0025da8afcd44f73247f868c5 /Documentation/scsi | |
parent | KEYS: X.509: Parse Basic Constraints for CA (diff) | |
download | linux-567671281a751b80918a4531c4ba84b90a2a42c0.tar.xz linux-567671281a751b80918a4531c4ba84b90a2a42c0.zip |
KEYS: X.509: Parse Key Usage
Parse the X.509 Key Usage. The key usage extension defines the purpose of
the key contained in the certificate.
id-ce-keyUsage OBJECT IDENTIFIER ::= { id-ce 15 }
KeyUsage ::= BIT STRING {
digitalSignature (0),
contentCommitment (1),
keyEncipherment (2),
dataEncipherment (3),
keyAgreement (4),
keyCertSign (5),
cRLSign (6),
encipherOnly (7),
decipherOnly (8) }
If the keyCertSign or digitalSignature is set, store it in the
public_key structure. Having the purpose of the key being stored
during parsing, allows enforcement on the usage field in the future.
This will be used in a follow on patch that requires knowing the
certificate key usage type.
Link: https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.3
Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
Tested-by: Mimi Zohar <zohar@linux.ibm.com>
Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
Diffstat (limited to 'Documentation/scsi')
0 files changed, 0 insertions, 0 deletions