summaryrefslogtreecommitdiff
path: root/2f/c5bfe2d1ab33417fb5c0e8c8fcabc7852e53b2
blob: d16e5c2f1bf4c3e25665f5756181066b62e7dd2c (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
86
87
88
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1XBlb3-0005iv-JH
	for bitcoin-development@lists.sourceforge.net;
	Mon, 28 Jul 2014 14:08:13 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.176 as permitted sender)
	client-ip=209.85.220.176; envelope-from=gmaxwell@gmail.com;
	helo=mail-vc0-f176.google.com; 
Received: from mail-vc0-f176.google.com ([209.85.220.176])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XBlb1-0001br-Sl
	for bitcoin-development@lists.sourceforge.net;
	Mon, 28 Jul 2014 14:08:13 +0000
Received: by mail-vc0-f176.google.com with SMTP id id10so11206347vcb.35
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 28 Jul 2014 07:08:06 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.221.44.69 with SMTP id uf5mr651948vcb.4.1406556485789; Mon,
	28 Jul 2014 07:08:05 -0700 (PDT)
Received: by 10.53.9.43 with HTTP; Mon, 28 Jul 2014 07:08:05 -0700 (PDT)
In-Reply-To: <06e8ee730ac511617e6c3c4a4bbae4bb@webmail.mckay.com>
References: <CAD5xwhhKKooGBfSY3nZzMmS=3WD=EdX9FQ7mZtQL3fkikuwyLg@mail.gmail.com>
	<20140728024030.GA17724@savin>
	<CAAS2fgR+r6VoUse_ropq=p3WTy_qWq68fpCQim1FhcbkCXYtsQ@mail.gmail.com>
	<E0F82AAE-1B71-4B8B-A5D5-0301BBECC317@osfda.org>
	<53D5BB5F.2060200@bitwatch.co>
	<CAAS2fgRVUbEM=7KQt-Haue=+sgAFu=HrfDdS0hhatNawci_eZQ@mail.gmail.com>
	<CANEZrP10sFWiBv=yi0YaPszzxrygfRhwTP8fdqKapSL1yucfow@mail.gmail.com>
	<b2f6693f-db93-4cb9-9c80-25f123c0b24e@email.android.com>
	<06e8ee730ac511617e6c3c4a4bbae4bb@webmail.mckay.com>
Date: Mon, 28 Jul 2014 07:08:05 -0700
Message-ID: <CAAS2fgQyz-xXp-MZFu4n8gMms9sZrUXbsub4HcWG0SsR3tQ89w@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Robert McKay <robert@mckay.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
	(gmaxwell[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-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: 1XBlb1-0001br-Sl
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Abnormally Large Tor node accepting only
 Bitcoin traffic
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, 28 Jul 2014 14:08:13 -0000

On Mon, Jul 28, 2014 at 5:31 AM, Robert McKay <robert@mckay.com> wrote:
> I don't think Sybil attack is the right term for this.. there is only
> one IP address.. one "identity".

The bitcoin protocol is more or less identityless. It's using up lots
of network capacity, "number of sockets" is as pretty close as you
get.

> I'm not even sure that this behaviour can be considered abuse.. it's
> pretty much following the rules and maybe even improving the transaction
> and block propagation.

It isn't relaying transactions or blocks as far as anyone with a
connection to it can tell.

and sure, probably not much to worry about=E2=80=94 people have been runnin=
g
spy nodes for a long time, at least that much is not new.