From: Kees Cook <kees.cook@canonical.com>
To: Christian Stroetmann <stroetmann@ontolinux.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux File System ML <linux-fsdevel@vger.kernel.org>,
Linux Security Module ML <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] security: Yama LSM
Date: Tue, 22 Jun 2010 23:22:42 -0700 [thread overview]
Message-ID: <20100623062242.GG5876@outflux.net> (raw)
In-Reply-To: <4C21A39C.6040406@ontolinux.com>
On Wed, Jun 23, 2010 at 08:03:08AM +0200, Christian Stroetmann wrote:
> "You've already had those suggestions some days ago. Use a security
> module, either by using something like SELinux (where you can do
> this just fine as far as I can see including exceptions by label for
> problem apps)", [Alan Cox, 2010-06-08], or integrate it into an
> already existing solution eg. grsecurity (www.grsecurity.net).
You appear to be quoting[1], but you left off a bit. To edit it a bit:
"Use a security module, either by using something like SELinux (...),
or write your own little security module that does it."
I have done the latter.
I don't need to integrate this into grsecurity because grsecurity already
has these protections. It is Openwall and grsecurity that I'm using as the
starting point for this attempt at upstreaming the protections.
-Kees
[1] http://lkml.org/lkml/2010/6/8/56
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2010-06-23 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 21:34 Kees Cook
[not found] ` <201006220028.o5M0Sbx7062650@www262.sakura.ne.jp>
2010-06-22 1:14 ` Kees Cook
2010-06-22 12:25 ` Dmitry Kasatkin
2010-06-22 16:06 ` ext Kees Cook
2010-06-23 6:03 ` Christian Stroetmann
2010-06-23 6:22 ` Kees Cook [this message]
2010-06-23 6:43 ` Christian Stroetmann
2010-06-23 7:01 ` Kees Cook
2010-06-23 9:16 ` Alan Cox
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=20100623062242.GG5876@outflux.net \
--to=kees.cook@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stroetmann@ontolinux.com \
/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®