From: Arun Iyengar via B4 Relay <devnull+aiyengar1990.gmail.com@kernel.org>
To: Lukas Wunner <lukas@wunner.de>, Ignat Korchagin <ignat@linux.win>,
Stefan Berger <stefanb@linux.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Erwin Pawliczek <pawliczekerwin@gmail.com>,
Arun Iyengar <aiyengar1990@gmail.com>
Subject: [PATCH 0/2] crypto: ecc - Fix P-521 public key generation
Date: Sat, 14 Nov 2026 08:44:12 +0000 [thread overview]
Message-ID: <20261114-ecc-p521-small-scalars-v1-0-7b114f076b33@gmail.com> (raw)
Two P-521 fixes for crypto/ecc.c. Patch 1 keeps the random initial Z
from commit cd65eaf17841 below 2^521: with 576 bits, every P-521
ecc_make_pub_key() call fails with -EAGAIN. Patch 2 fixes the scalar
multiplication for scalars below about 2^259.5. No in-tree caller is
affected yet.
This series was developed with Claude (Anthropic) as a coding assistant:
it wrote the code and the commit messages. I reviewed it and tested it
as described in each patch.
---
Arun Iyengar (2):
crypto: ecc - Keep the random initial Z below 2^521 on P-521
crypto: ecc - Fix P-521 scalar multiplication for small scalars
crypto/ecc.c | 31 +++++++++++++++++++------------
1 file changed, 19 insertions(+), 12 deletions(-)
---
base-commit: 8ba9044ff0bf4a5789216496019fad614eeafd45
change-id: 20261114-ecc-p521-small-scalars-601dd880c8bb
Best regards,
--
Arun Iyengar <aiyengar1990@gmail.com>
next reply other threads:[~2026-11-14 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 8:44 Arun Iyengar via B4 Relay [this message]
2026-11-14 8:44 ` [PATCH 1/2] crypto: ecc - Keep the random initial Z below 2^521 on P-521 Arun Iyengar via B4 Relay
2026-11-14 8:44 ` [PATCH 2/2] crypto: ecc - Fix P-521 scalar multiplication for small scalars Arun Iyengar via B4 Relay
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=20261114-ecc-p521-small-scalars-v1-0-7b114f076b33@gmail.com \
--to=devnull+aiyengar1990.gmail.com@kernel.org \
--cc=aiyengar1990@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=ignat@linux.win \
--cc=jarkko@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=pawliczekerwin@gmail.com \
--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®