patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: Why is /run/vm/by-id/${VM} writable by the VMM?
Date: Mon, 13 Jul 2026 11:04:36 +0200	[thread overview]
Message-ID: <87ech71crf.fsf@alyssa.is> (raw)
In-Reply-To: <ae3a437e-6d27-42ef-9688-3562f69f66b7@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

Demi Marie Obenour <demiobenour@gmail.com> writes:

> This seems to be a fairly significant hole in the VMM's sandbox.
> Various code operates in that directory and isn't secure against
> symlink attacks.
>
> Does the VMM really need write access to that directory?  Could it
> be given access to a subdirectory that is mounted "nosymfollow"?

I think it's just so it can create e.g. the serial file.  That could
indeed be moved to a subdirectory.  The ideal solution is of course for
Cloud Hypervisor to be able to accept every file it would otherwise
create as an open file descriptor, which I expect will happen
eventually.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2026-07-13 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 19:04 Why is /run/vm/by-id/${VM} writable by the VMM? Demi Marie Obenour
2026-07-13  9:04 ` Alyssa Ross [this message]
2026-07-13 17:00   ` Demi Marie Obenour
2026-07-15 18:54     ` Alyssa Ross
2026-07-16 17:06       ` Demi Marie Obenour
2026-07-21 16:05         ` Alyssa Ross
2026-07-21 20:11           ` Demi Marie Obenour
2026-07-22  8:18             ` 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=87ech71crf.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/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock

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).