[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C21AD07.5050201@ontolinux.com>
Date: Wed, 23 Jun 2010 08:43:19 +0200
From: Christian Stroetmann <stroetmann@...olinux.com>
To: Kees Cook <kees.cook@...onical.com>
CC: linux-kernel <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH] security: Yama LSM
On 23.06.2010 08:22, Kees Cook wrote:
> 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.
>
So, this sounds as if you are porting functionalities from grsecurtiy
into LSM. But [1].
> -Kees
>
> [1] http://lkml.org/lkml/2010/6/8/56
>
>
[1] http://www.grsecurity.net/lsm.php
Chrisitan Stroetmann
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists