diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2017-10-19 10:37:59 (GMT) |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2017-10-23 21:28:18 (GMT) |
| commit | 6af5520fe13d81ccd4ec4f7234a8d7a2426c2bd6 (patch) | |
| tree | d9fc07db96569ce67cd51ee8f61302ebea2b5128 | |
| parent | 16067e6b87293eeb1fc4bac3edc0fd675b94d1a8 (diff) | |
| download | u-boot-6af5520fe13d81ccd4ec4f7234a8d7a2426c2bd6.tar.xz | |
doc: verified-boot: fix crypto algorithm examples
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>
| -rw-r--r-- | doc/uImage.FIT/signature.txt | 4 |
1 files 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@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: |