|
Message-ID: <CAObL_7GzsJ+EW94oYG+EzcRqYyH2EPTyFgTgo6zmSz1yxEe-xw@mail.gmail.com> Date: Fri, 6 Apr 2012 13:54:19 -0700 From: Andrew Lutomirski <luto@....edu> To: Markus Gutschke <markus@...omium.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Will Drewry <wad@...omium.org>, linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, linux-arch@...r.kernel.org, linux-doc@...r.kernel.org, kernel-hardening@...ts.openwall.com, netdev@...r.kernel.org, x86@...nel.org, arnd@...db.de, davem@...emloft.net, hpa@...or.com, mingo@...hat.com, oleg@...hat.com, peterz@...radead.org, rdunlap@...otime.net, mcgrathr@...omium.org, tglx@...utronix.de, eparis@...hat.com, serge.hallyn@...onical.com, djm@...drot.org, scarybeasts@...il.com, indan@....nu, pmoore@...hat.com, corbet@....net, eric.dumazet@...il.com, coreyb@...ux.vnet.ibm.com, keescook@...omium.org, jmorris@...ei.org, Andy Lutomirski <luto@...capital.net> Subject: Re: [PATCH v17 01/15] Add PR_{GET,SET}_NO_NEW_PRIVS to prevent execve from granting privs On Fri, Apr 6, 2012 at 1:47 PM, Markus Gutschke <markus@...omium.org> wrote: > On Fri, Apr 6, 2012 at 12:49, Andrew Morton <akpm@...ux-foundation.org> wrote: >> On Thu, 29 Mar 2012 15:01:46 -0500 >> Will Drewry <wad@...omium.org> wrote: >>> From: Andy Lutomirski <luto@...capital.net> >>> With this set, a lot of dangerous operations (chroot, unshare, etc) >>> become a lot less dangerous because there is no possibility of >>> subverting privileged binaries. > > I don't want to derail things. So, tell me to go away, if I can't have > what I want. > > Having said that, it would be great if NO_NEW_PRIVS also gave access > to the restricted clone() flags. Such as CLONE_NEWIPC, CLONE_NEWNET > and CLONE_NEWPID. I decided to hold off on extra controversy for awhile. However: https://git.kernel.org/?p=linux/kernel/git/luto/linux.git;a=commit;h=9a520b74ad5dc14a3d6950b6d63a64714adbdd7d and http://web.mit.edu/luto/www/linux/nnp/newns.c I fully intend to resurrect both of those once nnp lands. (FWIW, I think that CLONE_NEWPID interacts badly with unix socket credentials and should be fixed as a prerequisite for making it easier to access.) --Andy
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.