From 97cfccda76e94860d72e72ecdc9f839a6d6f3057 Mon Sep 17 00:00:00 2001 From: Sascha Hauer Date: Tue, 10 May 2016 15:34:23 +0200 Subject: bootm: Add missing BOOTM_FORCE_SIGNED_IMAGES option The code already tests for this option, but it does not yet exist. Add the option to force using signed images. Signed-off-by: Sascha Hauer --- common/Kconfig | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'common/Kconfig') diff --git a/common/Kconfig b/common/Kconfig index aa257bfe3c..0be7cdab49 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -627,6 +627,15 @@ config BOOTM_FITIMAGE_SIGNATURE Additionally the barebox device tree needs a /signature node with the public key with which the image has been signed. +config BOOTM_FORCE_SIGNED_IMAGES + bool + prompt "Force booting of signed images" + depends on BOOTM_FITIMAGE_SIGNATURE + help + With this option enabled only signed images can be booted, unsigned images + are refused to boot. Effectively this means only FIT images can be booted + since they are the only supported image type that support signing. + config BLSPEC depends on BLOCK depends on FLEXIBLE_BOOTARGS -- cgit v1.2.3