From: Alexandru Gagniuc <mr.nuke.me@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 0/6] nable ECDSA FIT verification for stm32mp
Date: Thu, 15 Apr 2021 15:05:03 -0500 [thread overview]
Message-ID: <20210415200509.2335046-1-mr.nuke.me@gmail.com> (raw)
This series is Part II of the ECDSA saga. It applies on top of [1]:
* [PATCH v7 00/11] Add support for ECDSA image signing
Changes since v3:
- Remove unused ecdsa_check_key() function
Changes since v2:
- Spell out "elliptic curve" in Kconfig (Although RSA isn't spelled out)
Changes since v1:
- Add test to make sure the UCLASS is enabled
- Fix check against wrong sig_len in ecdsa_romapi.c
- s/U_BOOT_DEVICE/U_BOOT_DRVINFO/
- Use "if(!ret)" instead of "if (ret == 0)"
- Use uclass_first_device_err() instead of uclass_first_device()
- Make sure #includes are correctly alphabetized
Alexandru Gagniuc (6):
dm: crypto: Define UCLASS API for ECDSA signature verification
lib: ecdsa: Add skeleton to implement ecdsa verification in u-boot
lib: ecdsa: Implement signature verification for crypto_algo API
arm: stm32mp1: Implement ECDSA signature verification
Kconfig: FIT_SIGNATURE should not select RSA_VERIFY
test: dm: Add test for ECDSA UCLASS support
arch/arm/mach-stm32mp/Kconfig | 9 ++
arch/arm/mach-stm32mp/Makefile | 1 +
arch/arm/mach-stm32mp/ecdsa_romapi.c | 102 +++++++++++++++++++++
common/Kconfig.boot | 8 +-
configs/sandbox_defconfig | 2 +
include/crypto/ecdsa-uclass.h | 39 ++++++++
include/dm/uclass-id.h | 1 +
include/image.h | 10 +--
include/u-boot/rsa.h | 2 +-
lib/Kconfig | 1 +
lib/Makefile | 1 +
lib/ecdsa/Kconfig | 23 +++++
lib/ecdsa/Makefile | 1 +
lib/ecdsa/ecdsa-verify.c | 128 +++++++++++++++++++++++++++
test/dm/Makefile | 1 +
test/dm/ecdsa.c | 38 ++++++++
16 files changed, 357 insertions(+), 10 deletions(-)
create mode 100644 arch/arm/mach-stm32mp/ecdsa_romapi.c
create mode 100644 include/crypto/ecdsa-uclass.h
create mode 100644 lib/ecdsa/Kconfig
create mode 100644 lib/ecdsa/Makefile
create mode 100644 lib/ecdsa/ecdsa-verify.c
create mode 100644 test/dm/ecdsa.c
--
2.26.3
next reply other threads:[~2021-04-15 20:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 20:05 Alexandru Gagniuc [this message]
2021-04-15 20:05 ` [PATCH v4 1/6] dm: crypto: Define UCLASS API for ECDSA signature verification Alexandru Gagniuc
2021-04-21 7:15 ` Simon Glass
2021-04-15 20:05 ` [PATCH v4 2/6] lib: ecdsa: Add skeleton to implement ecdsa verification in u-boot Alexandru Gagniuc
2021-04-21 7:15 ` Simon Glass
2021-04-21 19:30 ` Alex G.
2021-04-22 23:55 ` Simon Glass
2021-04-23 0:47 ` Tom Rini
2021-04-24 4:56 ` Simon Glass
2021-04-26 14:21 ` Alex G.
2021-04-29 16:10 ` Simon Glass
2021-05-04 16:58 ` Simon Glass
2021-05-05 17:49 ` Alex G.
2021-05-05 18:43 ` Simon Glass
2021-05-05 18:56 ` Alex G.
2021-04-15 20:05 ` [PATCH v4 3/6] lib: ecdsa: Implement signature verification for crypto_algo API Alexandru Gagniuc
2021-04-15 20:05 ` [PATCH v4 4/6] arm: stm32mp1: Implement ECDSA signature verification Alexandru Gagniuc
2021-04-15 20:05 ` [PATCH v4 5/6] Kconfig: FIT_SIGNATURE should not select RSA_VERIFY Alexandru Gagniuc
2021-04-15 20:05 ` [PATCH v4 6/6] test: dm: Add test for ECDSA UCLASS support Alexandru Gagniuc
2021-04-21 7:15 ` Simon Glass
2021-04-21 7:14 ` [PATCH v4 0/6] nable ECDSA FIT verification for stm32mp Simon Glass
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=20210415200509.2335046-1-mr.nuke.me@gmail.com \
--to=mr.nuke.me@gmail.com \
--cc=u-boot@lists.denx.de \
/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