| 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: <CALCETrU4KXbwvfgtBo=fZ-=DGzgTkEVP0G=FhvJhdoo=+K1g6g@mail.gmail.com> Date: Tue, 29 Apr 2014 17:33:41 -0700 From: Andy Lutomirski <luto@...capital.net> To: "Theodore Ts'o" <tytso@....edu>, Serge Hallyn <serge.hallyn@...ntu.com>, Andy Lutomirski <luto@...capital.net>, Marian Marinov <mm@...com>, Linux Containers <containers@...ts.linux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, lxc-devel <lxc-devel@...ts.sourceforge.net> Subject: Re: ioctl CAP_LINUX_IMMUTABLE is checked in the wrong namespace On Tue, Apr 29, 2014 at 5:32 PM, Theodore Ts'o <tytso@....edu> wrote: > On Wed, Apr 30, 2014 at 12:16:41AM +0000, Serge Hallyn wrote: >> I forget the details, but there was another case where I wanted to >> have the userns which 'owns' the whole fs available. I guess we'd >> have to check against that instead of using inode_capable. > > Yes, that sounds right. > > And *please* tell me that that under no circumstances can anyone other > than root@...t_user_ns is allowed to use mknod.... I haven't read the code, but I tried it the other day, and I got -EPERM. So we're okay for now. (Well, other than the issue I just sent to security@...nel.org, but that's not quite the same thing.) --Andy -- 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