From: Stefan Berger <stefanb@linux.ibm.com>
To: Simo Sorce <simo@redhat.com>,
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
Subject: Re: [PATCH v2 00/14] Add support for NIST P521 to ecdsa and ecdh
Date: Fri, 16 Feb 2024 14:32:35 -0500 [thread overview]
Message-ID: <b507fd52-a807-4325-981b-3852f4f6190b@linux.ibm.com> (raw)
In-Reply-To: <3bdb1c9e0ac35c7dc3fbba1233bc7df80ac466a2.camel@redhat.com>
On 2/16/24 14:27, Simo Sorce wrote:
> On Thu, 2024-02-15 at 18:13 -0500, Stefan Berger wrote:
>> This series of patches adds support for the NIST P521 curve to ecdsa and
>> ecdh. Test cases for NIST P521 are added to both modules.
>>
>> An issue with the current code in ecdsa and ecdh is that it assumes that
>> input arrays providing key coordinates for example, are arrays of digits
>> (a 'digit' is a 'u64'). This works well for all currently supported
>> curves, such as NIST P192/256/384, but does not work for NIST P521 where
>> coordinates are 8 digits + 2 bytes long. So some of the changes deal with
>> converting byte arrays to digits and digits to byte arrays.
>>
>>
>> Regards,
>> Stefan
>>
>> v2:
>> - Reformulated some patch descriptions
>> - Fixed issue detected by krobot
>> - Some other small changes to the code
>>
>> Stefan Berger (14):
>> crypto: ecdsa - Convert byte arrays with key coordinates to digits
>> crypto: ecdsa - Adjust tests on length of key parameters
>> crypto: ecdsa - Extend res.x mod n calculation for NIST P521
>> crypto: ecc - Implement vli_mmod_fast_521 for NIST p521
>> crypto: ecc - For NIST P521 use vli_num_bits to get number of bits
>> crypto: ecc - Add NIST P521 curve parameters
>> crypto: ecdsa - Register NIST P521 and extend test suite
>> x509: Add OID for NIST P521 and extend parser for it
>> crypto: ecdh - Use properly formatted digits to check for valid key
>> crypto: ecc - Implement ecc_digits_to_bytes to convert digits to byte
>> array
>> crypto: Add nbits field to ecc_curve structure
>> crypto: ecc - Implement and use ecc_curve_get_nbytes to get curve's
>> nbytes
>> crypto: ecdh - Use functions to copy digits from and to byte array
>> crypto: ecdh - Add support for NIST P521 and add test case
>>
>> crypto/asymmetric_keys/x509_cert_parser.c | 3 +
>> crypto/ecc.c | 71 +++++--
>> crypto/ecc_curve_defs.h | 45 +++++
>> crypto/ecdh.c | 59 +++++-
>> crypto/ecdsa.c | 48 ++++-
>> crypto/testmgr.c | 14 ++
>> crypto/testmgr.h | 225 ++++++++++++++++++++++
>> include/crypto/ecc_curve.h | 3 +
>> include/crypto/ecdh.h | 1 +
>> include/crypto/internal/ecc.h | 61 +++++-
>> include/linux/oid_registry.h | 1 +
>> 11 files changed, 495 insertions(+), 36 deletions(-)
>
> Hi Stefan,
> what kind of side-channel testing was performed on this code?
> And what is the use case you are adding it for?
We're using public keys for signature verification. I am not aware that
public key usage is critical to side channels.
The use case for adding it is primarily driven by closing a gap to
complete the support for the common ECDSA NIST curves.
Stefan
>
> Thanks,
> Simo.
>
next prev parent reply other threads:[~2024-02-16 19:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 23:13 Stefan Berger
2024-02-15 23:14 ` [PATCH v2 01/14] crypto: ecdsa - Convert byte arrays with key coordinates to digits Stefan Berger
2024-02-15 23:14 ` [PATCH v2 02/14] crypto: ecdsa - Adjust tests on length of key parameters Stefan Berger
2024-02-15 23:14 ` [PATCH v2 03/14] crypto: ecdsa - Extend res.x mod n calculation for NIST P521 Stefan Berger
2024-02-15 23:14 ` [PATCH v2 04/14] crypto: ecc - Implement vli_mmod_fast_521 for NIST p521 Stefan Berger
2024-02-15 23:14 ` [PATCH v2 05/14] crypto: ecc - For NIST P521 use vli_num_bits to get number of bits Stefan Berger
2024-02-15 23:14 ` [PATCH v2 06/14] crypto: ecc - Add NIST P521 curve parameters Stefan Berger
2024-02-16 18:48 ` Elliott, Robert (Servers)
2024-02-16 19:03 ` Stefan Berger
2024-02-15 23:14 ` [PATCH v2 07/14] crypto: ecdsa - Register NIST P521 and extend test suite Stefan Berger
2024-02-15 23:14 ` [PATCH v2 08/14] x509: Add OID for NIST P521 and extend parser for it Stefan Berger
2024-02-15 23:14 ` [PATCH v2 09/14] crypto: ecdh - Use properly formatted digits to check for valid key Stefan Berger
2024-02-15 23:14 ` [PATCH v2 10/14] crypto: ecc - Implement ecc_digits_to_bytes to convert digits to byte array Stefan Berger
2024-02-15 23:14 ` [PATCH v2 11/14] crypto: Add nbits field to ecc_curve structure Stefan Berger
2024-02-15 23:14 ` [PATCH v2 12/14] crypto: ecc - Implement and use ecc_curve_get_nbytes to get curve's nbytes Stefan Berger
2024-02-15 23:14 ` [PATCH v2 13/14] crypto: ecdh - Use functions to copy digits from and to byte array Stefan Berger
2024-02-15 23:14 ` [PATCH v2 14/14] crypto: ecdh - Add support for NIST P521 and add test case Stefan Berger
2024-02-16 19:27 ` [PATCH v2 00/14] Add support for NIST P521 to ecdsa and ecdh Simo Sorce
2024-02-16 19:32 ` Stefan Berger [this message]
2024-02-16 19:40 ` Simo Sorce
2024-02-19 14:40 ` Stefan Berger
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=b507fd52-a807-4325-981b-3852f4f6190b@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saulo.alessandre@tse.jus.br \
--cc=simo@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®