1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
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 <peter@coinlab.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CANEZrP045E8zh+tJ5YSwXPWxLq9x-HRFTUrAwXxki_B6LLxtGA@mail.gmail.com>
From: Peter Vessenes <peter@coinlab.com>
In-Reply-To: <CANEZrP045E8zh+tJ5YSwXPWxLq9x-HRFTUrAwXxki_B6LLxtGA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 29 Jul 2012 21:20:44 +0900
Message-ID: <7209155576954731078@unknownmsgid>
To: Mike Hearn <mike@plan99.net>
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 <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Signing release binaries
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <mike@plan99.net> 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
|
