All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: SESA644425 <giojahermann@gmail.com>
Cc: sjg@chromium.org, 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
Subject: Re: [PATCH 3/3] lib: rsa: Update function padding_pss_verify (any-salt)
Date: Mon, 11 Apr 2022 16:14:20 -0400	[thread overview]
Message-ID: <20220411201420.GR14282@bill-the-cat> (raw)
In-Reply-To: <20220309092717.4203-4-gioja.hermann@non.se.com>

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

On Wed, Mar 09, 2022 at 01:27:17AM -0800, SESA644425 wrote:

> 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>
> Reviewed-by: Simon Glass <sjg@chromium.org>

Applied to u-boot/master, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2022-04-11 20:14 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 ` [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 [this message]

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=20220411201420.GR14282@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=gioja.hermann@non.se.com \
    --cc=giojahermann@gmail.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.