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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87625brr76.fsf@tucsk.pomaz.szeredi.hu>
Date:	Mon, 12 Nov 2012 12:33:33 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	ebiederm@...ssion.com (Eric W. Biederman)
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

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?

Thanks,
Miklos
--
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/