From: virtiofs-bot@sinrega.org
To: virtio-fs@redhat.com
Subject: [Virtio-fs] [virtiofsd] MR merged: sandbox: Allow non-root users run the daemon without isolation
Date: Tue, 8 Nov 2022 16:02:09 +0000 (UTC) [thread overview]
Message-ID: <68290.122110811020602504@us-mta-635.us.mimecast.lan> (raw)
Although, virtiofsd expect to run as root, either as the real one, or the pseudo-root inside a user namespace, there are use cases there are use cases that need to be able to run virtiofsd as a non-privileged user outside a user namespace.
In this mode many operations will not be available (e.g. chown).
There are some issues that are related to this MR: #8 and #43. Besides the request in #8 recently there was a request for this functionality in the matrix channel, I am creating this MR to have that discussion here.
Notes:
- Some operations fails, like chown, but these also fail with --sandbox=namespace.
- I want to move the capability-related code and `enable_seccomp()` call into `sandbox.rs`, so I don't need to "leak" the info about the sandbox type chosen by the user.
---
https://gitlab.com/virtio-fs/virtiofsd/-/merge_requests/136
reply other threads:[~2022-11-08 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68290.122110811020602504@us-mta-635.us.mimecast.lan \
--to=virtiofs-bot@sinrega.org \
--cc=virtio-fs@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 read-only IMAP folder(s) and NNTP newsgroup(s).