mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH v6 0/3] security: Yama LSM
Date: Wed, 2 Nov 2011 07:45:53 +1100 (EST)	[thread overview]
Message-ID: <alpine.LRH.2.00.1111020735080.11087@tundra.namei.org> (raw)
In-Reply-To: <1319672956-17114-1-git-send-email-keescook@chromium.org>

On Wed, 26 Oct 2011, Kees Cook wrote:

> As discussed at the Linux Security Summit, I'm resubmitting this
> code. As an LSM, it has coherent policy around expanding specific DAC
> behaviors. There is no need for it to be a full-blown MAC, since it is
> not intended to be one, but rather to be a simplified expansion to DAC,
> with system-wide knobs. See the specific patches for details...

Yes, there was a strong consensus (unanimous I believe) at the security 
summit on incorporating the Yama LSM as a container for generally useful 
miscellaneous security hardening features that don't belong elsewhere.

This means that LSM is no longer 'officially' only for access control 
mechanisms.

We probably need to flesh out criteria for inclusion in Yama and document 
it.



- James
-- 
James Morris
<jmorris@namei.org>

  parent reply	other threads:[~2011-11-01 20:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 23:49 Kees Cook
2011-10-26 23:49 ` [PATCH 1/3] " Kees Cook
2011-10-26 23:49 ` [PATCH 2/3] security: create task_free security callback Kees Cook
2011-10-26 23:49 ` [PATCH 3/3] security: Yama: add ptrace relationship tracking interface Kees Cook
2011-11-19 16:30   ` Vasiliy Kulikov
2011-11-19 16:59     ` Solar Designer
2011-11-21 18:40       ` Kees Cook
2011-11-01 20:45 ` James Morris [this message]
2011-11-01 21:05   ` [PATCH v6 0/3] security: Yama LSM Kees Cook
2011-11-01 21:37     ` James Morris
2011-11-01 23:23       ` Kees Cook
2011-11-18  4:17 ` James Morris
2011-11-18 21:39   ` Kees Cook
2011-11-18 21:45     ` Roland McGrath
2011-11-18 22:44       ` Kees Cook
2011-11-18 23:18   ` Kees Cook
2011-11-21 19:18 ` [RFC] Make Yama pid_ns aware Vasiliy Kulikov
2011-11-21 19:42   ` Kees Cook
2011-11-22 18:13   ` Serge Hallyn
2011-11-22 19:20     ` Vasiliy Kulikov
2011-11-22 20:10       ` Serge Hallyn
2011-11-23  7:45         ` Vasiliy Kulikov
2011-11-23 14:41           ` Serge Hallyn
2011-11-23 14:49           ` Serge E. Hallyn
2011-11-23 16:55             ` Vasiliy Kulikov
2011-11-23 17:00               ` Serge Hallyn
2011-11-28 18:12               ` Kees Cook
2011-11-28 18:14                 ` Vasiliy Kulikov
2011-11-28 19:16 ` [RFC -resend] " Vasiliy Kulikov
2011-11-28 19:35   ` Kees Cook
2011-11-28 20:15     ` Kees Cook
2011-11-28 20:00   ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.00.1111020735080.11087@tundra.namei.org \
    --to=jmorris@namei.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®