Repository navigation
Conversation
EVE does not use the Integrity Measurement Architecture: it loads no IMA policy, puts no ima_* parameter on the kernel command line, and nothing in the rootfs reads the measurement list. core and rt never enabled it; hwe and ai inherited CONFIG_IMA=y from the Ubuntu HWE derivation. IMA is not idle there either. On a Secure Boot host IMA_ARCH_POLICY installs arch rules that measure every module and kexec kernel load into PCR 10, and turns on kexec signature enforcement through set_kexec_sig_enforced(). EVM goes with it. Its verdict on a file's security xattrs is consumed by IMA appraisal, and it needs an evm-key that EVE never loads, so without IMA it protects nothing. eve-hwe_defconfig is regenerated with savedefconfig, as in commit 92df24b ("configs: drop CONFIG_XEN from the EVE defconfigs"). TCG_TPM, TCG_TIS, TCG_CRB, ENCRYPTED_KEYS and CRYPTO_SHA1 were =y only through IMA's and EVM's select; they stay =y, and savedefconfig now lists them explicitly. Beyond that, the resolved hwe and ai .config loses only IMA_* and EVM_* symbols. core and rt resolve to an identical .config. common.fragment pins both off, so a future re-derivation from Ubuntu cannot bring them back on any flavour. Signed-off-by: Mikhail Malyshev <mike.malyshev@gmail.com>
rucoder
force-pushed
the
mikem/no-ima-6.18.55
branch
from
November 6, 2026 14:35
3aed289 to
1e3f8ed
Compare
eriknordmark
approved these changes
Nov 8, 2026
eriknordmark
left a comment
Contributor
There was a problem hiding this comment.
LGTM. One more reason this matters: EVE seals the vault key to PCR 10. DefaultDiskKeySealingPCRs in pkg/pillar/evetpm/tpm.go selects PCRs 0-15 except 5 and 15.
With IMA on, PCR 10 receives the boot_aggregate entry even with no policy loaded, and that digest covers PCRs 0-9, including PCR 5, which EVE excludes because GPT attribute changes (e.g. inprogress -> active after an upgrade) move it. So on hwe/ai EVE-k devices a GPT flip can break local unseal and force the controller backup-key path, and under Secure Boot the MODULE_CHECK measurements can make PCR 10 differ on every boot. Dropping IMA removes both.
rucoder
merged commit Nov 9, 2026
2a84923
into
lf-edge:eve-kernel-amd64-v6.18.55-generic
5 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR removes IMA (Integrity Measurement Architecture) and its companion EVM (Extended Verification Module) from every kernel flavour:
core,rt,hweandai.coreandrtalready build without them.hweandaiinheritedCONFIG_IMA=yandCONFIG_EVM=yfrom the Ubuntu HWE derivation ineve-hwe_defconfig.Why
EVE does not use IMA. It loads no IMA policy, puts no
ima_*parameter on the kernel command line, and nothing in the rootfs reads the measurement list.IMA is not idle in
hweandai, though. On a Secure Boot host,IMA_ARCH_POLICYinstalls arch rules (security/integrity/ima/ima_efi.c) that:set_kexec_sig_enforced().EVM only produces a verdict on a file's security xattrs for IMA appraisal to consume. It also needs an
evm-keythat EVE never loads, so without IMA it protects nothing.How
eve-hwe_defconfigis regenerated withsavedefconfigwith IMA and EVM disabled, as in 92df24b ("configs: drop CONFIG_XEN from the EVE defconfigs").TCG_TPM,TCG_TIS,TCG_CRB,ENCRYPTED_KEYSandCRYPTO_SHA1were=yonly because IMA and EVM selected them, sosavedefconfighad left them out.=yand are now listed explicitly. Deleting the IMA lines by hand would have turned off built-in TPM support.common.fragmentpins# CONFIG_IMA is not setand# CONFIG_EVM is not set, so a future re-derivation from Ubuntu cannot bring them back on any flavour.Validation
All of this is config resolution only, with no kernel compile; CI builds every flavour.
eve-hwe_defconfigandeve-core_defconfigbyte for byte, so the regenerated defconfig has no toolchain noise..configwas resolved the wayDockerfile.gccdoes it: base defconfig, then each fragment throughmerge_config.sh, thenolddefconfig. Diffs of before against after withscripts/diffconfig:coreandrt: identical (rtwas resolved without the RT patch, which does not touch IMA);hwe(and soai, which has the same config inputs): onlyIMA_*andEVM_*symbols change. TPM, keys and crypto keep their values.eve/check-config.pypasses for all four flavours, with the same results as before this change. Its unit tests also pass (43 passed).checkpatch.pl --strict: 0 errors, 0 warnings, 0 checks.Backport
None.