All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: kernel-hardening@lists.openwall.com,
	Kees Cook <keescook@chromium.org>,
	Julia Lawall <julia.lawall@lip6.fr>,
	James Morris <jmorris@namei.org>, Theodore Tso <tytso@google.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 17:11 -0400	[thread overview]
Message-ID: <3030787.3cWGHfsCdK@sifl> (raw)
In-Reply-To: <507312C2.3070704@linux.vnet.ibm.com>

On Monday, October 08, 2012 01:52:02 PM 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.
> 
> http://kernsec.org/wiki/index.php/Linux_Security_Workgroup

Thanks for pulling this together.

I haven't forgotten about my TODO from the summit to look into running 
Coverity on the upstream kernel on a regular basis, I've just been stuck on 
other things since returning.  Unfortunately, the next couple of weeks will be 
a bit tricky too, but I hope to be able to report something back in early 
November.

-- 
paul moore
security and virtualization @ redhat

  parent reply	other threads:[~2012-10-08 21:11 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
2012-10-08 21:11         ` Paul Moore [this message]
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=3030787.3cWGHfsCdK@sifl \
    --to=pmoore@redhat.com \
    --cc=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=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 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.