From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Stefan Berger" <stefanb@linux.ibm.com>,
<keyrings@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <lukas@wunner.de>
Subject: Re: [PATCH 1/2] crypto: ecdsa - Use ecc_digits_from_bytes to create hash digits array
Date: Tue, 04 Jun 2024 19:31:33 +0300 [thread overview]
Message-ID: <D1RDKBAGB7DD.CML0Z8K8Z5KI@kernel.org> (raw)
In-Reply-To: <899c3637-dc2a-4c73-9b8a-91e7b4da1638@linux.ibm.com>
On Thu May 30, 2024 at 3:24 PM EEST, Stefan Berger wrote:
>
>
> On 5/30/24 01:28, Jarkko Sakkinen wrote:
> > On Thu May 30, 2024 at 2:08 AM EEST, Stefan Berger wrote:
> >> Since ecc_digits_from_bytes will provide zeros when an insufficient number
> >> of bytes are passed in the input byte array, use it to create the hash
> >> digits directly from the input byte array. This avoids going through an
> >> intermediate byte array (rawhash) that has the first few bytes filled with
> >> zeros.
> >>
> >> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> >> ---
> >> crypto/ecdsa.c | 17 ++++-------------
> >> 1 file changed, 4 insertions(+), 13 deletions(-)
> >>
> >> diff --git a/crypto/ecdsa.c b/crypto/ecdsa.c
> >> index 258fffbf623d..fa029f36110b 100644
> >> --- a/crypto/ecdsa.c
> >> +++ b/crypto/ecdsa.c
> >> @@ -142,10 +142,8 @@ static int ecdsa_verify(struct akcipher_request *req)
> >> struct ecdsa_signature_ctx sig_ctx = {
> >> .curve = ctx->curve,
> >> };
> >> - u8 rawhash[ECC_MAX_BYTES];
> >> u64 hash[ECC_MAX_DIGITS];
> >> unsigned char *buffer;
> >> - ssize_t diff;
> >> int ret;
> >>
> >> if (unlikely(!ctx->pub_key_set))
> >> @@ -164,18 +162,11 @@ static int ecdsa_verify(struct akcipher_request *req)
> >> if (ret < 0)
> >> goto error;
> >>
> >> - /* if the hash is shorter then we will add leading zeros to fit to ndigits */
> >> - diff = bufsize - req->dst_len;
> >> - if (diff >= 0) {
> >> - if (diff)
> >> - memset(rawhash, 0, diff);
> >> - memcpy(&rawhash[diff], buffer + req->src_len, req->dst_len);
> >> - } else if (diff < 0) {
> >> - /* given hash is longer, we take the left-most bytes */
> >> - memcpy(&rawhash, buffer + req->src_len, bufsize);
> >> - }
> >> + if (bufsize > req->dst_len)
> >> + bufsize = req->dst_len;
> >>
> >> - ecc_swap_digits((u64 *)rawhash, hash, ctx->curve->g.ndigits);
> >> + ecc_digits_from_bytes(buffer + req->src_len, bufsize,
> >> + hash, ctx->curve->g.ndigits);
> >>
> >> ret = _ecdsa_verify(ctx, hash, sig_ctx.r, sig_ctx.s);
> >>
> >
> > Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> >
> > I don't think it'd be even nit-picking to say that the function
> > called would really need kdoc. I had to spend about 20 minutes
> > to reacall ecc_digits_from_bytes().
>
> Here's the file with all the kdocs:
> https://elixir.bootlin.com/linux/v6.10-rc1/source/include/crypto/internal/ecc.h#L67
LOL, sorry I forgot this. I think this was the 2nd time I complained
about this ;-) I'm sorry, yeah that WFM.
Just not used to this convention but I don't mind actually if it is
that way.
BR, Jarkko
next prev parent reply other threads:[~2024-06-04 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 23:08 [PATCH 0/2] ecdsa: Use ecc_digits_from_bytes to simplify code Stefan Berger
2024-05-29 23:08 ` [PATCH 1/2] crypto: ecdsa - Use ecc_digits_from_bytes to create hash digits array Stefan Berger
2024-05-30 5:28 ` Jarkko Sakkinen
2024-05-30 12:24 ` Stefan Berger
2024-06-04 16:31 ` Jarkko Sakkinen [this message]
2024-05-29 23:08 ` [PATCH 2/2] crypto: ecdsa - Use ecc_digits_from_bytes to convert signature Stefan Berger
2024-05-30 5:28 ` Jarkko Sakkinen
2024-05-30 5:08 ` [PATCH 0/2] ecdsa: Use ecc_digits_from_bytes to simplify code Jarkko Sakkinen
2024-05-30 12:16 ` Stefan Berger
2024-06-04 16:30 ` Jarkko Sakkinen
2024-06-07 11:55 ` Herbert Xu
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=D1RDKBAGB7DD.CML0Z8K8Z5KI@kernel.org \
--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=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