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
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
|
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 <will.yager@gmail.com>) id 1WGjw2-0003wE-Nu
for bitcoin-development@lists.sourceforge.net;
Fri, 21 Feb 2014 06:50:10 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.53 as permitted sender)
client-ip=209.85.219.53; envelope-from=will.yager@gmail.com;
helo=mail-oa0-f53.google.com;
Received: from mail-oa0-f53.google.com ([209.85.219.53])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WGjw1-0001SB-Ns
for bitcoin-development@lists.sourceforge.net;
Fri, 21 Feb 2014 06:50:10 +0000
Received: by mail-oa0-f53.google.com with SMTP id m1so3499902oag.26
for <bitcoin-development@lists.sourceforge.net>;
Thu, 20 Feb 2014 22:50:04 -0800 (PST)
X-Received: by 10.60.115.68 with SMTP id jm4mr1443759oeb.45.1392965404380;
Thu, 20 Feb 2014 22:50:04 -0800 (PST)
Received: from wireless-10-148-122-32.public.utexas.edu
(nat-128-62-71-162.public.utexas.edu. [128.62.71.162])
by mx.google.com with ESMTPSA id g4sm7334210obe.5.2014.02.20.22.50.02
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 20 Feb 2014 22:50:02 -0800 (PST)
Content-Type: multipart/signed;
boundary="Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574";
protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: William Yager <will.yager@gmail.com>
In-Reply-To: <CA+s+GJAgs7otQB_tQNCntZ5gR+gp3+PfA+iiKPsjLu2oenaSUA@mail.gmail.com>
Date: Fri, 21 Feb 2014 00:50:01 -0600
Message-Id: <AB055C1C-76B1-4CE3-B92E-253C1C9541F6@gmail.com>
References: <CAJHLa0OD7w0Rs5ygAE4C14EWm1=x57YHG2kOee1pzxvj3FQ38g@mail.gmail.com>
<CANEZrP2siw9hGPVsPjQ6WyohacOrs8rqs5p9ZsFY5kF0URnPWg@mail.gmail.com>
<CA+s+GJCRqqmoHkmsq+6x9Wm6btKzdXoPjw5Af8zRDEkDE+6+zw@mail.gmail.com>
<CA+s+GJAgs7otQB_tQNCntZ5gR+gp3+PfA+iiKPsjLu2oenaSUA@mail.gmail.com>
To: Wladimir <laanwj@gmail.com>
X-Mailer: Apple Mail (2.1827)
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
(will.yager[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: 1WGjw1-0001SB-Ns
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: 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: Fri, 21 Feb 2014 06:50:10 -0000
--Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574
Content-Type: multipart/alternative;
boundary="Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C"
--Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
Running the network part of the core as a system service might make =
sense for server implementations, but it=92s a pain in the rear for most =
users.=20
That said, I think segregating the two processes is a great idea. Let=92s =
just try to avoid some complicated scheme that involves necessarily =
running things under multiple users.
Will
On Feb 21, 2014, at 0:43, Wladimir <laanwj@gmail.com> wrote:
> The most straightforward way would be to run the blockchain daemon as =
a system service (with its own uid/gid and set of Apparmor/SELinux =
restrictions) and the wallet daemon as the user.
--Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Running the network part of the core as a system =
service might make sense for server implementations, but it=92s a pain =
in the rear for most users. <div><br></div><div>That said, I think =
segregating the two processes is a great idea. Let=92s just try to avoid =
some complicated scheme that involves necessarily running things under =
multiple users.</div><div><br></div><div>Will</div><div><br><div><div>On =
Feb 21, 2014, at 0:43, Wladimir <<a =
href=3D"mailto:laanwj@gmail.com">laanwj@gmail.com</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: =
none; display: inline !important;">The most straightforward way would be =
to run the blockchain daemon as a system service (with its own uid/gid =
and set of Apparmor/SELinux restrictions) and the wallet daemon as the =
user.</span></blockquote></div><br></div></body></html>=
--Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C--
--Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJTBvcZAAoJEP6RFSSE221wdXIH/0xBay/rS9lAUSS616fRGY+G
PQnlJyNcXKdBFUytqFWjTUTE6Rg0TV3boR1NhPgIs7KmSdgTahUABEJlkbdwTZsB
Mw6KE+tGBn0of5qvZajBcRB8LUExuJlthRDu8Dqobs0veAzAcZkzlWJb+x+TQcW4
fEMTPSzdJYgGHZFd25zfJxbZXdDv/YdH5g+3pP+sc/O1wxL79IZ2V5qbN1Fom+Gl
QZGO65W2EY2L0ycmB6aiG02cLa0rdtz86xXaRYJrbDMs/6DQz917DmKD0WomXbg7
yaeKofSx8lnFufySKd0G9bPb+5hGlfeyJuvsSVa9HtH10/yVMCsFCEGaTps3mTg=
=h4z6
-----END PGP SIGNATURE-----
--Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574--
|
