public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Stefan Berger" <stefanb@linux.ibm.com>,
	"Lukas Wunner" <lukas@wunner.de>
Cc: <keyrings@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
	<herbert@gondor.apana.org.au>, <davem@davemloft.net>,
	<linux-kernel@vger.kernel.org>, <saulo.alessandre@tse.jus.br>
Subject: Re: [PATCH v3 01/10] crypto: ecdsa - Convert byte arrays with key coordinates to digits
Date: Fri, 01 Mar 2024 22:51:46 +0200	[thread overview]
Message-ID: <CZIPLSJ3HA9K.LUY0REGO0GAH@suppilovahvero> (raw)
In-Reply-To: <8d33a745-ac77-4965-8d1d-35061b027f33@linux.ibm.com>

On Fri Mar 1, 2024 at 10:48 PM EET, Stefan Berger wrote:
>
>
> On 3/1/24 15:26, Jarkko Sakkinen wrote:
> > On Thu Feb 29, 2024 at 4:57 PM EET, Stefan Berger wrote:
> >>
> >>
> >> On 2/29/24 04:11, Lukas Wunner wrote:
> >>> On Fri, Feb 23, 2024 at 03:41:40PM -0500, Stefan Berger wrote:
> >>>> +static inline void ecc_digits_from_bytes(const u8 *in, unsigned int nbytes,
> >>>> +					 u64 *out, unsigned int ndigits)
> >>>> +{
> >>>> +	unsigned int sz = ndigits << ECC_DIGITS_TO_BYTES_SHIFT;
> >>>> +	u8 tmp[ECC_MAX_DIGITS << ECC_DIGITS_TO_BYTES_SHIFT];
> >>>> +	unsigned int o = sz - nbytes;
> >>>> +
> >>>> +	memset(tmp, 0, o);
> >>>> +	memcpy(&tmp[o], in, nbytes);
> >>>> +	ecc_swap_digits(tmp, out, ndigits);
> >>>> +}
> >>>
> >>> Copying the whole key into tmp seems inefficient.  You only need
> >>> special handling for the first few bytes of "in" (6 bytes in the
> >>> P521 case) and could use ecc_swap_digits() to convert the rest
> >>> of "in" directly to "out" without using tmp.
> >>>
> >>> So it would be sufficient to allocate the first digit on the stack,
> >>> memset + memcpy, then convert that to native byte order into "in[0]"
> >>> and use ecc_swap_digits() for the rest.
> >>>
> >>> And the special handling would be conditional on "!o", so is skipped
> >>> for existing curves.
> >>
> >> Thanks. It looks like this now:
> >>
> >> static inline void ecc_digits_from_bytes(const u8 *in, unsigned int nbytes,
> >>                                            u64 *out, unsigned int ndigits)
> >> {
> >>           unsigned int o = nbytes & 7;
> >>           u64 msd = 0;
> >>           size_t i;
> >>
> >>           if (o == 0) {
> >>                   ecc_swap_digits(in, out, ndigits);
> >>           } else {
> >>                   for (i = 0; i < o; i++)
> >>                           msd = (msd << 8) | in[i];
> >>                   out[ndigits - 1] = msd;
> >>                   ecc_swap_digits(&in[o], out, ndigits - 1);
> > 
> > This would be more stream-lined IMHO:
> > 
> >          unsigned int o = nbytes & 7;
> > 	unsigned int n = ndigits;
> >          u64 msd = 0;
> >          size_t i;
> > 
> >          if (o != 0) {
> >                  for (i = 0; i < o; i++)
> >                          msd = (msd << 8) | in[i];
> > 
> >                  out[--n] = msd;
> >          }
> > 
> >          ecc_swap_digits(in, out, n);
>
> You forgot to advance 'in'.

yeah, pointing out that two call sites is unnecessary complexity, that's
all

BR, Jarkko

  reply	other threads:[~2024-03-01 20:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 20:41 [PATCH v3 00/10] Add support for NIST P521 to ecdsa Stefan Berger
2024-02-23 20:41 ` [PATCH v3 01/10] crypto: ecdsa - Convert byte arrays with key coordinates to digits Stefan Berger
2024-02-29  9:11   ` Lukas Wunner
2024-02-29 14:57     ` Stefan Berger
2024-02-29 16:48       ` Lukas Wunner
2024-02-29 17:20         ` Stefan Berger
2024-03-01 20:26       ` Jarkko Sakkinen
2024-03-01 20:48         ` Stefan Berger
2024-03-01 20:51           ` Jarkko Sakkinen [this message]
2024-03-02 14:00         ` Lukas Wunner
2024-03-02 21:19           ` Stefan Berger
2024-03-02 21:36             ` Lukas Wunner
2024-03-02 21:55           ` Jarkko Sakkinen
2024-02-23 20:41 ` [PATCH v3 02/10] crypto: ecdsa - Adjust tests on length of key parameters Stefan Berger
2024-02-29  9:16   ` Lukas Wunner
2024-02-29 20:28     ` Stefan Berger
2024-02-23 20:41 ` [PATCH v3 03/10] crypto: ecdsa - Extend res.x mod n calculation for NIST P521 Stefan Berger
2024-02-23 20:41 ` [PATCH v3 04/10] crypto: ecc - Implement vli_mmod_fast_521 for NIST p521 Stefan Berger
2024-02-23 20:41 ` [PATCH v3 05/10] crypto: ecc - Add nbits field to ecc_curve structure Stefan Berger
2024-02-23 20:41 ` [PATCH v3 06/10] crypte: ecc - Implement ecc_curve_get_nbits to get number of bits Stefan Berger
2024-02-27 20:15   ` Lukas Wunner
2024-02-29 20:29     ` Stefan Berger
2024-02-23 20:41 ` [PATCH v3 07/10] crypto: ecc - Use ecc_get_curve_nbits to get number of bits for NIST P521 Stefan Berger
2024-02-23 20:41 ` [PATCH v3 08/10] crypto: ecc - Add NIST P521 curve parameters Stefan Berger
2024-02-23 20:41 ` [PATCH v3 09/10] crypto: ecdsa - Register NIST P521 and extend test suite Stefan Berger
2024-02-23 20:41 ` [PATCH v3 10/10] x509: Add OID for NIST P521 and extend parser for it Stefan Berger
2024-02-29  9:34 ` [PATCH v3 00/10] Add support for NIST P521 to ecdsa Lukas Wunner
2024-02-29 18:45   ` 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=CZIPLSJ3HA9K.LUY0REGO0GAH@suppilovahvero \
    --to=jarkko@kernel.org \
    --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=lukas@wunner.de \
    --cc=saulo.alessandre@tse.jus.br \
    --cc=stefanb@linux.ibm.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