lkml.org 
[lkml]   [2005]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
DateWed, 22 Jun 2005 11:34:18 -0500
FromEric Van Hensbergen <>
SubjectRe: -mm -> 2.6.13 merge status (fuse)
On 6/22/05, Eric Van Hensbergen <ericvh@gmail.com> wrote:
...
>
> If you combine these two restrictions with only allowing unprivileged
> mounts in private name space I think you get 90% there. The only
> thing left to resolve is the best way to allow sharing private name
> spaces between threads/users -- and I still view this as more of
> extended functionality than a hard-requirement.
>

Reviewing my notes, there were a few subtle restrictions I forgot
(most of which originally suggested by Miklos):

(a) User's can't mount file system types not deemed "safe" (via flag
in the file system type) -- this should help mitigate user's
exploiting bugs in existing file systems to interfere with the system.
Judging when a file system type is "safe" is a nasty kettle of fish
though...
(b) Enforce NODEV along with NOSUID so that user-based synthetics
can't have device inodes with compromised permissions, etc.

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

\
 
 \ /
  Last update: 2005-06-22 18:45    [from the cache]
©2003-2010