* [U-Boot] [PATCH] doc: verified-boot: fix crypto algorithm examples
@ 2017-10-19 10:37 Masahiro Yamada
2017-10-22 14:36 ` Simon Glass
2017-10-24 18:15 ` [U-Boot] " Tom Rini
0 siblings, 2 replies; 3+ messages in thread
From: Masahiro Yamada @ 2017-10-19 10:37 UTC (permalink / raw)
To: u-boot
As you see in crypto_algos in common/image-sig.c, the algorithm
should be either "rsa2048" or "rsa4096". "rs2048" is a typo.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
---
doc/uImage.FIT/signature.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/uImage.FIT/signature.txt b/doc/uImage.FIT/signature.txt
index a57cdab..2ece4c4 100644
--- a/doc/uImage.FIT/signature.txt
+++ b/doc/uImage.FIT/signature.txt
@@ -85,7 +85,7 @@ allow the signer to operate. These should be added to the .its file.
Signature nodes sit at the same level as hash nodes and are called
signature at 1, signature at 2, etc.
-- algo: Algorithm name (e.g. "sha1,rs2048")
+- algo: Algorithm name (e.g. "sha1,rsa2048")
- key-name-hint: Name of key to use for signing. The keys will normally be in
a single directory (parameter -k to mkimage). For a given key <name>, its
@@ -139,7 +139,7 @@ public key in U-Boot's control FDT (using CONFIG_OF_CONTROL).
Public keys should be stored as sub-nodes in a /signature node. Required
properties are:
-- algo: Algorithm name (e.g. "sha1,rs2048")
+- algo: Algorithm name (e.g. "sha1,rsa2048")
Optional properties are:
--
2.7.4
^ permalink raw reply related [flat|nested] 3+ messages in thread
* [U-Boot] [PATCH] doc: verified-boot: fix crypto algorithm examples
2017-10-19 10:37 [U-Boot] [PATCH] doc: verified-boot: fix crypto algorithm examples Masahiro Yamada
@ 2017-10-22 14:36 ` Simon Glass
2017-10-24 18:15 ` [U-Boot] " Tom Rini
1 sibling, 0 replies; 3+ messages in thread
From: Simon Glass @ 2017-10-22 14:36 UTC (permalink / raw)
To: u-boot
On 19 October 2017 at 12:37, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> As you see in crypto_algos in common/image-sig.c, the algorithm
> should be either "rsa2048" or "rsa4096". "rs2048" is a typo.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> doc/uImage.FIT/signature.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Simon Glass <sjg@chromium.org>
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot] doc: verified-boot: fix crypto algorithm examples
2017-10-19 10:37 [U-Boot] [PATCH] doc: verified-boot: fix crypto algorithm examples Masahiro Yamada
2017-10-22 14:36 ` Simon Glass
@ 2017-10-24 18:15 ` Tom Rini
1 sibling, 0 replies; 3+ messages in thread
From: Tom Rini @ 2017-10-24 18:15 UTC (permalink / raw)
To: u-boot
On Thu, Oct 19, 2017 at 07:37:59PM +0900, Masahiro Yamada wrote:
> As you see in crypto_algos in common/image-sig.c, the algorithm
> should be either "rsa2048" or "rsa4096". "rs2048" is a typo.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.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: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171024/9742b9b9/attachment.sig>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-10-24 18:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-19 10:37 [U-Boot] [PATCH] doc: verified-boot: fix crypto algorithm examples Masahiro Yamada
2017-10-22 14:36 ` Simon Glass
2017-10-24 18:15 ` [U-Boot] " Tom Rini
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.