From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH v2 1/4] host/rootfs: Sandbox crosvm
Date: Thu, 04 Dec 2025 14:28:59 +0100 [thread overview]
Message-ID: <87sedq9y04.fsf@alyssa.is> (raw)
In-Reply-To: <69a23f96-5f1e-4afc-8acf-62df834df069@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3249 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> On 12/3/25 07:43, Alyssa Ross wrote:
>> Demi Marie Obenour <demiobenour@gmail.com> writes:
>>
>>> This means that a breach of crosvm is not guaranteed to be fatal.
>>>
>>> The Wayland socket is still only accessible by root, so crosvm must run
>>> as root. The known container escape via /proc/self/exe is blocked by
>>> bwrap being on a read-only filesystem. Container escapes via /proc are
>>> blocked by remounting /proc read-only. Crosvm does not have
>>> CAP_SYS_ADMIN so it cannot change mounts.
>>>
>>> The two remaining steps are:
>>>
>>> - Run crosvm as an unprivileged user.
>>> - Enable seccomp to block most system calls.
>>>
>>> The latter should be done from within crosvm itself.
>>>
>>> Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
>>> ---
>>> host/rootfs/default.nix | 4 ++--
>>> .../template/data/service/vhost-user-gpu/run | 24 +++++++++++++++++++++-
>>> 2 files changed, 25 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/host/rootfs/default.nix b/host/rootfs/default.nix
>>> index ca2084f26d58be5e0e1695634e125032c50f82b2..4716bb7298515b2940cad09bb55e42c196ce7ebc 100644
>>> --- a/host/rootfs/default.nix
>>> +++ b/host/rootfs/default.nix
>>> @@ -10,7 +10,7 @@ pkgsMusl.callPackage (
>>>
>>> { spectrum-host-tools, spectrum-router
>>> , lib, stdenvNoCC, nixos, runCommand, writeClosure, erofs-utils, s6-rc
>>> -, btrfs-progs, busybox, cloud-hypervisor, cosmic-files, crosvm
>>> +, btrfs-progs, bubblewrap, busybox, cloud-hypervisor, cosmic-files, crosvm
>>> , cryptsetup, dejavu_fonts, dbus, execline, foot, fuse3, iproute2
>>> , inotify-tools, jq, kmod, mdevd, mesa, mount-flatpak, s6
>>> , s6-linux-init, socat, systemd, util-linuxMinimal, virtiofsd
>>> @@ -25,7 +25,7 @@ let
>>> trivial;
>>>
>>> packages = [
>>> - btrfs-progs cloud-hypervisor cosmic-files crosvm cryptsetup dbus
>>> + btrfs-progs bubblewrap cloud-hypervisor cosmic-files crosvm cryptsetup dbus
>>> execline fuse3 inotify-tools iproute2 jq kmod mdevd mount-flatpak s6
>>> s6-linux-init s6-rc socat spectrum-host-tools spectrum-router
>>> util-linuxMinimal virtiofsd xdg-desktop-portal-spectrum-host
>>> diff --git a/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run b/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run
>>> index 0b4f6a00bc7aed0e721454d584d3bcd47fb18e2a..9b5dfad91944bd2c6c8994f387ab91394c68c1df 100755
>>> --- a/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run
>>> +++ b/host/rootfs/image/etc/s6-linux-init/run-image/service/vm-services/template/data/service/vhost-user-gpu/run
>>> @@ -1,10 +1,32 @@
>>> #!/bin/execlineb -P
>>> # SPDX-License-Identifier: EUPL-1.2+
>>> # SPDX-FileCopyrightText: 2025 Alyssa Ross <hi@alyssa.is>
>>> +# SPDX-FileCopyrightText: 2025 Demi Marie Obenour <demiobenour@gmail.com>
>>
>> You add a copyright line here, but not in subsequent patches. Is that
>> on purpose?
>
> No.
So which should it be, for all these changes?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-12-04 13:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 22:31 [PATCH] host/rootfs: Sandbox crosvm Demi Marie Obenour
2025-12-02 3:46 ` [PATCH v2 0/4] Partially sandbox Cloud Hypervisor, crosvm, virtiofsd, and the router Demi Marie Obenour
2025-12-02 3:46 ` [PATCH v2 1/4] host/rootfs: Sandbox crosvm Demi Marie Obenour
2025-12-03 12:43 ` Alyssa Ross
2025-12-03 12:48 ` Demi Marie Obenour
2025-12-03 13:09 ` Alyssa Ross
2025-12-04 13:28 ` Alyssa Ross [this message]
2025-12-02 3:46 ` [PATCH v2 2/4] host/rootfs: Sandbox router Demi Marie Obenour
2025-12-02 3:46 ` [PATCH v2 3/4] host/rootfs: Sandbox virtiofsd Demi Marie Obenour
2025-12-02 3:46 ` [PATCH v2 4/4] host/rootfs: Sandbox Cloud Hypervisor Demi Marie Obenour
2025-12-02 13:14 ` [PATCH v2 0/4] Partially sandbox Cloud Hypervisor, crosvm, virtiofsd, and the router Alyssa Ross
2025-12-03 15:54 ` [PATCH v3 0/5] " Demi Marie Obenour
2025-12-03 15:54 ` [PATCH v3 1/5] host/rootfs: Sandbox crosvm Demi Marie Obenour
2025-12-03 15:54 ` [PATCH v3 2/5] host/rootfs: Sandbox router Demi Marie Obenour
2025-12-03 16:06 ` Yureka
2025-12-03 16:11 ` Alyssa Ross
2025-12-09 11:23 ` Yureka
2025-12-03 15:54 ` [PATCH v3 3/5] host/rootfs: Unshare a few more namespaces in virtiofsd Demi Marie Obenour
2025-12-03 15:54 ` [PATCH v3 4/5] host/rootfs: Sandbox Cloud Hypervisor Demi Marie Obenour
2025-12-03 15:54 ` [PATCH v3 5/5] host/rootfs: Try to protect the portal and dbus daemon Demi Marie Obenour
2025-12-04 2:20 ` [PATCH v4 0/6] Partially sandbox Cloud Hypervisor, crosvm, virtiofsd, and the router Demi Marie Obenour
2025-12-04 2:20 ` [PATCH v4 1/6] host/rootfs: Sandbox crosvm Demi Marie Obenour
2025-12-04 13:03 ` Alyssa Ross
2025-12-04 2:20 ` [PATCH v4 2/6] host/rootfs: Sandbox router Demi Marie Obenour
2025-12-04 13:47 ` Alyssa Ross
2025-12-04 2:20 ` [PATCH v4 3/6] host/rootfs: Unshare a few more namespaces in virtiofsd Demi Marie Obenour
2025-12-04 14:03 ` Alyssa Ross
2025-12-04 2:20 ` [PATCH v4 4/6] host/rootfs: Sandbox Cloud Hypervisor Demi Marie Obenour
2025-12-04 14:35 ` Alyssa Ross
2025-12-06 17:35 ` Demi Marie Obenour
2025-12-06 17:46 ` Alyssa Ross
2025-12-06 17:47 ` Demi Marie Obenour
2025-12-06 17:56 ` Alyssa Ross
2025-12-04 2:20 ` [PATCH v4 5/6] host/rootfs: Try to protect the portal and dbus daemon Demi Marie Obenour
2025-12-04 14:23 ` Alyssa Ross
2025-12-04 2:20 ` [PATCH v4 6/6] host/rootfs: "Sandbox" Weston Demi Marie Obenour
2025-12-04 14:47 ` 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=87sedq9y04.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
/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).