| 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: <87ip5wvytq.fsf@xmission.com> Date: Wed, 13 Feb 2013 10:44:01 -0800 From: ebiederm@...ssion.com (Eric W. Biederman) To: linux-fsdevel@...r.kernel.org Cc: Linux Containers <containers@...ts.linux-foundation.org>, linux-kernel@...r.kernel.org, "Serge E. Hallyn" <serge@...lyn.com> Subject: Re: [PATCH review 18/85] coda: Restrict coda messages to the initial user namespace Jan Harkes <jaharkes@...cmu.edu> writes: > On Wed, Feb 13, 2013 at 09:51:07AM -0800, Eric W. Biederman wrote: >> From: "Eric W. Biederman" <ebiederm@...ssion.com> >> >> Remove the slight chance that uids and gids in coda messages will be >> interpreted in the wrong user namespace. > > Awesome, I was wondering how to handle uid's from different namespaces > cleanly in Coda's userspace daemon without resorting to exporting kuids > to userspace. > > But this is a much more elegant solution, every namespace that cares > about Coda should just run their own mountpoint and userspace daemon. Do you know if people care enough about coda that they will want to export run coda multiple mountpoint and userspace daemons? I have never seen anyone running coda so I was suspecting that coda was a filesystem that was gradually fading away. 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