summaryrefslogtreecommitdiff
path: root/doc/README.JFFS2_NAND
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2013-06-13 15:10:07 -0700
committerTom Rini <trini@ti.com>2013-06-26 10:18:56 -0400
commit399c744b22459585dc2dda2cb7353b3026e28e18 (patch)
tree82c9fe00fe92fd0eea8831a8224fcad3cac09aad /doc/README.JFFS2_NAND
parent4f6104270146c76fcaf46e951f84cdc1612a04b7 (diff)
downloadu-boot-imx-399c744b22459585dc2dda2cb7353b3026e28e18.zip
u-boot-imx-399c744b22459585dc2dda2cb7353b3026e28e18.tar.gz
u-boot-imx-399c744b22459585dc2dda2cb7353b3026e28e18.tar.bz2
mkimage: Add -r option to specify keys that must be verified
Normally, multiple public keys can be provided and U-Boot is not required to use all of them for verification. This is because some images may not be signed, or may be optionally signed. But we still need a mechanism to determine when a key must be used. This feature cannot be implemented in the FIT itself, since anyone could change it to mark a key as optional. The requirement for key verification must go in with the public keys, in a place that is protected from modification. Add a -r option which tells mkimage to mark all keys that it uses for signing as 'required'. If some keys are optional and some are required, run mkimage several times (perhaps with different key directories if some keys are very secret) using the -F flag to update an existing FIT. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Marek Vasut <marex@denx.de>
Diffstat (limited to 'doc/README.JFFS2_NAND')
0 files changed, 0 insertions, 0 deletions