[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20111128181443.GA4672@albatros>
Date: Mon, 28 Nov 2011 22:14:43 +0400
From: Vasiliy Kulikov <segoon@...nwall.com>
To: Kees Cook <keescook@...omium.org>
Cc: "Serge E. Hallyn" <serge@...lyn.com>,
Serge Hallyn <serge.hallyn@...onical.com>,
linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org,
kernel-hardening@...ts.openwall.com
Subject: Re: [RFC] Make Yama pid_ns aware
On Mon, Nov 28, 2011 at 10:12 -0800, Kees Cook wrote:
> On Wed, Nov 23, 2011 at 8:55 AM, Vasiliy Kulikov <segoon@...nwall.com> wrote:
> > Can we probably leave them in pid ns for now and when user ns is matured
> > just move it from pid ns to user ns? Is it possible without breaking
> > Yama's ABI (I think so)?
>
> So it sounds like you'll send a new patch where only ptrace_scope is
> tied to pidns?
Em, no. I've said we'll leave everything in pid ns for now. When user
ns is ready, we'll move some options (all of them?) from pid ns to user
ns. As user interface is kernel.yama.* sysctls and will not be changed
with the migration, ABI would not be broken by this migration.
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
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.
