From: Jason Cooper <jason@lakedaemon.net>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Self-nomination
Date: Wed, 27 Jul 2016 14:27:16 +0000 [thread overview]
Message-ID: <20160727142715.GQ4541@io.lakedaemon.net> (raw)
All,
I'd like to nominate myself for attending this year's KS. My primary
focus is in security topics. Signature management, secure boot, the
kernel-hardening efforts. Particularly on embedded systems. [0]
Since applying updates is a key security trait, I'm very interested in
discussing the stable workflow, safety review, and code minimization
efforts. In particular, ways to make it easier for vendors to provide
updates and for users to apply them.
I'm also perennially interested in co-maintainer workflows, especially
when sub-maintainers are contributing their trees to linux-next.
If anyone is interested in discussing hobbyists and recruitment, I'm
game. But it looks like that would be hallway track this year. Or,
over a beer or three. ;-)
thx,
Jason.
[0] I've been doing a lot of work over the past year or so on secure
communications and building trust in their foundations. In particular,
methods for developing strong entropy pools at early boot on
legacy/feature-less embedded systems. So, I'd love to meet with folks
also interested in this to discuss and share ideas.
next reply other threads:[~2016-07-27 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 14:27 Jason Cooper [this message]
2016-07-27 16:19 ` Jonathan Cameron
2016-07-28 18:16 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2016-07-29 16:31 [Ksummit-discuss] self-nomination Stephen Hemminger
2016-07-29 11:57 [Ksummit-discuss] Self-nomination Laurent Pinchart
2016-07-26 2:28 [Ksummit-discuss] self-nomination Wangnan (F)
2016-07-23 20:36 Benjamin Herrenschmidt
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=20160727142715.GQ4541@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linuxfoundation.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