From: Thirupathaiah Annapureddy <thiruan@linux.microsoft.com>
To: u-boot@lists.denx.de
Subject: [PATCH v3 3/3] doc: verified-boot: add required-mode information
Date: Sun, 16 Aug 2020 23:01:11 -0700 [thread overview]
Message-ID: <c78de38d257b732b0a3b3f810420764fdcaa9bdd.1597643014.git.thiruan@linux.microsoft.com> (raw)
In-Reply-To: <cover.1597643014.git.thiruan@linux.microsoft.com>
Add documentation about 'required-mode' property in /signature node
in U-Boot's control FDT.
Signed-off-by: Thirupathaiah Annapureddy <thiruan@linux.microsoft.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
---
Changes in v3:
- Added commit description to address checkpatch warning.
Changes in v2:
- New.
doc/uImage.FIT/signature.txt | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/doc/uImage.FIT/signature.txt b/doc/uImage.FIT/signature.txt
index d4afd755e9..a3455889ed 100644
--- a/doc/uImage.FIT/signature.txt
+++ b/doc/uImage.FIT/signature.txt
@@ -386,6 +386,20 @@ that might be used by the target needs to be signed with 'required' keys.
This happens automatically as part of a bootm command when FITs are used.
+For Signed Configurations, the default verification behavior can be changed by
+the following optional property in /signature node in U-Boot's control FDT.
+
+- required-mode: Valid values are "any" to allow verified boot to succeed if
+the selected configuration is signed by any of the 'required' keys, and "all"
+to allow verified boot to succeed if the selected configuration is signed by
+all of the 'required' keys.
+
+This property can be added to a binary device tree using fdtput as shown in
+below examples::
+
+ fdtput -t s control.dtb /signature required-mode any
+ fdtput -t s control.dtb /signature required-mode all
+
Enabling FIT Verification
-------------------------
--
2.25.2
next prev parent reply other threads:[~2020-08-17 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 6:01 [PATCH v3 0/3] Add support for multiple required keys Thirupathaiah Annapureddy
2020-08-17 6:01 ` [PATCH v3 1/3] vboot: add DTB policy for supporting multiple required conf keys Thirupathaiah Annapureddy
2020-10-13 14:06 ` Tom Rini
2020-08-17 6:01 ` [PATCH v3 2/3] test: vboot: add tests for multiple required keys Thirupathaiah Annapureddy
2020-10-13 14:06 ` Tom Rini
2020-08-17 6:01 ` Thirupathaiah Annapureddy [this message]
2020-10-13 14:06 ` [PATCH v3 3/3] doc: verified-boot: add required-mode information 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=c78de38d257b732b0a3b3f810420764fdcaa9bdd.1597643014.git.thiruan@linux.microsoft.com \
--to=thiruan@linux.microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).