From: Mimi Zohar <zohar@linux.ibm.com>
To: Pingfan Liu <piliu@redhat.com>
Cc: Baoquan He <bhe@redhat.com>,
prudo@redhat.com, linux-integrity@vger.kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
pmenzel@molgen.mpg.de, coxu@redhat.com, ruyang@redhat.com,
chenste@linux.microsoft.com
Subject: Re: [PATCH] ima: add a knob ima= to make IMA be able to be disabled
Date: Thu, 29 May 2025 10:31:54 -0400 [thread overview]
Message-ID: <91a9aa935b3a194c57a166133c9c1a537a9ca802.camel@linux.ibm.com> (raw)
In-Reply-To: <CAF+s44Q6ZJ8rdi1VG40JVJmxX-1hmss5eNaKvGhJSOS6xYLx-g@mail.gmail.com>
On Thu, 2025-05-29 at 12:13 +0800, Pingfan Liu wrote:
> On Tue, May 27, 2025 at 10:18 PM Mimi Zohar <zohar@linux.ibm.com> wrote:
> >
> > On Tue, 2025-05-27 at 11:25 +0800, Pingfan Liu wrote
> > > > >
> > > > >
> > > > > We're trying to close integrity gaps, not add new ones. Verifying the
> > > > > UKI's
> > > > > signature addresses the integrity of the initramfs. What about the
> > > > > integrity of
> > > > > the kdump initramfs (or for that matter the kexec initramfs)? If the
> > > > > kdump
> > > > > initramfs was signed, IMA would be able to verify it before the kexec.
> > >
> > > IMHO, from the higher level, if there is a requirement on the integrity of
> > > the
> > > initramfs, it should take a similar approach as UKI. And the system admin
> > > can
> > > choose whether to disable the unsafe format loader or not.
> >
> > Yes, that is a possibility, probably a good aim, but in the case of
> > kexec/kdump
> > that isn't really necessary. As filesystem(s) support xattrs, IMA policies
> > could be written in terms of "func=KEXEC_INITRAMFS_CHECK" to include the
> > initramfs.
> >
>
> Just aware that we have such a cool feature. Thanks!
> I checked the code. IIUC, the relevant code has already been in the
> kernel. And the thing left to do is to install an IMA policy, right?
Correct. The problem up to now has been that the initramfs was created on the
fly on the target system, so it was impossible to remotely sign it by the
distro.
>
> But there are still two things to be considered.
> -1.The UEFI partition is FAT format, which can not support xattr
The normal kexec/kdump kernel image and initramfs are stored in /boot, not the
UEFI partition. Is that changing?
e.g. kexec -s -l /boot/vmlinuz-`uname -r` --initrd=/boot/initramfs-`uname -
r`.img --reuse-cmdline
> -2. Just like in the UKI case, the kernel fd content is not necessary
> for the kernel image itself. The initramfs fd can be used to pass some
> extra data if we use a temp file as a package. So checking the
> signatures at the initramfs level will block this usage
Sorry I lost you here. What exactly is included in the UKI signature? What is
this initramfs fd extra data? Is it included in the UKI signature? Can you
point me to some documentation?
thanks,
Mimi
> >
next prev parent reply other threads:[~2025-05-29 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 23:39 [PATCH] ima: add a knob ima= to make IMA be able to be disabled Baoquan He
2025-05-16 0:22 ` Baoquan He
2025-05-21 12:54 ` Mimi Zohar
2025-05-21 12:58 ` Mimi Zohar
2025-05-22 3:49 ` Baoquan He
2025-05-22 3:14 ` Coiby Xu
2025-05-22 3:24 ` Baoquan He
2025-05-22 6:02 ` Coiby Xu
2025-05-22 11:08 ` Mimi Zohar
2025-05-22 14:52 ` Baoquan He
[not found] ` <CAF+s44QHJs8J27TEy0AW1m2wT=LRSz59nHf-8AuqL8px_zKGUg@mail.gmail.com>
2025-05-27 14:17 ` Mimi Zohar
2025-05-29 4:13 ` Pingfan Liu
2025-05-29 14:31 ` Mimi Zohar [this message]
2025-05-30 4:14 ` Pingfan Liu
2025-06-04 3:34 ` Coiby Xu
2025-06-04 22:53 ` Mimi Zohar
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=91a9aa935b3a194c57a166133c9c1a537a9ca802.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=chenste@linux.microsoft.com \
--cc=coxu@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piliu@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=prudo@redhat.com \
--cc=ruyang@redhat.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;
as well as URLs for NNTP newsgroup(s).