[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1437414899.148452.328428529.097963A9@webmail.messagingengine.com>
Date: Mon, 20 Jul 2015 13:54:59 -0400
From: Colin Walters <walters@...bum.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>,
Casey Schaufler <casey@...aufler-ca.com>
Cc: Andy Lutomirski <luto@...capital.net>,
Seth Forshee <seth.forshee@...onical.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
On Thu, Jul 16, 2015, at 12:47 AM, Eric W. Biederman wrote:
> With that said desktop environments have for a long time been
> automatically mounting whichever filesystem you place in your computer,
> so in practice what this is really about is trying to align the kernel
> with how people use filesystems.
There is a large attack surface difference between mounting a device
that someone physically plugged into the computer (and note typically
it's required that the active console be unlocked as well[1]) versus
allowing any "unprivileged" process at any time to do it.
Many server setups use "unprivileged" uids that otherwise wouldn't
be able to exploit bugs in filesystem code.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=653520
"AutomountManager also keeps track of the current session availability
(using the ConsoleKit and gnome-screensaver DBus interfaces) and
inhibits mounting if the current session is locked, or another session
is in use instead."
--
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