mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabor MICSKO <gmicsko@gmail.com>
To: torvalds@linux-foundation.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Grsecurity is about to be discontinued, unless...
Date: Sat, 03 Jan 2009 21:06:16 +0100	[thread overview]
Message-ID: <1231013176.6497.20.camel@localhost.localdomain> (raw)

Hi,

As most of you probably know, a GPL licensed security solution called
grsecurity [1] has been available for the Linux kernel since a while. It
has a rather impressive list of features [2]. The lead developer has
been maintaining patches for the 2.4 and the 2.6 branch for many years.

According to their developers, the patch includes various advanced
security aspects which inspired several further projects [3].

A week ago, the latest - and probably the last - release was published.
The main developer lost its sole sponsor due to the financial crisis, so
the future of the project is in danger. As a result, the future
development of PaX [4], one of the definitive components of grsecurity
is also in deep trouble [5].

In the past, there have been several requests toward the Linux
developers to include grsecurity and PaX in the mainline kernel
[6][7][8], but in vain.

The common opinion of the developers of grsecurity, PaX and their users
is that acceptance of the code into the kernel would be the best
solution for saving the project, beside finding another long-term
sponsor.

Before the project would finally die, I would like to draw your
attention to the question of integration into the kernel again.

In short, I would like to know what is your answer to this request. And
in the case if you see no chance for the integration, I would like to
know what is the reason behind this decision.

[1] http://www.grsecurity.net
[2] http://www.grsecurity.net/features.php
[3] http://grsecurity.net/~spender/grsecurity_pax-influence.png
[4] http://pax.grsecurity.net/
[5] http://www.grsecurity.net/news.php#grsec2112
[6] http://lkml.org/lkml/2003/4/20/13
[7] http://lkml.indiana.edu/hypermail/linux/net/0602.0/0020.html
[8] http://lkml.org/lkml/2005/1/13/184


Thanks and best regards,


-- 
Gabor MICSKO - http://hup.hu


             reply	other threads:[~2009-01-03 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 20:06 Gabor MICSKO [this message]
2009-01-03 20:16 ` Linus Torvalds
2009-01-04  4:51   ` Valdis.Kletnieks
2009-01-04  0:28 ` Jiri Kosina

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=1231013176.6497.20.camel@localhost.localdomain \
    --to=gmicsko@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®