[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKW+fo38ZqNt8u8oW4igY6uRpyfLvU_wD9Aq2zzP0ZVig@mail.gmail.com>
Date: Fri, 16 Dec 2016 10:58:41 -0800
From: Kees Cook <keescook@...omium.org>
To: "Sandra Escandor-O'Keefe" <rvonflugel@...il.com>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
"Reshetova, Elena" <elena.reshetova@...el.com>, Daniel Borkmann <daniel@...earbox.net>
Subject: Re: Working on lib/test_bpf.c tests for eBPF
constant blinding
On Fri, Dec 16, 2016 at 9:13 AM, Sandra Escandor-O'Keefe
<rvonflugel@...il.com> wrote:
> I'm interested in starting on a bit of linux kernel development, and also
> contributing to something security related for the kernel. I was looking at
> the projects listed in the TODO of
> https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project and "Write
> lib/test_bpf.c tests for eBPF constant blinding" caught my eye. Is this
> something that still needs to be done? If so, is there someone specific that
> I can reach out to in order to get some guidance on where to start?
Hi! Welcome to the fun. :)
I've added Elena and Daniel to CC, who both worked on the blinding.
The goal would be to add some kind of test that inserted constants in
eBPF instructions and then verified they were gone in the resulting
eBPF JIT kernel code. Until now, it's only been done manually, and
it'd be nice to have a test that could show if there were regressions
or if an architecture didn't support the blinding in its JIT.
For some background on the blinding, I wrote a short description of it here:
https://outflux.net/blog/archives/2016/10/03/security-things-in-linux-v4-7/
Let me know if that helps get you to a starting point! :)
-Kees
--
Kees Cook
Nexus 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.
