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
|
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 <dtrammell@dustintrammell.com>) id 1WH1U4-0000P2-Co
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Feb 2014 01:34:28 +0000
X-ACL-Warn:
Received: from mail-ob0-f175.google.com ([209.85.214.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WH1U0-0006Vi-3Y
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Feb 2014 01:34:28 +0000
Received: by mail-ob0-f175.google.com with SMTP id va2so1976998obc.20
for <bitcoin-development@lists.sourceforge.net>;
Fri, 21 Feb 2014 17:34:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to
:references:content-type:mime-version;
bh=EZItk8CXJ3TvPcnZGNqHvB3MMxfOh0vZGQa8VGB/5rg=;
b=D7D0kav6uR+RRAJT0WDEiP8jVJ3a+JQGJABv3piIDdmfxEnZnTHcTHCy5GnJ7+7MMc
SFmnucEJFr7FenmobPxvvEneGgxRkp++5/bVKQqt2UNsnchBqvRSaSAoCt8LxXifju2G
ig7orCr9ufROaPiosXpSKN9if7jQAnl1rosJ3nF5WzgoSo6910iYlXbZxu8NFRNJ/+OJ
0gCOD/NboAETqfEV/e3V9OlvDrFrecBBuV8RmS9cWcd/a1qZ69PYEiOae/b2GRgxY11z
YI/dIIu7M7ko9aWqFEC/uhq2eugCLquGexb1MoL0d0XlVo4IfrQ/G+ijf7jsvsb9EYgx
+X6w==
X-Gm-Message-State: ALoCoQke1CPmvmbpn5wGNMgQjY9lhtI+0opj3w2r6yuVRgFdOhu1ixXX5BnZGeJRLNS3b87pCS3g
X-Received: by 10.60.58.234 with SMTP id u10mr12862909oeq.72.1393031068503;
Fri, 21 Feb 2014 17:04:28 -0800 (PST)
Received: from [10.3.3.33] ([24.153.183.182])
by mx.google.com with ESMTPSA id x3sm50809019oek.3.2014.02.21.17.04.27
for <multiple recipients>
(version=SSLv3 cipher=RC4-SHA bits=128/128);
Fri, 21 Feb 2014 17:04:27 -0800 (PST)
Message-ID: <1393031052.6897.89.camel@staypuft>
From: "Dustin D. Trammell" <dtrammell@dustintrammell.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 21 Feb 2014 19:04:12 -0600
In-Reply-To: <CAJHLa0OD7w0Rs5ygAE4C14EWm1=x57YHG2kOee1pzxvj3FQ38g@mail.gmail.com>
References: <CAJHLa0OD7w0Rs5ygAE4C14EWm1=x57YHG2kOee1pzxvj3FQ38g@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1";
protocol="application/pgp-signature";
boundary="=-DDMAKObny8wqS66TMtRl"
X-Mailer: Evolution 3.2.3-0ubuntu6
Mime-Version: 1.0
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: 1WH1U0-0006Vi-3Y
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core trial balloon: splitting
blockchain engine and wallet
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: Sat, 22 Feb 2014 01:34:28 -0000
--=-DDMAKObny8wqS66TMtRl
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Fri, 2014-02-21 at 01:09 -0500, Jeff Garzik wrote:
> Recent IRC discussion have floated a rough proposal for a wallet
> next-step: Running the Bitcoin Core wallet as a separate process, a
> separate binary, from the blockchain engine. The wallet process would
> communicate with the blockchain engine using existing RPC and P2P
> channels, becoming a real SPV client. This accomplishes a
> longstanding security goal of sandboxing away wallet keys and
> sensitive data from the network-exposed P2P engine, in a separate
> process, among other benefits.
PLEASE.
For those of us that prefer the reference software and also manage
multiple wallets, having to store a copy of the blockchain for each one
eats up disk space quite quickly. If I could run a local blockchain
server (or a local network one, even) and then have whichever wallet I
start up use that instead of maintain its own copy of the blockchain, my
world would be much, much happier.
Sandboxing keys and sensitive wallet data away from the attack surface
introduced by the network interfaces into another separate process is
also a good security move. Don't forget to sanitize your IPC inputs (:
Thanks,
--=20
Dustin D. Trammell
dtrammell@dustintrammell.com
http://www.dustintrammell.com
--=-DDMAKObny8wqS66TMtRl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEABECAAYFAlMH94wACgkQ9tleUv2mbhbFWACeIowC2oHzB6cZBfILO4Lrxkb8
reAAn2zGRiIQ3ugf4SNF1vMSR2VBqVPa
=Yre3
-----END PGP SIGNATURE-----
--=-DDMAKObny8wqS66TMtRl--
|
