From: Christian Stroetmann <stroetmann@ontolinux.com>
To: ext Kees Cook <kees.cook@canonical.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: Wed, 23 Jun 2010 08:03:08 +0200 [thread overview]
Message-ID: <4C21A39C.6040406@ontolinux.com> (raw)
In-Reply-To: <20100622160613.GC5876@outflux.net>
On 22.06.2010 18:06, ext Kees Cook wrote:
> Hi Dmitry,
>
> On Tue, Jun 22, 2010 at 03:25:36PM +0300, Dmitry Kasatkin wrote:
>
>> What is YAMA?
>>
> "Yama" is just the name of the LSM. It's inspired by:
> http://en.wikipedia.org/wiki/Yama
>
Really?
>
>> Where is the tree?
>>
> At the moment:
> http://kernel.ubuntu.com/git?p=kees/linux-2.6.git;a=shortlog;h=refs/heads/yama
>
> -Kees
>
"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).
Christian Stroetmann
next prev parent reply other threads:[~2010-06-23 6:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100621213424.GG24749@outflux.net>
[not found] ` <201006220028.o5M0Sbx7062650@www262.sakura.ne.jp>
2010-06-22 1:14 ` [PATCH] security: Yama LSM Kees Cook
2010-06-22 12:25 ` Dmitry Kasatkin
2010-06-22 16:06 ` ext Kees Cook
2010-06-23 6:03 ` Christian Stroetmann [this message]
2010-06-23 6:22 ` Kees Cook
2010-06-23 6:43 ` Christian Stroetmann
2010-06-23 7:01 ` Kees Cook
2010-06-23 9:16 ` Alan Cox
2010-06-21 21:34 Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2010-06-21 21:34 Kees Cook
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=4C21A39C.6040406@ontolinux.com \
--to=stroetmann@ontolinux.com \
--cc=kees.cook@canonical.com \
--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).