[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1JEjCG-0000wz-BS@pomaz-ex.szeredi.hu>
Date: Tue, 15 Jan 2008 11:39:08 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: serue@...ibm.com
CC: miklos@...redi.hu, akpm@...ux-foundation.org, hch@...radead.org,
serue@...ibm.com, viro@....linux.org.uk, ebiederm@...ssion.com,
kzak@...hat.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, containers@...ts.osdl.org,
util-linux-ng@...r.kernel.org
Subject: Re: [patch 8/9] unprivileged mounts: propagation: inherit owner
from parent
> Quoting Miklos Szeredi (miklos@...redi.hu):
> > From: Miklos Szeredi <mszeredi@...e.cz>
> >
> > On mount propagation, let the owner of the clone be inherited from the
> > parent into which it has been propagated. Also if the parent has the
> > "nosuid" flag, set this flag for the child as well.
>
> What about nodev?
Hmm, I think the nosuid thing is meant to prevent suid mounts being
introduced into a "suidless" namespace. This doesn't apply to dev
mounts, which are quite safe in a suidless environment, as long as the
user is not able to create devices. But that should be taken care of
by capability tests.
I'll update the description.
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/
Powered by blists - more mailing lists