From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Kees Cook <keescook@chromium.org>
Cc: kernel-hardening@lists.openwall.com,
Julia Lawall <julia.lawall@lip6.fr>,
James Morris <jmorris@namei.org>, Theodore Tso <tytso@google.com>,
Paul Moore <pmoore@redhat.com>, Eric Paris <eparis@redhat.com>,
Tyler Hicks <tyhicks@canonical.com>,
zohar@us.ibm.com, john.johansen@canonical.com,
Dan Carpenter <dan.carpenter@oracle.com>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [kernel-hardening] Re: Linux Security Workgroup
Date: Mon, 08 Oct 2012 16:59:29 -0400 [thread overview]
Message-ID: <50733EB1.7050400@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAGXu5j+3hncd2gZXQck+FYO4m6gXEq0abeSgr+eTVREiQQOGAA@mail.gmail.com>
On 10/08/2012 04:00 PM, Kees Cook wrote:
> On Mon, Oct 8, 2012 at 10:52 AM, Corey Bryant <coreyb@linux.vnet.ibm.com> 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.
>>
>> http://kernsec.org/wiki/index.php/Linux_Security_Workgroup
>
> 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.
Good idea, I've added this.
>
>> 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.
>
That's fine with me. I just want to have a clear understanding more
than anything.
>> * Where should we document inactive, but desired, projects? I know Kees
>> has https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening 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
Awesome, thanks!
--
Regards,
Corey Bryant
next prev parent reply other threads:[~2012-10-08 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 19:26 [kernel-hardening] Linux Security Workgroup Corey Bryant
2012-10-02 16:23 ` [kernel-hardening] " Kees Cook
2012-10-02 16:44 ` Corey Bryant
2012-10-02 22:17 ` Kees Cook
2012-10-03 5:38 ` Julia Lawall
2012-10-03 5:45 ` Dan Carpenter
2012-10-03 21:59 ` Corey Bryant
2012-10-04 5:29 ` James Morris
2012-10-08 17:52 ` Corey Bryant
2012-10-08 20:00 ` Kees Cook
2012-10-08 20:59 ` Corey Bryant [this message]
2012-10-08 21:11 ` Paul Moore
2012-10-08 21:49 ` Kees Cook
2012-10-09 14:07 ` Corey Bryant
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=50733EB1.7050400@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=eparis@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=julia.lawall@lip6.fr \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=pmoore@redhat.com \
--cc=tyhicks@canonical.com \
--cc=tytso@google.com \
--cc=zohar@us.ibm.com \
/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 NNTP newsgroup(s).