From: Kees Cook <keescook@chromium.org>
To: tech-board-discuss@lists.linux-foundation.org
Subject: [Tech-board-discuss] Standing for 2022 TAB election
Date: Mon, 29 Aug 2022 12:04:31 -0700 [thread overview]
Message-ID: <202208291129.C5D1CCF6E@keescook> (raw)
Hello,
I'm volunteering again to stand for election to the Technical Advisory
Board.
My primary concern for the kernel is security. I'm a member of the
security@kernel.org response team, lead the Kernel Self-Protection
Project[1], maintain[2] for the kernel hardening, seccomp, and pstore
trees, and am a co-maintainer of the exec and binfmt tree. As a result, I
frequently work kernel-wide across many subsystems (or many architectures)
when helping land various security defenses. This cross-maintainer work is
a unique social and technical challenge, and the topic of "security" is
a similarly wide and unique challenge. I'd like to continue to represent
both of these concerns on the TAB.
In addition, I also bring several "downstream" perspectives on how the
kernel is consumed, from those of a general-purpose distro (having worked
on Ubuntu's security team) to those of special-purpose device vendors
(having worked with Chrome OS, Google Cloud, and Android).
Notable over my last 2 years on the TAB was helping review hundreds
of patches from UMN and showing that the incident[3] was one of
misunderstanding and lack of education rather than of malice. I helped
with the final report, and coordinated the creation of the base Researcher
Guideline documentation[4]. I've also continued to support[5] the TAB's
online election process.
Thank you for your consideration,
-Kees
[1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project
[2] https://lore.kernel.org/lkml/?q=f%3A%22Kees+Cook%22+s%3A%22GIT+PULL%22
[3] https://lore.kernel.org/lkml/202105051005.49BFABCE@keescook/
[4] https://www.kernel.org/doc/html/latest/process/researcher-guidelines.html
[5] https://github.com/kees/kernel-tools/blob/trunk/identity-canonicalizer
--
Kees Cook
reply other threads:[~2022-08-29 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202208291129.C5D1CCF6E@keescook \
--to=keescook@chromium.org \
--cc=tech-board-discuss@lists.linux-foundation.org \
/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