From: Vivek Goyal <vgoyal@redhat.com>
To: Chirantan Ekbote <chirantan@chromium.org>
Cc: virtio-fs-list <virtio-fs@redhat.com>, P J P <ppandit@redhat.com>
Subject: Re: [Virtio-fs] [RFC] About non-root virtiofsd(1) process
Date: Tue, 16 Feb 2021 09:39:54 -0500 [thread overview]
Message-ID: <20210216143954.GB3196@redhat.com> (raw)
In-Reply-To: <CAJFHJroGX7YYPK2KzxBtM3Pnf7heUxsjZXOvoH0GR7gMrDTuuQ@mail.gmail.com>
On Wed, Jan 20, 2021 at 02:49:52PM +0900, Chirantan Ekbote wrote:
> On Tue, Jan 19, 2021 at 11:34 PM P J P <ppandit@redhat.com> wrote:
> >
> > +-- On Mon, 18 Jan 2021, Stefan Hajnoczi wrote --+
> > | Guest applications may run with different uids/gids. The host has no control
> > | over that.
> > |
> > | Imagine booting a guest form a virtio-fs root file system and installing
> > | packages. The guest must be able to control uids/gids for that to work.
> >
> > * I see; I'll try to better understand how it's done.
> >
> > * With UID namespaces, I thought virtiofsd(1) would be able to operate files
> > with arbitrary uid/gid, even after dropping its root privileges to acquire
> > non-root privileges on the host; Because it has 'root' privileges under the
> > shared directory & UID namespace.
> >
>
> This is actually what we do in crosvm. It works pretty well but has a
> few limitations:
>
> - Setting up the uidmap and gidmap requires CAP_SETUID and CAP_SETGID
> (unless you're only mapping in the current euid/egid) so a user
> without sudo access cannot do it.
> - The daemon cannot do anything that requires caps in the init
> namespace. For example, it cannot set any security.* or trusted.*
> xattrs but that can be worked around by re-mapping them into the
> user.* xattr namespace. Another example is anything to do with
> filesystem quotas. We deal with this by forwarding them to another
> daemon running in the init namespace but it's not ideal.
As of now probably "chown" is another limitation. One has to chown
all uid/gid to appropriate mapping. Also if directory is shared
between two VMs, then they have to be using same uid/gid map.
Vivek
>
> Overall I think we're pretty happy with the user namespace sandbox. I
> think the benefit of dropping all privileges in the init namespace has
> been worth the cost of dealing with the limitations we've run into so
> far.
>
> Chirantan
>
> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
next prev parent reply other threads:[~2021-02-16 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 8:41 [Virtio-fs] [RFC] About non-root virtiofsd(1) process P J P
2021-01-14 10:08 ` Dr. David Alan Gilbert
2021-01-14 13:10 ` P J P
2021-01-14 13:34 ` Stefan Hajnoczi
2021-01-15 7:09 ` P J P
2021-01-18 16:55 ` Stefan Hajnoczi
2021-01-19 14:34 ` P J P
2021-01-20 5:49 ` Chirantan Ekbote
2021-01-20 16:21 ` Stefan Hajnoczi
2021-02-16 14:39 ` Vivek Goyal [this message]
2021-01-20 16:20 ` Stefan Hajnoczi
2021-02-16 14:36 ` Vivek Goyal
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=20210216143954.GB3196@redhat.com \
--to=vgoyal@redhat.com \
--cc=chirantan@chromium.org \
--cc=ppandit@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.