From: SESA644425 <giojahermann@gmail.com>
To: sjg@chromium.org
Cc: gioja.hermann@non.se.com, mr.nuke.me@gmail.com,
jamin_lin@aspeedtech.com, xypron.glpk@gmx.de,
philippe.reynes@softathome.com, thomas.perrot@bootlin.com,
u-boot@lists.denx.de, giojahermann@gmail.com
Subject: [PATCH 0/3] Support any-salt for padding pss verification
Date: Wed, 9 Mar 2022 01:27:14 -0800 [thread overview]
Message-ID: <20220309092717.4203-1-gioja.hermann@non.se.com> (raw)
This patchset does add support for any salt length in function
padding_pss_verify which currently supports only max salt-length
option. The fix is preceded by two changes to enhance memory
consumption and const-correctness in the area of the patch.
- Hermann Gioja -
SESA644425 (3):
lib: rsa: Fix const-correctness of rsassa_pss functions
lib: rsa: Leverage existing data buffer instead of systematic copy
lib: rsa: Update function padding_pss_verify (any-salt)
include/image.h | 2 +-
include/u-boot/rsa.h | 4 +--
lib/rsa/rsa-verify.c | 64 +++++++++++++++++++++++---------------------
3 files changed, 36 insertions(+), 34 deletions(-)
base-commit: 6d3c46ed0e230d999c3f20f7fd4f3a88c03b14ca
--
2.25.1
next reply other threads:[~2022-03-09 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 9:27 SESA644425 [this message]
2022-03-09 9:27 ` [PATCH 1/3] lib: rsa: Fix const-correctness of rsassa_pss functions SESA644425
2022-03-12 2:43 ` Simon Glass
2022-04-11 20:14 ` Tom Rini
2022-03-09 9:27 ` [PATCH 2/3] lib: rsa: Leverage existing data buffer instead of systematic copy SESA644425
2022-03-12 2:43 ` Simon Glass
2022-04-11 20:14 ` Tom Rini
2022-03-09 9:27 ` [PATCH 3/3] lib: rsa: Update function padding_pss_verify (any-salt) SESA644425
2022-03-12 2:43 ` Simon Glass
2022-04-11 20:14 ` Tom Rini
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=20220309092717.4203-1-gioja.hermann@non.se.com \
--to=giojahermann@gmail.com \
--cc=gioja.hermann@non.se.com \
--cc=jamin_lin@aspeedtech.com \
--cc=mr.nuke.me@gmail.com \
--cc=philippe.reynes@softathome.com \
--cc=sjg@chromium.org \
--cc=thomas.perrot@bootlin.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.