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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1VyK7a-00016e-I6
for bitcoin-development@lists.sourceforge.net;
Wed, 01 Jan 2014 11:37:58 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.45 as permitted sender)
client-ip=209.85.214.45; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f45.google.com;
Received: from mail-bk0-f45.google.com ([209.85.214.45])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VyK7Z-0006wx-Lb
for bitcoin-development@lists.sourceforge.net;
Wed, 01 Jan 2014 11:37:58 +0000
Received: by mail-bk0-f45.google.com with SMTP id mx13so4300736bkb.32
for <bitcoin-development@lists.sourceforge.net>;
Wed, 01 Jan 2014 03:37:51 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.204.81.7 with SMTP id v7mr24760566bkk.3.1388576271156; Wed,
01 Jan 2014 03:37:51 -0800 (PST)
Received: by 10.204.69.197 with HTTP; Wed, 1 Jan 2014 03:37:51 -0800 (PST)
In-Reply-To: <op.w8z55onhyldrnw@laptop-air.hsd1.ca.comcast.net>
References: <52A3C8A5.7010606@gmail.com>
<1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net>
<52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org>
<CANAnSg2OrmQAcZ+cZdtQeADicH3U29QOgYPfP1AQhOMP6+P1wg@mail.gmail.com>
<CAAS2fgR0khyJxmz9c2Oc87hOFgiNuiPJuaeugGajdo_EcKEW9w@mail.gmail.com>
<20131212205106.GA4572@netbook.cypherspace.org>
<CANAnSg3nPhrk2k=yDKf39AuBQnSuTWJbgANdMhGe=soiOy0NTw@mail.gmail.com>
<CAAS2fgTmWRMxYweu3sNn_X7grgjUqTQujM-DbZRxG_YMZnD=7g@mail.gmail.com>
<CANEZrP2X_63qkuNuk0MvsLR9ewd7HR0mPVaD7bZSgWMTJ5-9FQ@mail.gmail.com>
<CAAS2fgQmMZ6RYjbJ6ZfFO5+ZhZoR4d4yMf8CXLXKPmZt3-Je4Q@mail.gmail.com>
<CANEZrP1mdJNa7ADkUXTGDNKMSCROjGAVbMXZXxodxCz1LFDzZw@mail.gmail.com>
<op.w8y642nryldrnw@laptop-air.hsd1.ca.comcast.net>
<4264e886-48de-40ac-921a-a60502595060@email.android.com>
<op.w8z55onhyldrnw@laptop-air.hsd1.ca.comcast.net>
Date: Wed, 1 Jan 2014 12:37:51 +0100
Message-ID: <CA+s+GJCmnzBEUXQ=4m5OxGeyFbjE39R2DWsmwLqEHfZsaxTcbg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jeremy Spilman <jeremy@taplink.co>
Content-Type: multipart/alternative; boundary=047d7bf0c2c862f56404eee71b81
X-Spam-Score: -0.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
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1VyK7Z-0006wx-Lb
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org,
your thoughts?
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: Wed, 01 Jan 2014 11:37:58 -0000
--047d7bf0c2c862f56404eee71b81
Content-Type: text/plain; charset=UTF-8
>
> In any case, I think wallet users want to know when an upgrade is
> available, and ability to click an 'update' button get a binary they can
> trust. It's not a problem unique to bitcoind, deterministic builds are
> awesome, but I don't think fully solve it.
>
Deterministic builds are one part of the equation. Matt Corallo actually
did implement auto-updating using gitian updater:
https://github.com/bitcoin/bitcoin/pull/1453
It ran into lots of bike shedding and was eventually abandoned, but there
is no question whether it is possible with the current build process.
Wladimir
--047d7bf0c2c862f56404eee71b81
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
In any case, I think wallet users want to know when an upgrade is<br>
available, and ability to click an 'update' button get a binary the=
y can<br>
trust. It's not a problem unique to bitcoind, deterministic builds are<=
br>
awesome, but I don't think fully solve it.<br></blockquote><div><br></d=
iv><div>Deterministic builds are one part of the equation. Matt Corallo act=
ually did implement auto-updating using gitian updater:</div><div><a href=
=3D"https://github.com/bitcoin/bitcoin/pull/1453">https://github.com/bitcoi=
n/bitcoin/pull/1453</a></div>
<div><br></div><div>It ran into lots of bike shedding and was eventually ab=
andoned, but there is no question whether it is possible with the current b=
uild process.</div><div><br></div><div>Wladimir</div><div><br></div></div>
</div></div>
--047d7bf0c2c862f56404eee71b81--
|
