From: James Morris <jmorris@namei.org>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Kernel security
Date: Fri, 29 Sep 2017 08:50:12 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1709290833470.15742@namei.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1709231416010.10766@namei.org>
On Sat, 23 Sep 2017, James Morris wrote:
> I'd like to propose a kernel security tech topic, where we can discuss
> current development issues, with both core kernel folk and European
> security developers who may not have attended LSS.
>
> Potential agenda items include:
>
> - KSPP update (Kees Cook)
> - TPM status (Jarkko, if available)
> - LSS & LPC container security discussion readout (myself)
>
> And possibly other items depending on who is available at the conference,
> and how much time is available for the topic.
Another potential topic would be whether we can provide better review of
crypto users within the kernel.
One idea would be to create a mailing list for this purpose, which
developers can cc: if they are posting new code or updates to code which
uses the crypto API. We could encourage folk with crypto design &
analysis skills (who may not necessarily be kernel developers, or
following every possibly related mailing list) to help out with crypto
review.
It seems worth discussing, in any case.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2017-09-28 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 4:24 [Ksummit-discuss] [TECH TOPIC] Kernel security James Morris
2017-09-28 17:27 ` Jarkko Sakkinen
2017-10-09 16:23 ` Jarkko Sakkinen
2017-10-12 11:21 ` Jarkko Sakkinen
2017-09-28 22:50 ` James Morris [this message]
2017-09-28 23:09 ` Jason A. Donenfeld
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=alpine.LRH.2.21.1709290833470.15742@namei.org \
--to=jmorris@namei.org \
--cc=Jason@zx2c4.com \
--cc=ebiggers@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.