public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 3/3] lib: rsa: Update function padding_pss_verify (any-salt)
Date: Wed,  9 Mar 2022 01:27:17 -0800	[thread overview]
Message-ID: <20220309092717.4203-4-gioja.hermann@non.se.com> (raw)
In-Reply-To: <20220309092717.4203-1-gioja.hermann@non.se.com>

Modify function to support any salt length instead of max
length only. Function now detects salt length by parsing
the content of db buffer. Note that it works with (but is
not limited to) zero-length, digest-length and max-length

Signed-off-by: SESA644425 <gioja.hermann@non.se.com>
---
Despite checkpath.pl recommendation, it is not possible to use u8 instead
of uint8_t. Proceeding with u8 breaks build with error: unknown type name u8
 lib/rsa/rsa-verify.c | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/lib/rsa/rsa-verify.c b/lib/rsa/rsa-verify.c
index de71234cfb..1d95cfbdee 100644
--- a/lib/rsa/rsa-verify.c
+++ b/lib/rsa/rsa-verify.c
@@ -204,9 +204,7 @@ out:
 /*
  * padding_pss_verify() - verify the pss padding of a signature
  *
- * Only works with a rsa_pss_saltlen:-2 (default value) right now
- * saltlen:-1 "set the salt length to the digest length" is currently
- * not supported.
+ * Works with any salt length
  *
  * msg is a concatenation of : masked_db + h + 0xbc
  * Once unmasked, db is a concatenation of : [0x00]* + 0x01 + salt
@@ -229,8 +227,8 @@ int padding_pss_verify(struct image_sign_info *info,
 	const uint8_t *h = NULL;
 	uint8_t *hprime = NULL;
 	int h_len = hash_len;
-	uint8_t	*salt = NULL;
-	int salt_len = msg_len - hash_len - 2;
+	uint8_t *db_nopad = NULL, *salt = NULL;
+	int db_padlen, salt_len;
 	uint8_t pad_zero[8] = { 0 };
 	int ret, i, leftmost_bits = 1;
 	uint8_t leftmost_mask;
@@ -277,15 +275,20 @@ int padding_pss_verify(struct image_sign_info *info,
 	db[0] &= 0xff >> leftmost_bits;
 
 	/* step 10 */
-	if (db[0] != 0x01) {
+	db_padlen = 0;
+	while (db[db_padlen] == 0x00 && db_padlen < (db_len - 1))
+		db_padlen++;
+	db_nopad = &db[db_padlen];
+	if (db_nopad[0] != 0x01) {
 		printf("%s: invalid pss padding ", __func__);
-		printf("(leftmost byte of db isn't 0x01)\n");
+		printf("(leftmost byte of db after 0-padding isn't 0x01)\n");
 		ret = EINVAL;
 		goto out;
 	}
 
 	/* step 11 */
-	salt = &db[1];
+	salt_len = db_len - db_padlen - 1;
+	salt = &db_nopad[1];
 
 	/* step 12 & 13 */
 	compute_hash_prime(checksum, pad_zero, 8,
-- 
2.25.1


  parent 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 [PATCH 0/3] Support any-salt for padding pss verification SESA644425
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 ` SESA644425 [this message]
2022-03-12  2:43   ` [PATCH 3/3] lib: rsa: Update function padding_pss_verify (any-salt) 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-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox