From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v6 3/8] lib: rsa: bring exp_len in line when generating a key_prop
Date: Wed, 8 Jul 2020 20:23:53 -0400 [thread overview]
Message-ID: <20200709002353.GM1306@bill-the-cat> (raw)
In-Reply-To: <20200618142328.1753036-3-heiko@sntech.de>
On Thu, Jun 18, 2020 at 04:23:23PM +0200, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> The exponent field of struct key_prop gets allocated an uint64_t,
> and the contents are positioned from the back, so an exponent of
> "0x01 0x00 0x01" becomes 0x0 0x0 0x0 0x0 0x0 0x1 0x0 0x1"
>
> Right now rsa_gen_key_prop() allocates a uint64_t but sets exp_len
> to the size returned from the parser, while on the other hand the
> when getting the key from the devicetree exp_len always gets set to
> sizeof(uint64_t).
>
> So bring that in line with the established code.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200708/3bbde056/attachment.sig>
next prev parent reply other threads:[~2020-07-09 0:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 14:23 [PATCH v6 1/8] lib: rsa: distinguish between tpl and spl for CONFIG_RSA_VERIFY Heiko Stuebner
2020-06-18 14:23 ` [PATCH v6 2/8] lib: rsa: take spl/non-spl into account when building rsa_verify_with_pkey() Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
2020-07-09 0:23 ` Tom Rini
2020-06-18 14:23 ` [PATCH v6 3/8] lib: rsa: bring exp_len in line when generating a key_prop Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
2020-07-09 0:23 ` Tom Rini [this message]
2020-06-18 14:23 ` [PATCH v6 4/8] lib: rsa: fix allocated size for rr and rrtmp in rsa_gen_key_prop() Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
2020-07-07 20:05 ` Heinrich Schuchardt
2020-06-18 14:23 ` [PATCH v6 5/8] lib: rsa: free local arrays after use " Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
2020-07-09 0:23 ` Tom Rini
2020-06-18 14:23 ` [PATCH v6 6/8] lib: rsa: add documentation to padding_pss_verify to document limitations Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
2020-07-09 0:24 ` Tom Rini
2020-06-18 14:23 ` [PATCH v6 7/8] spl: fit: select SPL_HASH_SUPPORT for SPL_FIT_SIGNATURE Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
2020-07-09 0:24 ` Tom Rini
2020-06-18 14:23 ` [PATCH v6 8/8] spl: fit: select SPL_CRYPTO_SUPPORT " Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
2020-07-09 0:24 ` Tom Rini
2020-06-26 1:12 ` [PATCH v6 1/8] lib: rsa: distinguish between tpl and spl for CONFIG_RSA_VERIFY Simon Glass
2020-06-30 12:49 ` Heiko Stübner
2020-06-30 12:54 ` Heinrich Schuchardt
2020-07-09 0:23 ` 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=20200709002353.GM1306@bill-the-cat \
--to=trini@konsulko.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 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.