From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 5A222CFE2; Thu, 02 Jul 2026 14:23:01 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 282E6CFAB; Thu, 02 Jul 2026 14:22:58 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from fout-b1-smtp.messagingengine.com (fout-b1-smtp.messagingengine.com [202.12.124.144]) by atuin.qyliss.net (Postfix) with ESMTPS id 8355ACF6B for ; Thu, 02 Jul 2026 14:22:56 +0000 (UTC) Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfout.stl.internal (Postfix) with ESMTP id 561B41D000E7; Thu, 2 Jul 2026 10:22:54 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-05.internal (MEProxy); Thu, 02 Jul 2026 10:22:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1783002174; x=1783088574; bh=ulSRiryHO5 NHBAgL4Xyptl1a6bboV4qf0uHCgzeDxeg=; b=lPJ4wAIKIWr3EG/oyz4t/b/rwA LwbixkJ0VBuK1k4VAcsYdQ4lwlnRbxmBhlbwDmluHzx9t6OcUWsrYJFcFRxe1FAD QQD6NGSEwStN38Nj9EdLHfIs5My9eLGRvKb0rVA+gf4rFFkSuVOKgPKyQcpJrwIi kB7WpNhzOkaW3TzlS7lq3AUiidSa/v0J5iUowB2zrSyIPiqbXx3trYcIm/F9cuZX NBsezvwJtgn094Six/Vzxl/OaCJV0Hmffnc32YElvW3FZtOMm6zPO+QOj0G487Tj awLHi194wZEF2DtTLa4ZVlKbgGvKgsELVf/ya5tnp6dxlFRTql+MFE1RfakQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1783002174; x=1783088574; bh=ulSRiryHO5NHBAgL4Xyptl1a6bboV4qf0uH CgzeDxeg=; b=nBOK5Le3XsTNn15mHslcINHeib57JTnJpq8cHOK/P8UVts2NHM4 RXDAykv4b0Z8IuTvOeas7/nadPpzb0m/8UEFe+heLvN/GPvKyBb1OlXLPb6z1CPC s87NO7CUq9wt8A1IS+SVLoT8MoRa0EBWT1hWHrr8FqtemQPp+fn438w/GyxrZGql t8hbgivxgyUSLHH8te4kEGNpaS0M/m8mXAhRJ3WPwChLDZXUBgiYV5uO3njoMVrb FGt2EKNSvq1iNFL9hDPZWSgwtNZJKnbdwt34fpgBNtaxpoV+Jzc7u+AhPjjbGKS+ f/KBdT+w/Sicz665vIOL3j+D1aCN+Vw69sw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTGPM/x7u4gimlebfP0hrCgqeajrJVvE1b+vpbz+oVBYgsOGrTyiRJhDagJSa2LNWi OfbkRj6t9ZE4nt7j5m724xF3reyjU20Y2DYehioky2cTaeeG9eBW+fY3SeI0gFMTLfay1g erztmlJmIaoGxLchW9tyb+J7maKobFFDeTIJ0p9kieEJ7t200nhib289hZoWbMkBgQkHVn uExZeo6rvg+Bumr0XIzciQwdEUPpL70eAG1YillzZB8wce/pDtPGAPAl0M6Ti/o8csxr9v yfrhpGewmuKNCo2ZvL7VSCKPrtr4K3z3Ze0jvebfKErK3MhdghxVTsA6FKsHf1o0UoRzJ5 kP0NBZM+olaSoPO6jFDSe4SSkdqrIvNHdbsR2ClrtFVVdChKpIZPjupuyKjRju+KAJJE1+ mqEx8gGb5dDsNmzOmZivwhyu+4SzdhDxqZ9a7HpgeaYogONhExENWK/zxM+6/RUGD6i5NX CDSZq4lx+NvvMPS5L0fIRlg0OZgzR2M/LDyL7HPm2ALT/Q5sT6jBMy2JvenobR5RUdf6ze RLBi083eyBBz9XXs6bvVLcdYCE2vDnO7UeyQj8kBCck2A2kfApYqIxIWkeNDh5J8cWI72Q 3VP9hILxFwbHSxyVYlTqLpJ9lIWyiFMM+q3G64M/OiBJCU6MSzuC5ohzvr3Q X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 2 Jul 2026 10:22:53 -0400 (EDT) Received: by mbp.qyliss.net (Postfix, from userid 1000) id 640CE845F8B2; Thu, 02 Jul 2026 15:43:44 +0200 (CEST) From: Alyssa Ross To: colby@colbyt.com Subject: Re: [PATCH 0/5] vm: boot sub-VMs from dm-verity roots and enable IPE In-Reply-To: References: <20260625202013.1417254-1-colby@colbyt.com> <87cxxdz633.fsf@alyssa.is> Date: Thu, 02 Jul 2026 15:43:43 +0200 Message-ID: <878q7twlps.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-ID-Hash: B6QBAVLJGJ5BXKCPV7V7RXTTUACHZ27O X-Message-ID-Hash: B6QBAVLJGJ5BXKCPV7V7RXTTUACHZ27O X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: devel@spectrum-os.org X-Mailman-Version: 3.3.10 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable colby@colbyt.com writes: > Yes this is me laying the groundwork for/ trying to solve=20 > > "Look into Integrity Policy Enhancement LSM > Apparently this enforces that executables must be authenticated by dm-ver= ity. Could we use this?" > > I may have forgotten to push all the files but I got it implemented and w= orking --- only I did not want to push actual IPE policies in a patch, as t= hat has a substantial possibility to break things. Ah, yes. I meant IPE on the host when I wrote that. I'll update the text to make that clearer. I don't immediately see any value in IPE in VMs. > On Friday, June 26th, 2026 at 8:15 AM, Alyssa Ross wrote: > >> colbyt writes: >>=20 >> > 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, a= nd >> > 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. >>=20 >> 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? >>=20 >> (I really appreciate the quality of your patches BTW =E2=80=94 you've ob= viously >> gone to some effort to identify and follow all the tiny little >> conventions we have in the codebase. Thank you!) >>=20 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRV/neXydHjZma5XLJbRZGEIw/wogUCakZrDwAKCRBbRZGEIw/w okgXAP4pBwN/2kzXzhi/RdN2lE+6NeZgVFWG4pUd2dKXqh9MlAD+L92kwrTQc0/a 83G3LJl+mXvybn4ElnoY8YInrp27Vgk= =8Hvb -----END PGP SIGNATURE----- --=-=-=--