Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UNPzc-0001aB-KX for bitcoin-development@lists.sourceforge.net; Wed, 03 Apr 2013 15:52:56 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.128.170 as permitted sender) client-ip=209.85.128.170; envelope-from=grarpamp@gmail.com; helo=mail-ve0-f170.google.com; Received: from mail-ve0-f170.google.com ([209.85.128.170]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UNPzb-0000le-J2 for bitcoin-development@lists.sourceforge.net; Wed, 03 Apr 2013 15:52:56 +0000 Received: by mail-ve0-f170.google.com with SMTP id 15so1821896vea.15 for ; Wed, 03 Apr 2013 08:52:50 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.58.205.179 with SMTP id lh19mr1689422vec.7.1365004370003; Wed, 03 Apr 2013 08:52:50 -0700 (PDT) Received: by 10.220.115.7 with HTTP; Wed, 3 Apr 2013 08:52:49 -0700 (PDT) In-Reply-To: References: <20130401225107.GU65880@giles.gnomon.org.uk> <20130401225417.GV65880@giles.gnomon.org.uk> Date: Wed, 3 Apr 2013 11:52:49 -0400 Message-ID: From: grarpamp To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (grarpamp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1UNPzb-0000le-J2 Subject: Re: [Bitcoin-development] bitcoin pull requests X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2013 15:52:56 -0000 >> gpg signing commits, like the Linux kernel > Though, honestly, when I ACK that means I read the code, which is more > important than the author really. github seems fine for that still, > though I do wonder if there is a race possible, > > * just before I click "pull", sneak rebases the branch to something evil You might want to look at http://www.monotone.ca/, it does a good job of integrating crypto and review primitives into the workflow. It also has some reliable network distribution models (netsync) that work well over things like Tor, in case a new developer (or old Satoshi) doesn't wish to be in the public light. http://www.monotone.ca/monotone.html Once you have the crypto, it always boils down to human risk factors, rogue, password, cracks, etc which are harder.