From: Kees Cook <kees@kernel.org>
To: tech-board-discuss@lists.linux.dev
Subject: Standing for 2024 TAB election
Date: Thu, 5 Sep 2024 10:20:38 -0700 [thread overview]
Message-ID: <202409051004.05F71EE560@keescook> (raw)
Hello!
I'm volunteering again to stand for election to the LF Technical
Advisory Board.
My primary concern for Linux is its security. I'm a member of the
security@kernel.org response team, lead the Kernel Self-Protection
Project[1], maintain[2] the kernel hardening, seccomp, and pstore trees,
and co-maintain 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 lead
Ubuntu's security team) to those of special-purpose device vendors
(having worked on Chrome OS, Android, and Google Cloud).
Some examples of my contributions over the last 2 years on the TAB were
helping respond to the XZ backdoor[3], examining past XZ kernel commits,
and reviewing various community support documents like the Linux Kernel
Contribution Maturity Model[4]. I've also continued to support[5] the
TAB's online election process, with regular refreshes of contributor
metrics.
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/202403291221.124220E0F4@keescook/
https://lore.kernel.org/tech-board-discuss/202404151051.90B786EE85@keescook/
[4] https://git.kernel.org/linus/10a29eb658b3039eccfa6f249da079194f535a9a
[5] https://github.com/kees/kernel-tools/blob/trunk/identity-canonicalizer
--
Kees Cook
reply other threads:[~2024-09-05 17:20 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=202409051004.05F71EE560@keescook \
--to=kees@kernel.org \
--cc=tech-board-discuss@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).