From mboxrd@z Thu Jan 1 00:00:00 1970 From: Colin Walters Subject: Re: [PATCH 0/7] Initial support for user namespace owned mounts Date: Thu, 30 Jul 2015 11:52:07 -0400 Message-ID: <1438271527.4081427.337383497.750BC231@webmail.messagingengine.com> References: <20150730135531.GA109168@ubuntu-hedt> <55BA43C7.40300@schaufler-ca.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: "Theodore Ts'o" , Stephen Smalley , Andy Lutomirski , "Eric W. Biederman" , Alexander Viro , Linux FS Devel , LSM List , "SELinux-NSA" , Serge Hallyn , linux-kernel@vger.kernel.org To: Casey Schaufler , Amir Goldstein , Seth Forshee Return-path: In-Reply-To: <55BA43C7.40300@schaufler-ca.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org It's worth noting here that I think a lot of the use cases for unprivileged mounts are testing/development type things, and these are pretty well covered by: http://libguestfs.org/ Basically it just runs the host kernel in a VM, and the userspace is a minimal agent that you can talk to over virtio. You can use the API, or `guestmount` exposes it via FUSE. It doesn't magically make the kernel filesystems robust against untrusted input, but in the case of compromise, it's an "unprivileged" VM. I've used it for several projects and been quite happy.