[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5jJpVgGqZKpFamF8urWxOd349QmUK4T3PV2nLG5agij0hw@mail.gmail.com>
Date: Tue, 19 Jan 2016 15:59:46 -0800
From: Kees Cook <keescook@...omium.org>
To: "Schaufler, Casey" <casey.schaufler@...el.com>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: Still working on PAX_USERCOPY
On Thu, Jan 14, 2016 at 5:43 PM, Schaufler, Casey
<casey.schaufler@...el.com> wrote:
> Just a brief status update on my work on PAX_USERCOPY. I’ve ditched my first
> two attempts at doing somewhat simple minded cut’n’patch and am going to
> have to take a more engineering (e.g. understanding what’s really going on)
> approach. The good news is that I’ve made enough mistakes to think there
> aren’t that many left for a project this size.
Thanks for the report! Were you able to use or improve on the
lib/test_user_copy.c tests during your experiments? (Or maybe we just
need a separate lkdtm test?)
What kinds of dead-ends did you run into?
-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.
