[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1438271527.4081427.337383497.750BC231@webmail.messagingengine.com>
Date: Thu, 30 Jul 2015 11:52:07 -0400
From: Colin Walters <walters@...bum.org>
To: Casey Schaufler <casey@...aufler-ca.com>,
Amir Goldstein <amir@...lrox.com>,
Seth Forshee <seth.forshee@...onical.com>
Cc: "Theodore Ts'o" <tytso@....edu>,
Stephen Smalley <sds@...ho.nsa.gov>,
Andy Lutomirski <luto@...capital.net>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
LSM List <linux-security-module@...r.kernel.org>,
"SELinux-NSA" <selinux@...ho.nsa.gov>,
Serge Hallyn <serge.hallyn@...onical.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] Initial support for user namespace owned mounts
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.
--
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/
Powered by blists - more mailing lists