lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 16 Apr 2007 01:47:00 -0700 From: Ram Pai <linuxram@...ibm.com> To: devel@...nvz.org Cc: "Serge E. Hallyn" <serue@...ibm.com>, Miklos Szeredi <miklos@...redi.hu>, linux-kernel@...r.kernel.org, containers@...ts.osdl.org, viro@....linux.org.uk, linux-fsdevel@...r.kernel.org, akpm@...ux-foundation.org Subject: Re: [Devel] Re: [patch 05/10] add "permit user mounts in new namespace" clone flag > > "Serge E. Hallyn" <serue@...ibm.com> writes: > > > Quoting Miklos Szeredi (miklos@...redi.hu): > >> From: Miklos Szeredi <mszeredi@...e.cz> > >> > >> If CLONE_NEWNS and CLONE_NEWNS_USERMNT are given to clone(2) or > >> unshare(2), then allow user mounts within the new namespace. > >> > >> This is not flexible enough, because user mounts can't be enabled > for > >> the initial namespace. > >> > >> The remaining clone bits also getting dangerously few... > >> > >> Alternatives are: > >> > >> - prctl() flag > >> - setting through the containers filesystem > > > > Sorry, I know I had mentioned it, but this is definately my least > > favorite approach. > > > > Curious whether are any other suggestions/opinions from the > containers > > list? > > Given the existence of shared subtrees allowing/denying this at the > mount > namespace level is silly and wrong. > > If we need more than just the filesystem permission checks can we > make it a mount flag settable with mount and remount that allows > non-privileged users the ability to create mount points under it > in directories they have full read/write access to. Also for bind-mount and remount operations the flag has to be propagated down its propagation tree. Otherwise a unpriviledged mount in a shared mount wont get reflected in its peers and slaves, leading to unidentical shared-subtrees. RP > > I don't like the use of clone flags for this purpose but in this > case the shared subtress are a much more fundamental reasons for not > doing this at the namespace level. > > Eric > _______________________________________________ > Containers mailing list > Containers@...ts.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/containers - 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