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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pieter.wuille@gmail.com>) id 1WaXsg-0004LF-UN
for bitcoin-development@lists.sourceforge.net;
Wed, 16 Apr 2014 22:00:34 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.174 as permitted sender)
client-ip=209.85.223.174; envelope-from=pieter.wuille@gmail.com;
helo=mail-ie0-f174.google.com;
Received: from mail-ie0-f174.google.com ([209.85.223.174])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WaXsg-0005tG-9w
for bitcoin-development@lists.sourceforge.net;
Wed, 16 Apr 2014 22:00:34 +0000
Received: by mail-ie0-f174.google.com with SMTP id rp18so11115710iec.19
for <bitcoin-development@lists.sourceforge.net>;
Wed, 16 Apr 2014 15:00:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.136.130 with SMTP id u2mr4467860ict.51.1397685628985;
Wed, 16 Apr 2014 15:00:28 -0700 (PDT)
Received: by 10.50.141.135 with HTTP; Wed, 16 Apr 2014 15:00:28 -0700 (PDT)
In-Reply-To: <534EF88F.0@monetize.io>
References: <CA+s+GJDdENtqQt1f+L5htuuyPxUxsq0prLQFBLirTjJz0nG1gw@mail.gmail.com>
<534E9DDC.7000502@gmail.com>
<CAPg+sBg-LBHx4sTR1QuK_-t1Yb+N+Vsi9BsyQ41vaWB6gFEHvw@mail.gmail.com>
<20140416204223.GL59714@giles.gnomon.org.uk>
<07D78278-F882-42D3-AD52-84D168F104D2@heliacal.net>
<534EF64C.8050000@gmail.com> <534EF88F.0@monetize.io>
Date: Thu, 17 Apr 2014 00:00:28 +0200
Message-ID: <CAPg+sBi4QSpxSo8DBFuJR5ca1vuXYdauf5puPiY4js7Fvq+bLQ@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Mark Friedenbach <mark@monetize.io>
Content-Type: text/plain; charset=ISO-8859-1
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
(pieter.wuille[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: 1WaXsg-0005tG-9w
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Warning message when running wallet in
Windows XP (or drop support?)
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, 16 Apr 2014 22:00:35 -0000
On Wed, Apr 16, 2014 at 11:39 PM, Mark Friedenbach <mark@monetize.io> wrote:
> On 04/16/2014 02:29 PM, Kevin wrote:
>> Okay, so how about an autoupdate function which pulls a work around off
>> the server? Sooner or later, the vulnerabilities must be faced.
>
> NO. Bitcoin Core will never have an auto-update functionality. That
> would be a single point of failure whose compromise could result in the
> theft of every last bitcoin held in a Bitcoin Core wallet.
Or, even accidentally, cause a hard forking bug to be rolled out (or
worsen one).
--
Pieter
|
