From: Peng Fan <peng.fan@nxp.com>
To: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Cc: "keescook@chromium.org" <keescook@chromium.org>
Subject: contribute to KSPP
Date: Thu, 14 Nov 2019 01:29:33 +0000 [thread overview]
Message-ID: <AM0PR04MB4481EB76361DB1681D1F265488710@AM0PR04MB4481.eurprd04.prod.outlook.com> (raw)
Hi,
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.
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
move kernel stack to vmap area
KASLR for ARM
Protect ARM vector
Thanks,
Peng.
next reply other threads:[~2019-11-14 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 1:29 Peng Fan [this message]
2019-11-18 17:16 ` contribute to KSPP Kees Cook
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=AM0PR04MB4481EB76361DB1681D1F265488710@AM0PR04MB4481.eurprd04.prod.outlook.com \
--to=peng.fan@nxp.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.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;
as well as URLs for NNTP newsgroup(s).