From: colby@colbyt.com
To: Alyssa Ross <hi@alyssa.is>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 0/5] vm: boot sub-VMs from dm-verity roots and enable IPE
Date: Fri, 26 Jun 2026 19:12:28 +0000 [thread overview]
Message-ID: <ICoS5yuQbZk_Eyz6pZC6t_3yjO5-TJC4PHALB434Ic8LLUwlmHfJgEUkG3VNw7KaquehbsL6j9k3rP6p6Bzoe1sf15UNegCqQV21QV9fcXs=@colbyt.com> (raw)
In-Reply-To: <87cxxdz633.fsf@alyssa.is>
Yes this is me laying the groundwork for/ trying to solve
"Look into Integrity Policy Enhancement LSM
Apparently this enforces that executables must be authenticated by dm-verity. Could we use this?"
I may have forgotten to push all the files but I got it implemented and working --- only I did not want to push actual IPE policies in a patch, as that has a substantial possibility to break things.
On Friday, June 26th, 2026 at 8:15 AM, Alyssa Ross <hi@alyssa.is> wrote:
> colbyt <colby@colbyt.com> writes:
>
> > This series changes the app VM and net VM root images to boot through
> > dm-verity, then enables IPE kernel support for the sub-VMs and the
> > Spectrum host rootfs.
> >
> > Each sub-VM disk now has a verity metadata partition and an EROFS root
> > partition. The build installs the root hash next to the disk image, and
> > the VM boot paths pass that hash to a shared initramfs. The initramfs
> > uses the hash to find both partitions, opens /dev/mapper/root-verity, and
> > switches into it read-only.
> >
> > The last two patches only enable kernel support for IPE. They do not
> > install an IPE policy. With the existing generated kernel config,
> > enabling SECURITY_IPE also enables the dm-verity root-hash provider, so
> > later policy work can match files from verified roots.
>
> Would you mind explaining your motivation / the direction you envisage
> here in a bit more detail? Given that the VM gets its root file system
> and the corresponding verity hash from the same place (the host file
> system), there's no immediate security benefit from using dm-verity,
> right? Is the idea rather to enable some sort of cool IPE thing for
> which dm-verity is a requirement, but that's not implemented yet as part
> of this series?
>
> (I really appreciate the quality of your patches BTW — you've obviously
> gone to some effort to identify and follow all the tiny little
> conventions we have in the codebase. Thank you!)
>
next prev parent reply other threads:[~2026-06-26 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 20:20 [PATCH 0/5] vm: boot sub-VMs from dm-verity roots and enable IPE colbyt
2026-06-25 20:20 ` [PATCH 1/5] vm: generate dm-verity metadata for sub-VM roots colbyt
2026-06-25 20:20 ` [PATCH 2/5] vm: add shared initramfs for verified roots colbyt
2026-06-25 20:20 ` [PATCH 3/5] vm: boot sub-VMs through " colbyt
2026-06-25 20:20 ` [PATCH 4/5] vm: enable IPE in sub-VM kernels colbyt
2026-06-25 20:20 ` [PATCH 5/5] host/rootfs: enable IPE in the host kernel colbyt
2026-07-02 13:44 ` Alyssa Ross
2026-06-26 15:14 ` [PATCH 0/5] vm: boot sub-VMs from dm-verity roots and enable IPE Alyssa Ross
2026-06-26 19:12 ` colby [this message]
2026-07-02 13:43 ` Alyssa Ross
2026-07-02 23:16 ` colby
2026-07-03 14:06 ` Alyssa Ross
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='ICoS5yuQbZk_Eyz6pZC6t_3yjO5-TJC4PHALB434Ic8LLUwlmHfJgEUkG3VNw7KaquehbsL6j9k3rP6p6Bzoe1sf15UNegCqQV21QV9fcXs=@colbyt.com' \
--to=colby@colbyt.com \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
/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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).