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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1VvPWP-0006im-JV
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Dec 2013 10:47:33 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.67 as permitted sender)
client-ip=209.85.220.67; envelope-from=tier.nolan@gmail.com;
helo=mail-pa0-f67.google.com;
Received: from mail-pa0-f67.google.com ([209.85.220.67])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VvPWO-0004dD-CR
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Dec 2013 10:47:33 +0000
Received: by mail-pa0-f67.google.com with SMTP id rd3so4004754pab.10
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Dec 2013 02:47:26 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.68.178.197 with SMTP id da5mr31696701pbc.28.1387882046491;
Tue, 24 Dec 2013 02:47:26 -0800 (PST)
Received: by 10.70.70.196 with HTTP; Tue, 24 Dec 2013 02:47:26 -0800 (PST)
In-Reply-To: <op.w8k9l8qayldrnw@laptop-air.hsd1.ca.comcast.net>
References: <op.w8k9l8qayldrnw@laptop-air.hsd1.ca.comcast.net>
Date: Tue, 24 Dec 2013 10:47:26 +0000
Message-ID: <CAE-z3OXaucepVnN_GbxVQPyeoxYsPirinfamg7fi9CJEOzuRMA@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b86f8365f135704ee4578b9
X-Spam-Score: 2.1 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: github.com]
-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
(tier.nolan[at]gmail.com)
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?209.85.220.67>]
-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
1.5 SF_NO_SPF_SPAM SF_NO_SPF_SPAM
X-Headers-End: 1VvPWO-0004dD-CR
Subject: Re: [Bitcoin-development] Peer Discovery and Overlay
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: Tue, 24 Dec 2013 10:47:33 -0000
--047d7b86f8365f135704ee4578b9
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Dec 24, 2013 at 8:52 AM, Jeremy Spilman <jeremy@taplink.co> wrote:
> Are there any past instances of applications hijacking or interfacing with
> the exiting p2p messages, or abusing 'getaddr' functionality? Are there
> any guidelines on this, or should there be?
>
>
There was a BIP by Stefan Thomas for adding custom services to the
protocol. Discovery would be helpful here too. If this was added, it
wouldn't be intended for use in a hostile way though.
This one was the custom services BIP. It defines a change to the version
message and also custom sub-commands.
https://github.com/bitcoin/bips/blob/master/bip-0036.mediawiki
This one discusses how network discovery should be handles.
https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_Discovery
--047d7b86f8365f135704ee4578b9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote">On Tue, Dec 24, 2013 at 8:52 AM, Jeremy Spilman <span dir=3D"ltr"><=
;<a href=3D"mailto:jeremy@taplink.co" target=3D"_blank">jeremy@taplink.co</=
a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
Are there any past instances of applications hijacking or interfacing with<=
br>
the exiting p2p messages, or abusing 'getaddr' functionality? Are t=
here<br>
any guidelines on this, or should there be?<br>
<br></blockquote><div><br><div>There was a BIP by <span name=3D"Stefan Thom=
as" class=3D"">Stefan Thomas </span>for adding custom services to the proto=
col.=A0 Discovery would be helpful here too.=A0 If this was added, it would=
n't be intended for use in a hostile way though.<br>
<br></div>This one was the custom services BIP.=A0 It defines a change to t=
he version message and also custom sub-commands.<br><a href=3D"https://gith=
ub.com/bitcoin/bips/blob/master/bip-0036.mediawiki">https://github.com/bitc=
oin/bips/blob/master/bip-0036.mediawiki</a><br>
<br>This one discusses how network discovery should be handles.<br><a href=
=3D"https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_Disc=
overy">https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_D=
iscovery</a><br>
</div></div></div></div></div></div>
--047d7b86f8365f135704ee4578b9--
|
