diff options
| author | Coiby Xu <coxu@redhat.com> | 2023-07-26 10:08:05 +0800 |
|---|---|---|
| committer | Mimi Zohar <zohar@linux.ibm.com> | 2023-08-01 08:18:11 -0400 |
| commit | 56dc986a6b20b20aab1b76e0d8bff79954a00333 (patch) | |
| tree | 8dac3db48e573eea858c51945f8282e3c90d020e /security | |
| parent | f20765fdfdc2c8f47b41cb08489fdad3194a8465 (diff) | |
| download | linux-stable-56dc986a6b20b20aab1b76e0d8bff79954a00333.tar.gz linux-stable-56dc986a6b20b20aab1b76e0d8bff79954a00333.tar.bz2 linux-stable-56dc986a6b20b20aab1b76e0d8bff79954a00333.zip | |
ima: require signed IMA policy when UEFI secure boot is enabled
With commit 099f26f22f58 ("integrity: machine keyring CA
configuration"), users are able to add custom IMA CA keys via
MOK. This allows users to sign their own IMA polices without
recompiling the kernel. For the sake of security, mandate signed IMA
policy when UEFI secure boot is enabled.
Note this change may affect existing users/tests i.e users won't be able
to load an unsigned IMA policy when the IMA architecture specific policy
is configured and UEFI secure boot is enabled.
Suggested-by: Mimi Zohar <zohar@linux.ibm.com>
Signed-off-by: Coiby Xu <coxu@redhat.com>
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'security')
| -rw-r--r-- | security/integrity/ima/ima_efi.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/security/integrity/ima/ima_efi.c b/security/integrity/ima/ima_efi.c index 9db66fe310d4..138029bfcce1 100644 --- a/security/integrity/ima/ima_efi.c +++ b/security/integrity/ima/ima_efi.c @@ -58,6 +58,9 @@ static const char * const sb_arch_rules[] = { #if !IS_ENABLED(CONFIG_MODULE_SIG) "appraise func=MODULE_CHECK appraise_type=imasig", #endif +#if IS_ENABLED(CONFIG_INTEGRITY_MACHINE_KEYRING) && IS_ENABLED(CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY) + "appraise func=POLICY_CHECK appraise_type=imasig", +#endif "measure func=MODULE_CHECK", NULL }; |