Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Svfk2-0004j1-1l for bitcoin-development@lists.sourceforge.net; Mon, 30 Jul 2012 02:29:54 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.47 as permitted sender) client-ip=209.85.160.47; envelope-from=da2ce7@gmail.com; helo=mail-pb0-f47.google.com; Received: from mail-pb0-f47.google.com ([209.85.160.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Svfk1-0006bQ-9o for bitcoin-development@lists.sourceforge.net; Mon, 30 Jul 2012 02:29:54 +0000 Received: by pbbrq2 with SMTP id rq2so8264262pbb.34 for ; Sun, 29 Jul 2012 19:29:47 -0700 (PDT) Received: by 10.68.241.35 with SMTP id wf3mr31251257pbc.102.1343615387406; Sun, 29 Jul 2012 19:29:47 -0700 (PDT) Received: from [192.168.178.20] (124-168-89-46.dyn.iinet.net.au. [124.168.89.46]) by mx.google.com with ESMTPS id rs4sm6891289pbc.0.2012.07.29.19.29.44 (version=SSLv3 cipher=OTHER); Sun, 29 Jul 2012 19:29:46 -0700 (PDT) Message-ID: <5015F197.4040302@gmail.com> Date: Mon, 30 Jul 2012 12:29:43 +1000 From: Cameron Garnham User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <201207291715.15969.luke@dashjr.org> In-Reply-To: <201207291715.15969.luke@dashjr.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) 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 (da2ce7[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (da2ce7[at]gmail.com) -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: 1Svfk1-0006bQ-9o Subject: Re: [Bitcoin-development] Signing release binaries 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: Mon, 30 Jul 2012 02:29:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm not a vendor, however I have a code-signing key for windows; I could sign the windows installer and binary. On 30/07/2012 3:15 AM, Luke-Jr wrote: > On Sunday, July 29, 2012 10:17:51 AM Mike Hearn wrote: >> I guess Gavin would be the final signer. > > Considering that Gavin is not interested in participating in any way in the > stable versions, I would prefer to see someone else responsible for OS-vendor > signing. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlAV8ZYACgkQBJ8cMDO159ZNVgD+KsQUlNcTDSmTGaHvLbAw0Cxy OCDfnsFbaiLoX2xWP3MBAOnN/QvcYY8f2WzMfI+N1PfnydRYGxlkA2JZ2Nrtnxcv =qeUe -----END PGP SIGNATURE-----