Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 31 Jan 2013 10:37:19 -0800
From: Kees Cook <>
To: "" <>
Cc: Anthony Liguori <>, Frank Novak <>, 
	George Wilson <>, Joel Schopp <>, 
	Kevin Wolf <>, Warren Grunbok II <>
Subject: Re: Secure Open Source Project Guide

On Thu, Jan 31, 2013 at 7:34 AM, Corey Bryant <> wrote:
> In light of events like this "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.


Kees Cook
Chrome OS Security

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.