From: Baoquan He <bhe@redhat.com>
To: Coiby Xu <coxu@redhat.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>, RuiRui Yang <ruyang@redhat.com>,
linux-integrity@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [RFC PATCH] ima: add a knob to make IMA be able to be disabled
Date: Wed, 2 Apr 2025 19:49:26 +0800 [thread overview]
Message-ID: <Z+0kRhCfsjdZ53rZ@MiWiFi-R3L-srv> (raw)
In-Reply-To: <h3bjnvtded2hgbhya6ugb62mnlmkjpmifa6w6wwutfd3jq326r@lzpoun5pksev>
On 04/02/25 at 04:43pm, Coiby Xu wrote:
> On Tue, Apr 01, 2025 at 11:30:09PM -0400, Mimi Zohar wrote:
> > On Wed, 2025-04-02 at 09:47 +0800, RuiRui Yang wrote:
> [...]
> > > > > that. Please don't make it generic like this.
> > > > >
> > > > > Please refer to ima_appraise_parse_cmdline().
> > > >
> > > > Hi Mimi,
> > > >
> > > > To save memory for kdump, it seems init_ima has been to be skipped thus
> > > > ima=off is necessary (ima_appraise=off won't serve the purpose). Or do
> > > > you have any specific concerns in mind?
> > >
> > > I think as Mimi said see below logic enforces the IMA even with the
> > > cmdline disabling, see ima_appraise_parse_cmdline:
> > > if (sb_state) {
> > > if (!(appraisal_state & IMA_APPRAISE_ENFORCE))
> > > pr_info("Secure boot enabled: ignoring
> > > ima_appraise=%s option",
> > > str);
> > > } else {
> > > ima_appraise = appraisal_state;
> > > }
>
> Thanks for pointing me to the above code! Note with the whole IMA
> disabled as done by this patch, the above code will not run so IMA
> (appraisal) won't be enforced.
>
> >
> > Thanks, RuiRui.
> >
>
> Mimi, so do I understand it correctly that your want IMA-appraisal to be
> always enabled as long as secure boot is enabled even if users choose to
> disable IMA? I wonder what security issue will it bring if this promise
> gets broken considering other LSMs can SELinux can be disabled when
> secure boot is enabled?
>
> > Coiby, would disabling just IMA-measurement, as opposed to IMA-appraisal, save
> > sufficient memory for kdump?
>
> For disabling just IMA-measurement, do you mean not enabling any measure
> rules? The more memory reserved for the kdump kernel, the less memory
> can be used by the 1st kernel. So from the perfective of kdump, we try
> to make the memory footprint as smaller as possible.
>
> Baoquan, do you have any statistics about the memory overhead of IMA?
I am getting a system to check that. I think there are two aspects of
IMA functionality we want to disable. One is disable the IMA-measurement
copying from 1st kernel to 2nd kernel, this is only needed by kexec
reboot; the other is IMA is not needed at all in kdump kernel, means we
don't want to call ima_init() to initialize
ima_keyring/crypto/template/digests/fs etc.
With my shallow knowledge about IMA, I don't know how to imitate
appraisal cmdline to disable IMA partially in kdump kernel case.
One exmaple is 'cgroup_disable=memory' we have been doing to add into
kdump cmdline because mem_cgroup is not needed at all for kdump kernel.
We want to achieve that effect.
next prev parent reply other threads:[~2025-04-02 11:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 6:16 [RFC PATCH] ima: add a knob to make IMA be able to be disabled Baoquan He
2025-03-31 6:22 ` Paul Menzel
2025-03-31 8:21 ` Baoquan He
2025-03-31 12:15 ` Mimi Zohar
2025-04-02 1:38 ` Coiby Xu
2025-04-02 1:47 ` RuiRui Yang
2025-04-02 3:30 ` Mimi Zohar
2025-04-02 8:43 ` Coiby Xu
2025-04-02 11:25 ` Mimi Zohar
2025-04-02 11:49 ` Baoquan He [this message]
2025-04-03 20:03 ` Mimi Zohar
2025-04-07 1:34 ` Baoquan He
2025-04-07 11:46 ` Mimi Zohar
2025-04-09 2:42 ` Baoquan He
2025-04-09 15:40 ` Mimi Zohar
2025-04-16 3:22 ` Baoquan He
2025-04-28 3:48 ` Coiby Xu
2025-04-29 11:39 ` Mimi Zohar
2025-05-09 5:59 ` Coiby Xu
2025-05-09 13:03 ` Mimi Zohar
2025-05-13 0:14 ` Coiby Xu
2025-05-13 3:55 ` Gao Xiang
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=Z+0kRhCfsjdZ53rZ@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=coxu@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=ruyang@redhat.com \
--cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.