public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: GCS <gcs@lsc.hu>
Cc: Nico Schottelius <nico-kernel@schottelius.org>,
	Chris Wright <chrisw@osdl.org>, Amon Ott <ao@rsbac.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dev@grsecurity.net
Subject: Re: security patches / lsm
Date: Wed, 9 Jun 2004 13:46:15 +0200	[thread overview]
Message-ID: <20040609114615.GK601@schottelius.org> (raw)
In-Reply-To: <20040609112235.GA1088@pooh>

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

GCS [Wed, Jun 09, 2004 at 01:22:35PM +0200]:
> * Nico Schottelius <nico-kernel@schottelius.org> [2004-06-09 11:03:46 +0200]:
> 
> > Who decides whether to integrate them or not?
>  Linus? AFAIK he already said no to grsecurity.

I heard about that, but I wanted to know whether this statement is still
true. I think with grsecurity you get a great security enhanced kernel.

And if the performance is really getting worse, why not add grsecurity
patches with #ifdef GRSECURITY_ENABLED? 

Nico

-- 
Keep it simple & stupid, use what's available.
Please use pgp encryption: 8D0E 27A4 is my id.
http://nerd-hosting.net | http://nico.schotteli.us

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2004-06-09 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 19:11 security patches / lsm Nico Schottelius
2004-01-22 23:09 ` Chris Wright
2004-06-09  9:03   ` Nico Schottelius
2004-06-09 11:22     ` GCS
2004-06-09 11:46       ` Nico Schottelius [this message]
2004-06-09 12:37         ` Olaf Hering
2004-06-09 16:28         ` Valdis.Kletnieks
2004-06-09 14:15     ` Greg KH
2004-06-09 17:40     ` Chris Wright
2004-06-12 19:55       ` Nico Schottelius

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=20040609114615.GK601@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --cc=ao@rsbac.org \
    --cc=chrisw@osdl.org \
    --cc=dev@grsecurity.net \
    --cc=gcs@lsc.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox