blob: 3a7aa7e5d17089806b11769e3a8c29986bc9d2e0 (
plain)
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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YWXke-0000BI-Bz
for bitcoin-development@lists.sourceforge.net;
Fri, 13 Mar 2015 22:08:16 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.180 as permitted sender)
client-ip=209.85.223.180; envelope-from=mh.in.england@gmail.com;
helo=mail-ie0-f180.google.com;
Received: from mail-ie0-f180.google.com ([209.85.223.180])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YWXkc-0000tQ-90
for bitcoin-development@lists.sourceforge.net;
Fri, 13 Mar 2015 22:08:16 +0000
Received: by iegc3 with SMTP id c3so132741098ieg.3
for <bitcoin-development@lists.sourceforge.net>;
Fri, 13 Mar 2015 15:08:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.28.8 with SMTP id x8mr88305277igg.19.1426284488480; Fri,
13 Mar 2015 15:08:08 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.36.54.147 with HTTP; Fri, 13 Mar 2015 15:08:08 -0700 (PDT)
In-Reply-To: <55035EAC.80201@localhost.local>
References: <55034205.4030607@localhost.local>
<CANEZrP2OM6BrEsgqe5j23qaZp7wypOFJOZf+cNuMMe12WBv8LA@mail.gmail.com>
<55035EAC.80201@localhost.local>
Date: Fri, 13 Mar 2015 15:08:08 -0700
X-Google-Sender-Auth: geBA-lWJ7t2ot-mJZt6Qxm0lC4w
Message-ID: <CANEZrP0c04KrpjNTsANPhrK_NchQ+aP=yOtRV+5GMBsKWKREkQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Justus Ranvier <justusranvier@riseup.net>
Content-Type: multipart/alternative; boundary=089e015386d648e014051132bc26
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: 1YWXkc-0000tQ-90
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Criminal complaints against "network
disruption as a service" startups
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, 13 Mar 2015 22:08:16 -0000
--089e015386d648e014051132bc26
Content-Type: text/plain; charset=UTF-8
>
> I'm not talking about keeping logs, I mean purporting to be a network
> peer in order to gain a connection slot and then not behaving as one
> (not relaying transactions)
That definition would include all SPV clients?
I get what you are trying to do. It just seems extremely tricky.
--089e015386d648e014051132bc26
Content-Type: text/html; charset=UTF-8
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm not talking about keeping logs, I mean purporting to be a network<br>
peer in order to gain a connection slot and then not behaving as one<br>
(not relaying transactions)</blockquote><div><br></div><div>That definition would include all SPV clients?</div><div><br></div><div>I get what you are trying to do. It just seems extremely tricky.</div></div></div></div>
--089e015386d648e014051132bc26--
|
