From: Kees Cook <kees.cook@canonical.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4] security: Yama LSM
Date: Tue, 29 Jun 2010 17:49:12 -0700 [thread overview]
Message-ID: <20100630004911.GI4837@outflux.net> (raw)
In-Reply-To: <alpine.LRH.2.00.1006300854170.14620@tundra.namei.org>
Hi,
On Wed, Jun 30, 2010 at 09:18:32AM +1000, James Morris wrote:
> On Mon, 28 Jun 2010, Kees Cook wrote:
>
> > This adds the Yama Linux Security Module to collect several security
> > features (symlink, hardlink, and PTRACE restrictions) that have existed
> > in various forms over the years and have been carried outside the mainline
> > kernel by other Linux distributions like Openwall and grsecurity.
> >
> > Signed-off-by: Kees Cook <kees.cook@canonical.com>
>
> There were no further complaints, and we seem to have reached a workable
> consensus on the topic.
>
> It's not clear yet whether existing LSMs will modify their base policies
> to incorporate these protections, utilize the Yama code more directly, or
> implement some combination of both.
I'm hoping we can implement really simple chaining -- nothing fancy.
Trying to chain comprehensive LSMs seems like it will always fail, but
putting little LSMs in front of big LSMs seems like an easy win.
> If you're a user of an existing LSM and want these protections, bug the
> developers for a solution :-)
>
> Applied to
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next
Thanks!
-Kees
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2010-06-30 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 18:42 [PATCH v4] security: Yama LSM Kees Cook
2010-06-29 23:18 ` James Morris
2010-06-30 0:49 ` Kees Cook [this message]
2010-06-30 8:44 ` Christian Stroetmann
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=20100630004911.GI4837@outflux.net \
--to=kees.cook@canonical.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).