summaryrefslogtreecommitdiff
path: root/08/261619829a1260c7768a4b4fd45acdf4c8abe9
blob: 5aa7189bd5f5163d19c88186f5c3751354e7f596 (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mark@monetize.io>) id 1WaXYO-0003Tj-Bp
	for bitcoin-development@lists.sourceforge.net;
	Wed, 16 Apr 2014 21:39:36 +0000
Received: from mail-pa0-f44.google.com ([209.85.220.44])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WaXYN-0005RO-9f
	for bitcoin-development@lists.sourceforge.net;
	Wed, 16 Apr 2014 21:39:36 +0000
Received: by mail-pa0-f44.google.com with SMTP id bj1so11382352pad.17
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 16 Apr 2014 14:39:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:message-id:date:from:organization:user-agent
	:mime-version:to:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=rszGRVrmYxz9xNM1RdUaacQRaEsesIJCyrfeRGdJu6k=;
	b=dz+IXuykEXzY5KBlVas9C7X0oS84JI23Cw54Ozm/3f70ZIw+peZPxj0iHOttNMtSn8
	esIs8WEi5MowU3zwJwlreCD6qdakOZaFyVdkrd+Y+oBTHLALJGTTqL3j6U+2fBU2KOrm
	arPr4tu2uvOtOLxtzbd8Wn5wD8eAreinYtv/U3tvFdbtZEO54whBauOgHmM8QZr7d4lt
	1Ezi84XxVrKK94uT7T8OJNcno2kZUuzQ1P/bESc+uEO8zQLE2XwZayQr9oGdB3YTQqHm
	fpGulvfv5Q2dFwF1yk2BChJLiafhXdHlr9QOqiL3OLG/ARplp+BOk8B8Dd/yYIOOR9rs
	bKUg==
X-Gm-Message-State: ALoCoQloTUFvjAuJv7YkQRj0cDLGWL+uJuC6lqLA/7pUGLQ18H9D2vQifkKUSbPEI6UXW0aGxngA
X-Received: by 10.68.231.35 with SMTP id td3mr11009490pbc.137.1397684369185;
	Wed, 16 Apr 2014 14:39:29 -0700 (PDT)
Received: from [192.168.127.194] (50-0-36-93.dsl.dynamic.sonic.net.
	[50.0.36.93]) by mx.google.com with ESMTPSA id
	pv4sm49057292pbb.55.2014.04.16.14.39.28
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 16 Apr 2014 14:39:28 -0700 (PDT)
Message-ID: <534EF88F.0@monetize.io>
Date: Wed, 16 Apr 2014 14:39:27 -0700
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
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>
In-Reply-To: <534EF64C.8050000@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1WaXYN-0005RO-9f
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 21:39:36 -0000

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.