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
|
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 <laanwj@gmail.com>) id 1WH6Sy-0000nT-Ba
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Feb 2014 06:53:40 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.43 as permitted sender)
client-ip=209.85.214.43; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f43.google.com;
Received: from mail-bk0-f43.google.com ([209.85.214.43])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WH6Sx-00076i-GE
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Feb 2014 06:53:40 +0000
Received: by mail-bk0-f43.google.com with SMTP id v15so37158bkz.16
for <bitcoin-development@lists.sourceforge.net>;
Fri, 21 Feb 2014 22:53:33 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.205.75.74 with SMTP id yz10mr2519852bkb.43.1393052013165;
Fri, 21 Feb 2014 22:53:33 -0800 (PST)
Received: by 10.205.75.72 with HTTP; Fri, 21 Feb 2014 22:53:33 -0800 (PST)
In-Reply-To: <1393031340.6897.90.camel@staypuft>
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>
<1393031340.6897.90.camel@staypuft>
Date: Sat, 22 Feb 2014 07:53:33 +0100
Message-ID: <CA+s+GJD=-Y5e7jfBt8Ced-2wXkjYcODBKrre2jqT-k-tQO8fCQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: "Dustin D. Trammell" <dtrammell@dustintrammell.com>
Content-Type: multipart/alternative; boundary=f46d04103737662d9a04f2f93267
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: 1WH6Sx-00076i-GE
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: Sat, 22 Feb 2014 06:53:40 -0000
--f46d04103737662d9a04f2f93267
Content-Type: text/plain; charset=UTF-8
On Sat, Feb 22, 2014 at 2:09 AM, Dustin D. Trammell <
dtrammell@dustintrammell.com> wrote:
> On Fri, 2014-02-21 at 07:43 +0100, Wladimir 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.
>
> This assumes you as a user have the rights to do so. This would be
> preferred, but in some cases may not be possible. Perhaps it should be
> optional?
>
No! I'm proposing that we force everyone to do it. Using all means
necessary. There should be regular audits that everyone is running the
software exactly in my configuration, and if not, a special task force will
take care that spankings are carried out on the spot.
Repeated offenders will lose their BitLicense.
</s>
Please stop kicking this dead horse. It was just a random idea. Maybe a way
how Linux distributions could structure it, but it may or may not apply in
your case. And that's fine, this is free software development, you can do
whatever you want!
Let's try to bring this discussion back to its original intention: for
anyone that wants to concretely help this along, please help reviewing and
testing the pull requests that jgarzik mentions.
Wladimir
BTW: All of those patches are helpful for monolithic-bitcoind as well as
they (lay the groundwork for) speeding up block synchronization.
--f46d04103737662d9a04f2f93267
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sat, Feb 22, 2014 at 2:09 AM, Dustin D. Trammell <span dir=3D"ltr"><<=
a href=3D"mailto:dtrammell@dustintrammell.com" target=3D"_blank">dtrammell@=
dustintrammell.com</a>></span> wrote:<br>
<blockquote 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;p=
adding-left:1ex"><div class=3D"">On Fri, 2014-02-21 at 07:43 +0100, Wladimi=
r wrote:<br>
> The most straightforward way would be to run the blockchain daemon as<=
br>
> a system service (with its own uid/gid and set of Apparmor/SELinux<br>
> restrictions) and the wallet daemon as the user.<br>
<br>
</div>This assumes you as a user have the rights to do so. =C2=A0This would=
be<br>
preferred, but in some cases may not be possible. =C2=A0Perhaps it should b=
e<br>
optional?<br></blockquote><div><br></div><div>No! I'm proposing that we=
force everyone to do it. Using all means necessary. There should be regula=
r audits that everyone is running the software exactly in my configuration,=
and if not, a special task force will take care that spankings are carried=
out on the spot.</div>
<div><br></div><div>Repeated offenders will lose their BitLicense.</div><di=
v></s><br></div><div><br></div><div>Please stop kicking this dead hor=
se. It was just a random idea. Maybe a way how Linux distributions could st=
ructure it, but it may or may not apply in your case. And that's fine, =
this is free software development, you can do whatever you want!</div>
<div><br></div><div>Let's try to bring this discussion back to its orig=
inal intention: for anyone that wants to concretely help this along, please=
help reviewing and testing the pull requests that jgarzik mentions.</div>
<div><br></div><div>Wladimir<br></div><div><div>BTW: All of those patches a=
re helpful for monolithic-bitcoind as well as they (lay the groundwork for)=
speeding up block synchronization.</div></div><div><br></div></div></div>
</div>
--f46d04103737662d9a04f2f93267--
|
