From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SvSsO-0003Wc-Jx for bitcoin-development@lists.sourceforge.net; Sun, 29 Jul 2012 12:45:40 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of coinlab.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=peter@coinlab.com; helo=mail-gg0-f175.google.com; Received: from mail-gg0-f175.google.com ([209.85.161.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SvSsN-0005hJ-KJ for bitcoin-development@lists.sourceforge.net; Sun, 29 Jul 2012 12:45:40 +0000 Received: by ggnp4 with SMTP id p4so4158731ggn.34 for ; Sun, 29 Jul 2012 05:45:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=7S/bq0QVvcwm5oRP/GKJPPT1O2+yEiYmaBeq3vgYW2w=; b=ic4m9mVPUgGmvTTb4AjINLwqHn4EGyJTV/+wOXoyLu397KICTYvG9FWxBr0CSTZ6W2 lNANCqKDB3uYTew7YcsKqQu6+3aP8CMxLUXsvaTader0Grwsx59093SYNrBnmifafeMk EzBJ7P7srEhfZobaHZDWJ5HL8OFn4kfPPW4tPwEwv/R+3RmRrkK2XxaFgShIwND13kU/ O4xofvbctj1YanGAGpZrU7dAxemctNvdjwWkdHs1ZFRvQ3ADCET8Iz/LOaAYdEr2Bzvk R+OWc2Ctqww11AbkMUqFRPP0Bsii+Qyr64kR3OMwGm7egUfJ5/gU1790ALv4H+gH7i41 C/AQ== Received: by 10.42.255.68 with SMTP id nh4mr4855448icb.38.1343564446655; Sun, 29 Jul 2012 05:20:46 -0700 (PDT) References: From: Peter Vessenes In-Reply-To: Mime-Version: 1.0 (1.0) Date: Sun, 29 Jul 2012 21:20:44 +0900 Message-ID: <7209155576954731078@unknownmsgid> To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQm/qv++54uGKYWaqGNy8pNg9w9WXAndP7947Bx/AwWVuRB4zI4dNFcBhr12e7X6pcuW6Xw8 X-Spam-Score: -1.0 (-) 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 SPF_PASS SPF: sender matches SPF record 0.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SvSsN-0005hJ-KJ Cc: Bitcoin Dev 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: Sun, 29 Jul 2012 12:45:40 -0000 This is a good idea. I think I can come up with the cash, I will follow up with gavin. Sent from my smartphone! On Jul 29, 2012, at 7:18 PM, Mike Hearn wrote: > MacOS X 10.8 makes application signing borderline mandatory, in that > you cannot run unsigned apps unless you tweak your settings via the > control panel. You must sign with a certificate issued by Apple via > their "identified developer" program. > > Windows allows but does not require signing. However, anti-virus > systems tend to use signers with good reputation as a whitelisting > signal. Signing Bitcoin releases makes sense because it may lead to, > at minimum, higher performance if AV engines ignore file reads/writes > by Bitcoin. And it can also shield us from false positives. You only > need to see the mess that the mining tools world has become to > understand why this is important. > > As I don't take part in the release process, I can't help out with > this directly, but I believe it's important and would be willing to > throw some money in towards buying the signing certs for both > platforms. I guess Gavin would be the final signer. > > ------------------------------------------------------------------------------ > 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