All of lore.kernel.org
 help / color / mirror / Atom feed
From: Solar Designer <solar@openwall.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>,
	kernel-hardening@lists.openwall.com
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Kees Cook <keescook@chromium.org>,
	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: Wed, 6 Feb 2013 03:09:10 +0400	[thread overview]
Message-ID: <20130205230910.GB14416@openwall.com> (raw)
In-Reply-To: <511150AA.5@linux.vnet.ibm.com>

On Tue, Feb 05, 2013 at 01:34:18PM -0500, Corey Bryant wrote:
> I haven't heard any objections to using the oss-security wiki to host 
> the guide, so I've created a page here.  A brain dump would be a much 
> appreciated start to get things moving.  Thanks!
> 
> http://oss-security.openwall.org/wiki/secure-oss-dev-guide

This is a good start, although I'd call the page "development",
"development-guide", "secure-development", or maybe even
"secure-development-guide" for search engine friendliness. ;-)
We already have "oss" and "security" in the URL anyway, so the
non-redundant words are only "development" and "guide" (can omit the
latter since it's less informative). ;-)

On a more serious note, I think you need to announce this on the
oss-security mailing list.

Thanks,

Alexander

  reply	other threads:[~2013-02-05 23:09 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 [this message]
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
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=20130205230910.GB14416@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.