| 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
| ||
|
Message-ID: <m1bqhhked1.fsf@ebiederm.dsl.xmission.com> Date: Sat, 21 Apr 2007 08:10:18 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: Andrew Morton <akpm@...ux-foundation.org> Cc: Miklos Szeredi <miklos@...redi.hu>, serue@...ibm.com, viro@....linux.org.uk, linuxram@...ibm.com, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, containers@...ts.osdl.org Subject: Re: [patch 7/8] allow unprivileged mounts Andrew Morton <akpm@...ux-foundation.org> writes: > On Fri, 20 Apr 2007 12:25:39 +0200 Miklos Szeredi <miklos@...redi.hu> wrote: > >> Define a new fs flag FS_SAFE, which denotes, that unprivileged >> mounting of this filesystem may not constitute a security problem. >> >> Since most filesystems haven't been designed with unprivileged >> mounting in mind, a thorough audit is needed before setting this flag. > > Practically speaking, is there any realistic likelihood that any filesystem > apart from FUSE will ever use this? Also potentially some of the kernel virtual filesystems. /proc should be safe already. If you don't have any kind of backing store this problem gets easier. With unprivileged users allowed to create mounts the utility of kernel functionality exported as filesystems goes up quite a bit. We are not plan9 but this is the last bottleneck in allowing the everything is a filesystem paradigm from being really usable in linux. Eric - 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