All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
Cc: Chris Wright <chris@wirex.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: grsecurity in 2.5?
Date: Mon, 21 Apr 2003 16:39:41 -0700	[thread overview]
Message-ID: <20030421163941.E11886@figure1.int.wirex.com> (raw)
In-Reply-To: <1050968186.3065.16.camel@flat41>; from gj@pointblue.com.pl on Tue, Apr 22, 2003 at 12:36:26AM +0100

* Grzegorz Jaskiewicz (gj@pointblue.com.pl) wrote:

> Maybe we should start to bring them piece by piece, fe. PaX first and
> others. 

PaX is an example of something that won't port to LSM.  The grsecurity
MAC, RBAC, chroot restrictions, TPE are the types of things that would port
nicely.

> Question is not that will somebody do that, i am sure of that - grsec is
> needed in 2.4 - and it will be needed in 2.6. Question is, if it will be
> included in mainstream kernel release ?

I don't expect to see it in 2.6 mainline at all.  The patch could be
reduced if some of the core access control logic was placed in an LSM.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2003-04-21 23:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-20  8:23 grsecurity in 2.5? Zoltan NAGY
2003-04-21 21:25 ` Greg KH
2003-04-21 21:37   ` Zoltan NAGY
2003-04-21 21:38     ` Chris Wright
2003-04-21 23:36       ` Grzegorz Jaskiewicz
2003-04-21 23:39         ` Chris Wright [this message]
2003-04-21 21:45     ` Valdis.Kletnieks
2003-04-21 22:04       ` Chris Wright

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=20030421163941.E11886@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=gj@pointblue.com.pl \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.