[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJuoC7dgB_U2qj1Pb0-wd_D+JjLEuxS2e+uZDEugvGqXQ@mail.gmail.com>
Date: Mon, 21 Nov 2011 11:42:12 -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] Make Yama pid_ns aware
On Mon, Nov 21, 2011 at 11:18 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.
Cool, this seems like a good idea. Thanks for the patch! If Serge (or
other folks thinking about per-pid_ns stuff) think this is a good
approach, I'm happy to include it in the next revision of the Yama
patchset.
> proc_pid_dointvec_minmax() is stolen from its ipc_ns equivalent in
> ipc/ipc_sysctl.c.
I wonder if this function should be moved into a common location, in
case other things will want to do similar things.
-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.
