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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WUXGB-0003hz-D7
for bitcoin-development@lists.sourceforge.net;
Mon, 31 Mar 2014 08:07:59 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.178 as permitted sender)
client-ip=209.85.213.178; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f178.google.com;
Received: from mail-ig0-f178.google.com ([209.85.213.178])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WUXGA-00065e-H4
for bitcoin-development@lists.sourceforge.net;
Mon, 31 Mar 2014 08:07:59 +0000
Received: by mail-ig0-f178.google.com with SMTP id hn18so3195185igb.11
for <bitcoin-development@lists.sourceforge.net>;
Mon, 31 Mar 2014 01:07:53 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.57.19 with SMTP id we19mr430818icb.89.1396253273125; Mon,
31 Mar 2014 01:07:53 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Mon, 31 Mar 2014 01:07:53 -0700 (PDT)
Date: Mon, 31 Mar 2014 10:07:53 +0200
Message-ID: <CA+s+GJDHBZVYdN_KWdLm9-dBa6mJb2y1=sqZ=nAeJbOjQXN_kg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=bcaec51b20295c79e804f5e28c03
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: 1WUXGA-00065e-H4
Subject: [Bitcoin-development] Anyone using bitcoind that needs RPC bound to
interface? [testing needed]
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: Mon, 31 Mar 2014 08:07:59 -0000
--bcaec51b20295c79e804f5e28c03
Content-Type: text/plain; charset=UTF-8
A while ago I created a patch to make it possible to bind the RPC port to a
specific address or even multiple address/port pairs.
https://github.com/bitcoin/bitcoin/pull/3695
I'm fairly confident that it works, but it cannot hurt if some people that
need this functionality tested it before merge. Test results from normal
setups as well as weird corner cases (IPv4+IPv6, VPNs, ...) are welcome.
Regards,
Wladimir
--bcaec51b20295c79e804f5e28c03
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><br>A while ago I created a patch to make it possible=
to bind the RPC port to a specific address or even multiple address/port p=
airs.<br><br><a href=3D"https://github.com/bitcoin/bitcoin/pull/3695">https=
://github.com/bitcoin/bitcoin/pull/3695</a><br>
<br></div><div>I'm fairly confident that it works, but it cannot hurt i=
f some people that need this functionality tested it before merge. Test res=
ults from normal setups as well as weird corner cases (IPv4+IPv6, VPNs, ...=
) are welcome.<br>
</div><div><br></div><div>Regards,<br></div>Wladimir<br><br></div>
--bcaec51b20295c79e804f5e28c03--
|
