From: Kees Cook <keescook@chromium.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: contribute to KSPP
Date: Mon, 18 Nov 2019 09:16:20 -0800 [thread overview]
Message-ID: <201911180912.B860362F@keescook> (raw)
In-Reply-To: <AM0PR04MB4481EB76361DB1681D1F265488710@AM0PR04MB4481.eurprd04.prod.outlook.com>
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
next prev parent reply other threads:[~2019-11-18 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 1:29 contribute to KSPP Peng Fan
2019-11-18 17:16 ` Kees Cook [this message]
2019-11-25 12:29 ` Peng Fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201911180912.B860362F@keescook \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=peng.fan@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox