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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1XFke4-0007wa-Fj
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 13:55:48 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.48 as permitted sender)
client-ip=209.85.219.48; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f48.google.com;
Received: from mail-oa0-f48.google.com ([209.85.219.48])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XFke3-000679-J4
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 13:55:48 +0000
Received: by mail-oa0-f48.google.com with SMTP id m1so4019383oag.7
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 Aug 2014 06:55:42 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.224.227 with SMTP id rf3mr30714176obc.70.1407506142144;
Fri, 08 Aug 2014 06:55:42 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Fri, 8 Aug 2014 06:55:42 -0700 (PDT)
In-Reply-To: <CA+s+GJBuyn2xYeBoh9r4E=qjHdrti6u1K6cApYbgROs2CpPukQ@mail.gmail.com>
References: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>
<CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com>
<CA+s+GJD+9qpwFcVfHOCCsFYjmk7A0V=65vG-7jJ6D7jj4Pi_7g@mail.gmail.com>
<CANEZrP245242JYDBBo72XVmKgEBO96QPjcJi8Jy2Dm_r90n1Bw@mail.gmail.com>
<CAJHLa0N3xx1QZ==iSLYNsdgkBGoqN34+4eVtukkjn+3SrDhC7A@mail.gmail.com>
<CANEZrP1mhSodC-ZvkuVKAgHO44bM7QX=RivRDhnDeHOKr8PXqQ@mail.gmail.com>
<CA+s+GJCbCRQP_w3g-0qtA6K8qrf6ywNfJ9d1367gSTfgCwgU2Q@mail.gmail.com>
<CANEZrP2UFMDJ+88MU=RTyU4FV_HCHwuHLmd5S9aK2AZ7DJ+j7g@mail.gmail.com>
<CA+s+GJBuyn2xYeBoh9r4E=qjHdrti6u1K6cApYbgROs2CpPukQ@mail.gmail.com>
Date: Fri, 8 Aug 2014 15:55:42 +0200
X-Google-Sender-Auth: cLgropYW0OFcZpRF9sYYyjoR_8k
Message-ID: <CANEZrP2GeX9VLqD7p7uCBN6QrYo6LfGj0pNJthk2LjLkVLNFmA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=089e013a05de9f336c05001e8fcd
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1XFke3-000679-J4
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related
services
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, 08 Aug 2014 13:55:48 -0000
--089e013a05de9f336c05001e8fcd
Content-Type: text/plain; charset=UTF-8
>
> I'd be OK with such an idea if bitcoind listens on a separate port for
> connections from plugins, a port that cannot be used for normal P2P
> traffic. This could also be a UNIX socket instead of a TCP port.
Yes, can be done this way too. I was thinking about setups where you have
services distributed across multiple machines. However a separate port does
indeed allow iptables or the like to be used.
--089e013a05de9f336c05001e8fcd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">I'd be OK with such an idea if bitcoind list=
ens on a separate port for<br>
connections from plugins, a port that cannot be used for normal P2P<br>
traffic. This could also be a UNIX socket instead of a TCP port.</blockquot=
e><div><br></div><div>Yes, can be done this way too. I was thinking about s=
etups where you have services distributed across multiple machines. However=
a separate port does indeed allow iptables or the like to be used.=C2=A0</=
div>
</div></div></div>
--089e013a05de9f336c05001e8fcd--
|
