From: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
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, jarkko@kernel.org
Subject: Re: [PATCH] crypto: ecc - Fix off-by-one missing to clear most significant digit
Date: Fri, 14 Jun 2024 11:47:26 +0530 [thread overview]
Message-ID: <e44fab6a-8ae7-4cbc-86c6-c9a50458b0d5@linux.vnet.ibm.com> (raw)
In-Reply-To: <20240613213820.995832-1-stefanb@linux.ibm.com>
Tested with the proposed patch and issue is fixed.
Tested-by: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Regards,
Venkat.
On 14/06/24 3:08 am, Stefan Berger wrote:
> Fix an off-by-one error where the most significant digit was not
> initialized leading to signature verification failures by the testmgr.
>
> Example: If a curve requires ndigits (=9) and diff (=2) indicates that
> 2 digits need to be set to zero then start with digit 'ndigits - diff' (=7)
> and clear 'diff' digits starting from there, so 7 and 8.
>
> Reported-by: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
> Closes: https://lore.kernel.org/linux-crypto/619bc2de-b18a-4939-a652-9ca886bf6349@linux.ibm.com/T/#m045d8812409ce233c17fcdb8b88b6629c671f9f4
> Fixes: 2fd2a82ccbfc ("crypto: ecdsa - Use ecc_digits_from_bytes to create hash digits array")
> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> ---
> crypto/ecc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/crypto/ecc.c b/crypto/ecc.c
> index fe761256e335..dd48d9928a21 100644
> --- a/crypto/ecc.c
> +++ b/crypto/ecc.c
> @@ -78,7 +78,7 @@ void ecc_digits_from_bytes(const u8 *in, unsigned int nbytes,
> /* diff > 0: not enough input bytes: set most significant digits to 0 */
> if (diff > 0) {
> ndigits -= diff;
> - memset(&out[ndigits - 1], 0, diff * sizeof(u64));
> + memset(&out[ndigits], 0, diff * sizeof(u64));
> }
>
> if (o) {
next prev parent reply other threads:[~2024-06-14 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 21:38 Stefan Berger
2024-06-14 6:17 ` Venkat Rao Bagalkote [this message]
2024-06-16 5:59 ` 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=e44fab6a-8ae7-4cbc-86c6-c9a50458b0d5@linux.vnet.ibm.com \
--to=venkat88@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®