[arch-dev-public] providing grsecurity in [community]

Daniel Micay danielmicay at gmail.com
Fri Apr 18 04:44:16 EDT 2014

On 18/04/14 04:09 AM, Sébastien Luttringer wrote:
> On 16/04/2014 06:09, Daniel Micay wrote:
>> To go along with this, I'm interested in maintaining the grsecurity
>> kernel and userspace tools in [community] to provide a hardened kernel
>> and role-based access control system. 
> How do you/we will handle off stream kernel modules rebuild? Each
> modules maintainer will have to create a new version for this kernel and
> update it when you push a new version, right?

I could build these myself when I push a new version, because there
aren't many of them. I don't think it makes sense to bother with the
nvidia module because it would be a bit silly to mix it with grsecurity.

grsecurity almost always follows the point releases of the previous
kernel version longer than Arch keeps them around, so any real work to
migrate to the new kernel version would already be done and easily
copied over.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20140418/fb3e0aae/attachment.asc>

More information about the arch-dev-public mailing list