|
Message-ID: <CAGXu5jKHFaA6YawiospVcZWk5aVjGE+5p9TosrtQHgRYLbXuLw@mail.gmail.com> Date: Mon, 28 Nov 2011 12:15:36 -0800 From: Kees Cook <keescook@...omium.org> To: Vasiliy Kulikov <segoon@...nwall.com> Cc: linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, kernel-hardening@...ts.openwall.com, "Serge E. Hallyn" <serge@...lyn.com> Subject: Re: [RFC -resend] Make Yama pid_ns aware On Mon, Nov 28, 2011 at 11:35 AM, Kees Cook <keescook@...omium.org> wrote: > On Mon, Nov 28, 2011 at 11:16 AM, Vasiliy Kulikov <segoon@...nwall.com> wrote: >> As Yama's sysctls are about defining a security policy for the system, >> it is reasonable to define it per container in case of LXC containers >> (or out-of-tree alternatives like OpenVZ). In my opinion they belong >> to pid namespace. With per-pid_ns sysctls it is possible to create >> multiple containers with different ptrace, /tmp, etc. policies. >> [...] >> Signed-off-by: Vasiliy Kulikov <segoon@...nwall.com> > > Thanks! I'll include this in the next Yama patch set. > > Acked-by: Kees Cook <keescook@...omium.org> I should mention, this lives here now: http://git.kernel.org/?p=linux/kernel/git/kees/linux.git;a=shortlog;h=refs/heads/yama -Kees -- Kees Cook ChromeOS Security
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.