From: Mimi Zohar <zohar@linux.ibm.com>
To: Yeoreum Yun <yeoreum.yun@arm.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org
Cc: paul@paul-moore.com, roberto.sassu@huaweicloud.com,
noodles@earth.li, jarkko@kernel.org, sudeep.holla@kernel.org,
jmorris@namei.org, serge@hallyn.com, dmitry.kasatkin@gmail.com,
eric.snowberg@oracle.com, jgg@ziepe.ca,
Jonathan McDowell <noodles@meta.com>
Subject: Re: [PATCH v5 3/4] security: ima: rename boot_aggregate when ima is initialised at late_sync
Date: Tue, 02 Jun 2026 08:34:46 -0400 [thread overview]
Message-ID: <5c52effb1b4723c025f478c1c902bf83a9a4d0ed.camel@linux.ibm.com> (raw)
In-Reply-To: <20260601142749.3379697-4-yeoreum.yun@arm.com>
On Mon, 2026-06-01 at 15:27 +0100, Yeoreum Yun wrote:
> From: Jonathan McDowell <noodles@meta.com>
>
> The Linux IMA (Integrity Measurement Architecture) subsystem used for
> secure boot, file integrity, or remote attestation cannot be a loadable
> module for few reasons listed below:
>
> o Boot-Time Integrity: IMA’s main role is to measure and appraise files
> before they are used. This includes measuring critical system files
> during early boot (e.g., init, init scripts, login binaries). If IMA
> were a module, it would be loaded too late to cover those.
>
> o TPM Dependency: IMA integrates tightly with the TPM to record
> measurements into PCRs. The TPM must be initialized early (ideally
> before init_ima()), which aligns with IMA being built-in.
>
> o Security Model: IMA is part of a Trusted Computing Base (TCB). Making
> it a module would weaken the security model, as a potentially
> compromised system could delay or tamper with its initialization.
>
> IMA must be built-in to ensure it starts measuring from the earliest
> possible point in boot which inturn implies TPM must be initialised and
> ready to use before IMA.
>
> Unfortunately some TPM drivers (such as Arm FF-A, or SPI attached TPM
> devices) are not reliably available during the initcall_late stage,
> resulting in a log error:
>
> ima: No TPM chip found, activating TPM-bypass!
>
> To address this issue, IMA_INIT_LATE_SYNC is introduced.
> However, a remote attestation service cannot determine when IMA has been
> initialized because the boot_aggregate measurement name remains unchanged,
> even though IMA is initialized later at late_initcall_sync when
> IMA_INIT_LATE_SYNC is enabled.
>
> Therefore, use a distinct boot_aggregate name when IMA_INIT_LATE_SYNC
> is enabled, allowing the remote attestation service to identify
> when IMA has been initialized.
>
> Signed-off-by: Jonathan McDowell <noodles@meta.com>
> [yeoreum.yun@arm.com: modified to align with the IMA_INIT_LATE_SYNC change]
Thanks, Yeoreum. This version requires your Signed-off-by tag as well as
Jonathan's. Otherwise the patch looks good.
Mimi
next prev parent reply other threads:[~2026-06-02 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 14:27 [PATCH v5 0/4] introduce IMA_INIT_LATE_SYNC option Yeoreum Yun
2026-06-01 14:27 ` [PATCH v5 1/4] security: lsm: allow LSMs to register for late_initcall_sync init Yeoreum Yun
2026-06-01 14:27 ` [PATCH v5 2/4] security: ima: introduce IMA_INIT_LATE_SYNC option Yeoreum Yun
2026-06-02 12:35 ` Mimi Zohar
2026-06-02 12:58 ` Yeoreum Yun
2026-06-01 14:27 ` [PATCH v5 3/4] security: ima: rename boot_aggregate when ima is initialised at late_sync Yeoreum Yun
2026-06-02 12:34 ` Mimi Zohar [this message]
2026-06-02 12:58 ` Yeoreum Yun
2026-06-01 14:27 ` [PATCH v5 4/4] tpm: tpm_crb_ffa: revert defered_probed when tpm_crb_ffa is built-in Yeoreum Yun
2026-06-02 2:29 ` Jarkko Sakkinen
2026-06-02 12:56 ` Yeoreum Yun
2026-06-02 12:57 ` Yeoreum Yun
2026-06-08 4:01 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c52effb1b4723c025f478c1c902bf83a9a4d0ed.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=noodles@earth.li \
--cc=noodles@meta.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=serge@hallyn.com \
--cc=sudeep.holla@kernel.org \
--cc=yeoreum.yun@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome