From: Solar Designer <solar@openwall.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: kernel-hardening@lists.openwall.com,
Kees Cook <keescook@chromium.org>,
Anthony Liguori <aliguori@us.ibm.com>,
Frank Novak <fnovak@us.ibm.com>,
George Wilson <gcwilson@us.ibm.com>,
Joel Schopp <jschopp@linux.vnet.ibm.com>,
Kevin Wolf <kwolf@redhat.com>,
Warren Grunbok II <wgrunbok@vnet.ibm.com>
Subject: Re: [kernel-hardening] Secure Open Source Project Guide
Date: Fri, 1 Feb 2013 19:08:09 +0400 [thread overview]
Message-ID: <20130201150809.GA11114@openwall.com> (raw)
In-Reply-To: <510BD433.2020803@linux.vnet.ibm.com>
On Fri, Feb 01, 2013 at 09:41:55AM -0500, Corey Bryant wrote:
> Thanks Alexander. I agree, this really is targeting OSS in general so I
> think it makes sense to move to the oss-security mailing list and wiki.
> Is anyone opposed to this or have a better idea?
>
> And maybe we can find a good place to link to our Linux Security
> Workgroup wiki on the OSS wiki:
> http://kernsec.org/wiki/index.php/Linux_Security_Workgroup
For now, we can add it to:
http://oss-security.openwall.org/wiki/links
Please feel free to do that. And yes, maybe we can find/add a better
place for links to closely related projects maintained by people who are
also active in the oss-security group. Maybe have a Related Projects
section right on the main oss-security wiki page?
Alexander
next prev parent reply other threads:[~2013-02-01 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 15:34 [kernel-hardening] Secure Open Source Project Guide Corey Bryant
2013-01-31 18:37 ` Kees Cook
2013-01-31 19:30 ` Anthony Liguori
2013-02-01 14:33 ` Corey Bryant
2013-02-05 18:34 ` Corey Bryant
2013-02-05 23:09 ` Solar Designer
2013-01-31 21:10 ` Corey Bryant
2013-01-31 23:18 ` Peter Huewe
2013-02-01 14:36 ` Corey Bryant
2013-02-01 14:17 ` Solar Designer
2013-02-01 14:41 ` Corey Bryant
2013-02-01 15:08 ` Solar Designer [this message]
2013-02-05 18:37 ` Corey Bryant
2013-02-06 7:02 ` Shawn
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=20130201150809.GA11114@openwall.com \
--to=solar@openwall.com \
--cc=aliguori@us.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=fnovak@us.ibm.com \
--cc=gcwilson@us.ibm.com \
--cc=jschopp@linux.vnet.ibm.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kwolf@redhat.com \
--cc=wgrunbok@vnet.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.