From: Claudius Heine <ch@denx.de>
To: Marek Vasut <marex@denx.de>, Peng Fan <peng.fan@nxp.com>,
Fabio Estevam <festevam@denx.de>,
Tim Harvey <tharvey@gateworks.com>, Claudius Heine <ch@denx.de>,
u-boot@lists.denx.de (open list)
Subject: [PATCH] imx: hab: add documentation about the required keys/certs
Date: Tue, 7 May 2024 15:06:50 +0200 [thread overview]
Message-ID: <20240507130650.713801-1-ch@denx.de> (raw)
In-Reply-To: <20240503010518.263458-1-marex@denx.de>
For CST to find the certificates and keys for signing, some keys and
certs need to be copied into the u-boot build directory.
Signed-off-by: Claudius Heine <ch@denx.de>
---
doc/imx/habv4/guides/mx8m_spl_secure_boot.txt | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/doc/imx/habv4/guides/mx8m_spl_secure_boot.txt b/doc/imx/habv4/guides/mx8m_spl_secure_boot.txt
index ce1de659d8..42214df21a 100644
--- a/doc/imx/habv4/guides/mx8m_spl_secure_boot.txt
+++ b/doc/imx/habv4/guides/mx8m_spl_secure_boot.txt
@@ -144,6 +144,22 @@ The signing is activated by wrapping SPL and fitImage sections into nxp-imx8mcst
etype, which is done automatically in arch/arm/dts/imx8m{m,n,p,q}-u-boot.dtsi
in case CONFIG_IMX_HAB Kconfig symbol is enabled.
+Per default the HAB keys and certificates need to be located in the build
+directory, this means copying the following files from the HAB keys directory
+flat (e.g. removing the `keys` and `cert` subdirectory) into the u-boot build
+directory for the CST Code Signing Tool to locate them:
+
+- `crts/SRK_1_2_3_4_table.bin`
+- `crts/CSF1_1_sha256_4096_65537_v3_usr_crt.pem`
+- `keys/CSF1_1_sha256_4096_65537_v3_usr_key.pem`
+- `crts/IMG1_1_sha256_4096_65537_v3_usr_crt.pem`
+- `keys/IMG1_1_sha256_4096_65537_v3_usr_key.pem`
+- `keys/key_pass.txt`
+
+The paths to the SRK table and the certificates can be modified via changes to
+the nxp_imx8mcst device tree node, however the other files are required by the
+CST tools as well, and will be searched for in relation to them.
+
Build of flash.bin target then produces a signed flash.bin automatically.
1.4 Closing the device
--
2.42.0
next prev parent reply other threads:[~2024-05-07 13:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 1:05 [PATCH v2 1/4] binman: Add nxp_imx8mcst etype for i.MX8M flash.bin signing Marek Vasut
2024-05-03 1:05 ` [PATCH v2 2/4] ARM: dts: imx: Introduce SPL and FIT labels to i.MX8M DTs binman nodes Marek Vasut
2024-05-03 1:05 ` [PATCH v2 3/4] ARM: dts: imx: Wrap i.MX8M binman SPL and FIT nodes in CST node if IMX_HAB enabled Marek Vasut
2024-05-03 1:05 ` [PATCH v2 4/4] imx: hab: Use nxp_imx8mcst etype for i.MX8M flash.bin signing Marek Vasut
2024-05-14 18:34 ` Tim Harvey
2024-05-14 20:23 ` Marek Vasut
2024-05-15 22:16 ` Tim Harvey
2024-05-15 22:31 ` Tim Harvey
2024-05-16 1:53 ` Marek Vasut
2024-05-16 15:31 ` Tim Harvey
2024-05-06 11:52 ` [PATCH v2 1/4] binman: Add " Francesco Dolcini
2024-05-06 15:21 ` Marek Vasut
2024-05-07 13:06 ` Claudius Heine [this message]
2024-05-07 13:28 ` [PATCH] imx: hab: add documentation about the required keys/certs Marek Vasut
2024-05-08 7:23 ` Claudius Heine
2024-05-13 3:46 ` Marek Vasut
2024-05-14 18:50 ` Tim Harvey
2024-05-15 22:46 ` Tim Harvey
2024-05-16 8:25 ` Claudius Heine
2024-05-16 9:50 ` Rasmus Villemoes
2024-05-16 11:27 ` Claudius Heine
2024-05-16 8:36 ` [PATCH v2] " Claudius Heine
2024-05-18 8:30 ` Heinrich Schuchardt
2024-05-24 16:27 ` Fabio Estevam
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=20240507130650.713801-1-ch@denx.de \
--to=ch@denx.de \
--cc=festevam@denx.de \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=tharvey@gateworks.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