diff options
author | Nayna Jain <nayna@linux.ibm.com> | 2020-03-09 01:57:51 +0100 |
---|---|---|
committer | Mimi Zohar <zohar@linux.ibm.com> | 2020-03-12 12:43:57 +0100 |
commit | 9e2b4be377f0d715d9d910507890f9620cc22a9d (patch) | |
tree | b837793b54687af1ab19e7957833182399ff3d7d /security | |
parent | Merge branch 'next-integrity.logging-cleanup' into next-integrity (diff) | |
download | linux-9e2b4be377f0d715d9d910507890f9620cc22a9d.tar.xz linux-9e2b4be377f0d715d9d910507890f9620cc22a9d.zip |
ima: add a new CONFIG for loading arch-specific policies
Every time a new architecture defines the IMA architecture specific
functions - arch_ima_get_secureboot() and arch_ima_get_policy(), the IMA
include file needs to be updated. To avoid this "noise", this patch
defines a new IMA Kconfig IMA_SECURE_AND_OR_TRUSTED_BOOT option, allowing
the different architectures to select it.
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Nayna Jain <nayna@linux.ibm.com>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Acked-by: Philipp Rudo <prudo@linux.ibm.com> (s390)
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'security')
-rw-r--r-- | security/integrity/ima/Kconfig | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/security/integrity/ima/Kconfig b/security/integrity/ima/Kconfig index 3f3ee4e2eb0d..edde88dbe576 100644 --- a/security/integrity/ima/Kconfig +++ b/security/integrity/ima/Kconfig @@ -327,3 +327,10 @@ config IMA_QUEUE_EARLY_BOOT_KEYS depends on IMA_MEASURE_ASYMMETRIC_KEYS depends on SYSTEM_TRUSTED_KEYRING default y + +config IMA_SECURE_AND_OR_TRUSTED_BOOT + bool + depends on IMA_ARCH_POLICY + help + This option is selected by architectures to enable secure and/or + trusted boot based on IMA runtime policies. |