diff mbox series

doc: verified-boot: fix crypto algorithm examples

Message ID 1508409479-15021-1-git-send-email-yamada.masahiro@socionext.com
State Accepted
Commit 6af5520fe13d81ccd4ec4f7234a8d7a2426c2bd6
Headers show
Series doc: verified-boot: fix crypto algorithm examples | expand

Commit Message

Masahiro Yamada Oct. 19, 2017, 10:37 a.m. UTC
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(-)

Comments

Simon Glass Oct. 22, 2017, 2:36 p.m. UTC | #1
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>
Tom Rini Oct. 24, 2017, 6:15 p.m. UTC | #2
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
diff mbox series

Patch

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@1, signature@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: