[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8b96c136-dca9-5b6a-2221-e906d265c40b@microchip.com>
Date: Tue, 23 Feb 2021 10:44:52 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <yumeng18@...wei.com>, <herbert@...dor.apana.org.au>,
<davem@...emloft.net>, <marcel@...tmann.org>,
<johan.hedberg@...il.com>, <luiz.dentz@...il.com>
CC: <linux-crypto@...r.kernel.org>, <xuzaibo@...wei.com>,
<wangzhou1@...ilicon.com>, <linux-kernel@...r.kernel.org>,
<Nicolas.Ferre@...rochip.com>
Subject: Re: [PATCH v9 3/7] crypto: move curve_id of ECDH from the key to
algorithm name
Hi,
On 2/23/21 9:10 AM, Meng Yu wrote:
> --- a/drivers/crypto/atmel-ecc.c
> +++ b/drivers/crypto/atmel-ecc.c
> @@ -104,7 +104,7 @@ static int atmel_ecdh_set_secret(struct crypto_kpp *tfm, const void *buf,
> return -EINVAL;
> }
>
> - ctx->n_sz = atmel_ecdh_supported_curve(params.curve_id);
> + ctx->n_sz = atmel_ecdh_supported_curve(ctx->curve_id);
> if (!ctx->n_sz || params.key_size) {
> /* fallback to ecdh software implementation */
> ctx->do_fallback = true;
Now that you moved the curve id info into the alg name, and it is
no longer dynamically discovered when decoding the key, does it
still make sense to keep the curve id, the key size checks, and
the fallback to the software implementation?
I don't have an atecc508 at hand to test the changes, but I expect
your changes won't affect the functionality.
ta
Powered by blists - more mailing lists