Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 8 Oct 2012 13:00:55 -0700
From: Kees Cook <>
To: Corey Bryant <>
Cc:, Julia Lawall <>, 
	James Morris <>, Theodore Tso <>, Paul Moore <>, 
	Eric Paris <>, Tyler Hicks <>,,, Dan Carpenter <>, 
	Fengguang Wu <>
Subject: Re: Re: Linux Security Workgroup

On Mon, Oct 8, 2012 at 10:52 AM, Corey Bryant <> wrote:
> Here's a start on the wiki.  There's not really a whole lot on it other than
> what we've discussed on the list, but it's a start.  Comments and updates
> are very much welcome.

Cool! This looks good.

We may want to add a mailing list pointer to this top-level page, so
people can find this list more directly.

> A couple of questions:
>  * What should the work group's scope be?  The charter mentions " ...
> on-going security verification of Linux kernel subsystems ... ".  I was
> thinking it would focus more on items like: fuzzing, static analysis,
> education for reviewing code, tooling/build security enhancements.  But I
> have a feeling it will start to include Kernel development projects too.

I think it should, yes. Finding bugs is, of course, important, but I'd
like to have a single point of contact for development tasks too.

>  * Where should we document inactive, but desired, projects?  I know Kees
> has but I'm
> wondering if it makes sense to keep track of work items on the same wiki.

I'll take a TODO to build up a Development section on the wiki and
move things from the ubuntu wik


Kees Cook
Chrome OS Security

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.