linux-kernel - Re: [PATCH] userns: Support fuse interacting with multiple user namespaces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <878va6i5xu.fsf@xmission.com>
Date:	Mon, 12 Nov 2012 18:37:33 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	<linux-fsdevel@...r.kernel.org>,
	"Serge E. Hallyn" <serge@...lyn.com>,
	Linux Containers <containers@...ts.linux-foundation.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] userns: Support fuse interacting with multiple user namespaces

Miklos Szeredi <miklos@...redi.hu> writes:

> ebiederm@...ssion.com (Eric W. Biederman) writes:
>
>> Use kuid_t and kgid_t in struct fuse_conn and struct fuse_mount_data.
>>
>> The connection between between a fuse filesystem and a fuse daemon is
>> established when a fuse filesystem is mounted and provided with a file
>> descriptor the fuse daemon created by opening /dev/fuse.
>>
>> For now restrict the communication of uids and gids between the fuse
>> filesystem and the fuse daemon to the initial user namespace.
>
> Why?
>
> I think far more logical would be to limit a single instance of the
> filesystem and the daemon to an arbitrary but *single* namespace.
> I.e. one fuse_conn <-> one user namespace.
>
> Is there a reason to treat the initial namespace specially?

Stepwise making this work.

The initial user namespace is special in that is the only user namespace
you can currently mount a filesystem in.

My goal with the posted patch is to support users on the other side of
the vfs that are in multiple user namespaces.  Which basically means
accepting kuid_t and kgid_t values and converting them to uid_t and
gid_t values where needed.

As for creating a version of fuse that can be mounted in different user
namespaces and can communicate with the fuse daemon in the user
namespace the filesystem was mounted in, I have a preliminary patch for
that.  My goal with that patch is to support unprivileged mounts of fuse
without the help of a suid root mount program.  But that patch is more
involved and not quite ready yet.

I want to get to the point that I can enable fuse and user namespaces at
the same time (what this patch allows) and then put in the effort to
fully take advantage of user namespaces.

Eric

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/