[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151108104517.GC8632@chrystal.uk.oracle.com>
Date: Sun, 8 Nov 2015 11:45:17 +0100
From: Quentin Casasnovas <quentin.casasnovas@...cle.com>
To: kernel-hardening@...ts.openwall.com
Subject: Re: Re: Kernel Self Protection Project
On Sat, Nov 07, 2015 at 10:50:04PM -0800, Kees Cook wrote:
> On Sat, Nov 7, 2015 at 1:52 AM, Quentin Casasnovas
> <quentin.casasnovas@...cle.com> wrote:
> >>
> >> I actually think that just splitting out features might be a good
> >> first step all around. Most folks aren't very familiar with the
> >> PaX/Grsec patches, and they, in their monolithic nature, can be hard
> >> to understand. Many depend on each other, but some are separable.
> >>
> >
> > Agreed, that should be a required step before people can review.
>
> Yeah. Does anyone want to also extract PAX_USERCOPY or
> GRKERNSEC_KSTACKOVERFLOW ? No one has mentioned an interest in those
> yet.
>
I could have a look at splitting GRKERNSEC_KSTACKOVERFLOW on my free time
if no-one beats me to it.
Quentin
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
