linux-kernel - Re: Grsecurity is about to be discontinued, unless...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0901031210260.3179@localhost.localdomain>
Date:	Sat, 3 Jan 2009 12:16:50 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Gabor MICSKO <gmicsko@...il.com>
cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: Grsecurity is about to be discontinued, unless...

On Sat, 3 Jan 2009, Gabor MICSKO wrote:
> 
> 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.

Quite frankly, historically the patches have been a mis-match of

 - some sane stuff

 - lots of totally insane and very annoying and invasive code.

an example of the second class is the totally idiotic "emulate NX bit - 
badly - with code segment limits" kind of patches. These kinds of patches 
only add unmaintainable crap that isn't even relevant in the long run, and 
thus any sane maintainer (me) should refuse to take them.

The apparent inability (and perhaps more importantly - total 
unwillingless) from the PaX team to be able to see what makes sense in a 
long-term general kernel and what does not, and split things up and try to 
push the sensible things up (and know which things are too ugly or too 
specialized to make sense), caused many PaX features to never be merged.

Much of it did get merged over the years (mostly because some people spent 
the time to separate things out), but no, we're not going to suddenly 
start merging code like that just because the project is in trouble. None 
of the basic issues have been solved.

			Linus
--
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/