From: Ivan Mikhaylov <fr0st61te@gmail.com>
To: Simon Glass <sjg@chromium.org>, Jan Kiszka <jan.kiszka@siemens.com>
Cc: u-boot@lists.denx.de, Ivan Mikhaylov <fr0st61te@gmail.com>
Subject: [PATCH v2 1/5] binman: add documentation for binman sign option
Date: Wed, 8 Mar 2023 01:13:38 +0000 [thread overview]
Message-ID: <20230308011342.21992-2-fr0st61te@gmail.com> (raw)
In-Reply-To: <20230308011342.21992-1-fr0st61te@gmail.com>
Add the documentation about binman sign option and providing an
example.
Signed-off-by: Ivan Mikhaylov <fr0st61te@gmail.com>
---
tools/binman/binman.rst | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst
index 0921e31878..c9d352e3ba 100644
--- a/tools/binman/binman.rst
+++ b/tools/binman/binman.rst
@@ -1330,6 +1330,24 @@ You can also replace just a selection of entries::
.. _`BinmanLogging`:
+Signing FIT container with private key in an image
+--------------------------------------------------
+
+You can sign FIT container with private key in your image.
+For example::
+
+ $ binman sign -i image.bin -k privatekey -a sha256,rsa4096 fit
+
+binman will extract FIT container, sign and replace it immediately.
+
+If you want to sign and replace FIT container in place::
+
+ $ binman sign -i image.bin -k privatekey -a sha256,rsa4096 -f fit.fit fit
+
+which will sign FIT container with private key and replace it immediately
+inside your image.
+
+
Logging
-------
--
2.39.1
next prev parent reply other threads:[~2023-03-08 13:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 1:13 [PATCH v2 0/5] Introduce new sign binman's option Ivan Mikhaylov
2023-03-08 1:13 ` Ivan Mikhaylov [this message]
2023-03-11 1:47 ` [PATCH v2 1/5] binman: add documentation for binman sign option Simon Glass
2023-03-12 17:36 ` Simon Glass
2023-03-08 1:13 ` [PATCH v2 2/5] binman: add sign option for binman Ivan Mikhaylov
2023-03-11 1:37 ` Simon Glass
2023-03-11 1:47 ` Simon Glass
2023-03-12 17:36 ` Simon Glass
2023-03-08 1:13 ` [PATCH v2 3/5] binman: add tests for sign option Ivan Mikhaylov
2023-03-11 1:47 ` Simon Glass
2023-03-11 1:48 ` Simon Glass
2023-03-12 17:36 ` Simon Glass
2023-03-08 1:13 ` [PATCH v2 4/5] tools: add fdt_add_pubkey Ivan Mikhaylov
2023-03-11 1:47 ` Simon Glass
2023-03-08 1:13 ` [PATCH v2 5/5] test_vboot.py: include test of fdt_add_pubkey tool Ivan Mikhaylov
2023-03-11 1:46 ` Simon Glass
2023-03-16 4:17 ` Ivan Mikhaylov
2023-03-16 13:59 ` Simon Glass
2023-03-16 17:45 ` Ivan Mikhaylov
2023-03-16 21:49 ` Simon Glass
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=20230308011342.21992-2-fr0st61te@gmail.com \
--to=fr0st61te@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=sjg@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox