All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: 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: Fri, 01 Feb 2013 09:33:16 -0500	[thread overview]
Message-ID: <510BD22C.2010100@linux.vnet.ibm.com> (raw)
In-Reply-To: <874nhxb16r.fsf@codemonkey.ws>



On 01/31/2013 02:30 PM, Anthony Liguori wrote:
> Kees Cook <keescook@chromium.org> writes:
>
>> On Thu, Jan 31, 2013 at 7:34 AM, Corey Bryant <coreyb@linux.vnet.ibm.com> wrote:
>>> In light of events like this http://lwn.net/Articles/535149/ "China, GitHub
>>> and the man-in-the-middle (Greatfire)", we are thinking that a guide for
>>> securing open source projects is needed.  For example, recommending pull
>>> requests or commits be PGP signed are a few things we've discussed that
>>> could defend against a MITM attack inserting malicious code.
>>>
>>> Does anyone have any thoughts as to where we could publish such a guide?
>>> Perhaps the Linux Foundation?
>>>
>>> I believe we have the resources on this mailing list to work through the
>>> details and put together a succinct guide that we could take to a wider
>>> audience.
>>
>> Yeah, sounds good. I think we could easily use the kernel-security
>> wiki to work on it initially, and if it needs a different home in the
>> end, we can move it then.
>
> If someone picks a home, I'll do a brain dump of some of my concerns and
> what I think can be done about it.
>
> Regards,
>
> Anthony Liguori
>

That would be great.  Thanks Anthony.

-- 
Regards,
Corey Bryant

>>
>> -Kees
>>
>> --
>> Kees Cook
>> Chrome OS Security
>
>
>

  reply	other threads:[~2013-02-01 14:33 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 [this message]
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
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=510BD22C.2010100@linux.vnet.ibm.com \
    --to=coreyb@linux.vnet.ibm.com \
    --cc=aliguori@us.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.