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.LRH.1.10.0901040125190.2418@twin.jikos.cz>
Date:	Sun, 4 Jan 2009 01:28:27 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Gabor MICSKO <gmicsko@...il.com>
cc:	torvalds@...ux-foundation.org, 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.

I think that the main question here is -- what exact features are you 
missing in the vanilla Linux kernel that grsecurity provides?

Over past months/years, vanilla kernel gained some of the features that 
were initially present only in the PaX/grsecurity patchsets (address space 
layout randomization for x86, to name the one that I have been involved 
in myself).
Other things (roles? && access control stuff ) could be achieved by code 
that is already present in the vanilla kernel (selinux, smack and 
friends).

Thanks,

-- 
Jiri Kosina
SUSE Labs

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