[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201911180912.B860362F@keescook>
Date: Mon, 18 Nov 2019 09:16:20 -0800
From: Kees Cook <keescook@...omium.org>
To: Peng Fan <peng.fan@....com>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: contribute to KSPP
On Thu, Nov 14, 2019 at 01:29:33AM +0000, Peng Fan wrote:
> Hi,
Hi! Welcome to the list!
> I work for NXP Linux Kernel team, my work are mostly ARM64/ARM SoC BSP,
> embedded virtualization, bootloader development.
>
> I came across KSPP, find this is an attractive project. And would
> like to do some contribution.
>
> Not sure https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Work
> is still up to date.
I've been slowly transitioning the TODO list to a github issue tracker
here:
https://github.com/KSPP/linux/issues/
> If you have any items not owned, please share me the info. Currently I am
> going through the kernel items, such as the following form ARM/ARM64:
> split thread_info off to kernel stack
https://github.com/KSPP/linux/issues/1
> move kernel stack to vmap area
https://github.com/KSPP/linux/issues/2
> KASLR for ARM
https://github.com/KSPP/linux/issues/3
> Protect ARM vector
https://github.com/KSPP/linux/issues/13
All four of those apply only to arm32. arm64 either has them already
(first three), or it doesn't apply (protect vector, IIUC, is
arm32-specific).
I'm not aware of anyone working on those currently, so they would be
very welcome! :)
Thanks for reaching out!
--
Kees Cook
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.
