[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jLbhCVxEce0czNRY8VSOC+BBZzqEjUNbTB8gp5EoA7+bg@mail.gmail.com>
Date: Fri, 11 Dec 2015 10:44:40 -0800
From: Kees Cook <keescook@...omium.org>
To: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Cc: "Schaufler, Casey" <casey.schaufler@...el.com>, Catalin Marinas <catalin.marinas@....com>,
PaX Team <pageexec@...email.hu>, Michael Ellerman <mpe@...erman.id.au>,
Heiko Carstens <heiko.carstens@...ibm.com>, Ralf Baechle <ralf@...ux-mips.org>
Subject: Re: Self Introduction
On Fri, Dec 11, 2015 at 9:54 AM, <Valdis.Kletnieks@...edu> wrote:
> On Thu, 10 Dec 2015 11:45:35 -0800, Kees Cook said:
>> On Thu, Dec 10, 2015 at 11:38 AM, Schaufler, Casey
>
>> That's great! Thanks for speaking up. Another area that hasn't seen
>> any traction yet is PAX_USERCOPY. Valdis seems to be MIA, so I'd love
>> to see someone else take on that chunk of work.
>
> Whoops. sorry.. I just didn't have anything in a state ready to share,
> and I got sidetracked by a week in the hospital (am all OK now, thankfully).
Yikes! Glad you're okay. If other people have more time to dedicate to
PAX_USERCOPY extraction, maybe you could help with testing? Or what do
you think?
> Biggest problem is just taking one big 7M patch and teasing out just the
> USERCOPY parts, and then re-arranging it into something that upstream will
> be willing to take. Just lots and lots of grunt work.
Yup, that's the first step in the work. Well, first is extraction,
then figuring out the best way to upstream.
> I don't suppose the grsecurity guys have a git repo where a lot of the
> heavy duty lifting is already done? :)
AIUI, no such thing exists. :)
-Kees
--
Kees Cook
Chrome OS & Brillo Security
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.
