[Ksummit-discuss] [TECH TOPIC] Kernel security

[Ksummit-discuss] [TECH TOPIC] Kernel security

[James Morris]

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.


-- 
James Morris
<jmorris@namei.org>

Re: [Ksummit-discuss] [TECH TOPIC] Kernel security

[Jarkko Sakkinen]

On Sat, 2017-09-23 at 14:24 +1000, 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

I apologize for late response. I just sent a travel request and should get
response next week.

/Jarkko

Re: [Ksummit-discuss] [TECH TOPIC] Kernel security

[James Morris]

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>

Re: [Ksummit-discuss] [TECH TOPIC] Kernel security

[Jason A. Donenfeld]

On Fri, Sep 29, 2017 at 12:50 AM, James Morris <jmorris@namei.org> wrote:
> 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.

To cross-post what I wrote in our other thread, which wasn't CCd to this list:

> I won't be at kernel summit, regrettably, but I do intend to
> methodically work through the kernel reviewing the various crypto
> [mis]uses in places. I also have some larger plans regarding reworking
> a few aspects of the crypto API, that I'll start a discussion with
> Herbert about during the next several months.
> So, expect some more things like this patch to gradually be rolling
> your way, along with maybe larger overall changes. If you wind up
> discussing this in any substantial way at the summit this year, please
> do try to loop me in at some point.

So, I really like the idea of having a dedicated mailing list or even
a simple email alias for that kind of discussion. I know a few
pure-academics who would actually be interested in participating in
that, and personally I'm kind of existing in the void between the
kernel world and the crypto world, so that sort of list is of course
interesting to me.

One potential difficulty with "security-related" lists, and
crypto-related things in particular, is that there are often many
people eager to share misinformation or who read Schneier way back
when and then... Anyway, I suspect at kernel summit, a discussion will
yield some way to approach that.

Jason

Re: [Ksummit-discuss] [TECH TOPIC] Kernel security

[Jarkko Sakkinen]

On Thu, Sep 28, 2017 at 08:27:59PM +0300, Jarkko Sakkinen wrote:
> On Sat, 2017-09-23 at 14:24 +1000, 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
> 
> I apologize for late response. I just sent a travel request and should get
> response next week.
> 
> /Jarkko

My travel request was accepted. I will be available.

/Jarkko

Re: [Ksummit-discuss] [TECH TOPIC] Kernel security

[Jarkko Sakkinen]

On Mon, Oct 09, 2017 at 07:23:25PM +0300, Jarkko Sakkinen wrote:
> On Thu, Sep 28, 2017 at 08:27:59PM +0300, Jarkko Sakkinen wrote:
> > On Sat, 2017-09-23 at 14:24 +1000, 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
> > 
> > I apologize for late response. I just sent a travel request and should get
> > response next week.
> > 
> > /Jarkko
> 
> My travel request was accepted. I will be available.
> 
> /Jarkko

My flights have been booked. Is there a speaker code I should use when I
register?

/Jarkko