All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
	herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-kernel@vger.kernel.org, saulo.alessandre@tse.jus.br,
	lukas@wunner.de, Stefan Berger <stefanb@linux.ibm.com>,
	David Howells <dhowells@redhat.com>
Subject: [PATCH v5 12/12] crypto: x509 - Add OID for NIST P521 and extend parser for it
Date: Wed,  6 Mar 2024 17:22:57 -0500	[thread overview]
Message-ID: <20240306222257.979304-13-stefanb@linux.ibm.com> (raw)
In-Reply-To: <20240306222257.979304-1-stefanb@linux.ibm.com>

Enable the x509 parser to accept NIST P521 certificates and add the
OID for ansip521r1, which is the identifier for NIST P521.

Cc: David Howells <dhowells@redhat.com>
Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
Tested-by: Lukas Wunner <lukas@wunner.de>
---
 crypto/asymmetric_keys/x509_cert_parser.c | 3 +++
 include/linux/oid_registry.h              | 1 +
 2 files changed, 4 insertions(+)

diff --git a/crypto/asymmetric_keys/x509_cert_parser.c b/crypto/asymmetric_keys/x509_cert_parser.c
index 487204d39426..99f809b7910b 100644
--- a/crypto/asymmetric_keys/x509_cert_parser.c
+++ b/crypto/asymmetric_keys/x509_cert_parser.c
@@ -538,6 +538,9 @@ int x509_extract_key_data(void *context, size_t hdrlen,
 		case OID_id_ansip384r1:
 			ctx->cert->pub->pkey_algo = "ecdsa-nist-p384";
 			break;
+		case OID_id_ansip521r1:
+			ctx->cert->pub->pkey_algo = "ecdsa-nist-p521";
+			break;
 		default:
 			return -ENOPKG;
 		}
diff --git a/include/linux/oid_registry.h b/include/linux/oid_registry.h
index 3921fbed0b28..af16d96fbbf2 100644
--- a/include/linux/oid_registry.h
+++ b/include/linux/oid_registry.h
@@ -65,6 +65,7 @@ enum OID {
 	OID_Scram,			/* 1.3.6.1.5.5.14 */
 	OID_certAuthInfoAccess,		/* 1.3.6.1.5.5.7.1.1 */
 	OID_id_ansip384r1,		/* 1.3.132.0.34 */
+	OID_id_ansip521r1,		/* 1.3.132.0.35 */
 	OID_sha256,			/* 2.16.840.1.101.3.4.2.1 */
 	OID_sha384,			/* 2.16.840.1.101.3.4.2.2 */
 	OID_sha512,			/* 2.16.840.1.101.3.4.2.3 */
-- 
2.43.0


      parent reply	other threads:[~2024-03-06 22:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 22:22 [PATCH v4 00/12] Add support for NIST P521 to ecdsa Stefan Berger
2024-03-06 22:22 ` [PATCH v5 01/12] crypto: ecdsa - Convert byte arrays with key coordinates to digits Stefan Berger
2024-03-08  8:41   ` Lukas Wunner
2024-03-08 12:11     ` Stefan Berger
2024-03-06 22:22 ` [PATCH v5 02/12] crypto: ecdsa - Adjust tests on length of key parameters Stefan Berger
2024-03-06 22:22 ` [PATCH v5 03/12] crypto: ecdsa - Extend res.x mod n calculation for NIST P521 Stefan Berger
2024-03-06 22:22 ` [PATCH v5 04/12] crypto: ecc - Add nbits field to ecc_curve structure Stefan Berger
2024-03-06 22:22 ` [PATCH v5 05/12] crypto: ecc - Implement vli_mmod_fast_521 for NIST p521 Stefan Berger
2024-03-07 19:11   ` Jarkko Sakkinen
2024-03-07 20:37     ` Stefan Berger
2024-03-11  5:07   ` [EXTERNAL] " Bharat Bhushan
2024-03-11 14:03     ` Stefan Berger
2024-03-11 16:11       ` [EXTERNAL] " Bharat Bhushan
2024-03-06 22:22 ` [PATCH v5 06/12] crypto: ecc - Add special case for NIST P521 in ecc_point_mult Stefan Berger
2024-03-06 22:22 ` [PATCH v5 07/12] crypto: ecc - Add NIST P521 curve parameters Stefan Berger
2024-03-06 22:22 ` [PATCH v5 08/12] crypto: ecdsa - Replace ndigits with nbits where precision is needed Stefan Berger
2024-03-06 22:22 ` [PATCH v5 09/12] crypto: ecdsa - Rename keylen to bufsize where necessary Stefan Berger
2024-03-07 19:13   ` Jarkko Sakkinen
2024-03-07 19:20     ` Stefan Berger
2024-03-08  7:48       ` Vitaly Chikunov
2024-03-06 22:22 ` [PATCH v5 10/12] crypto: ecdsa - Register NIST P521 and extend test suite Stefan Berger
2024-03-06 22:22 ` [PATCH v5 11/12] crypto: asymmetric_keys - Adjust signature size calculation for NIST P521 Stefan Berger
2024-03-06 22:22 ` Stefan Berger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240306222257.979304-13-stefanb@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=saulo.alessandre@tse.jus.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.