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
121
122
123
124
125
126
|
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 <mbde@bitwatch.co>) id 1XBbNi-0004Ob-3w
for bitcoin-development@lists.sourceforge.net;
Mon, 28 Jul 2014 03:13:46 +0000
Received: from dd32718.kasserver.com ([85.13.150.64])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1XBbNg-0001FH-E5
for bitcoin-development@lists.sourceforge.net;
Mon, 28 Jul 2014 03:13:46 +0000
Received: from [192.168.100.43]
(dslb-084-059-052-221.084.059.pools.vodafone-ip.de [84.59.52.221])
by dd32718.kasserver.com (Postfix) with ESMTPSA id 9341B4900034
for <bitcoin-development@lists.sourceforge.net>;
Mon, 28 Jul 2014 04:54:26 +0200 (CEST)
Message-ID: <53D5BB5F.2060200@bitwatch.co>
Date: Mon, 28 Jul 2014 04:54:23 +0200
From: "mbde@bitwatch.co" <mbde@bitwatch.co>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
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>
In-Reply-To: <E0F82AAE-1B71-4B8B-A5D5-0301BBECC317@osfda.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1XBbNg-0001FH-E5
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 03:13:46 -0000
These website list Tor nodes by bandwidth:
http://torstatus.blutmagie.de/index.php
https://torstatus.rueckgr.at/index.php?SR=3DBandwidth&SO=3DDesc
And the details reveal it's a port 8333 only exit node:
http://torstatus.blutmagie.de/router_detail.php?FP=3D0d6d2caafbb32ba85ee5=
162395f610ae42930124
blockchain.info has some records about the related IP going back to the
end of this May:
https://blockchain.info/ip-address/5.9.93.101?offset=3D300
-------- Original Message --------
Subject: Re: [Bitcoin-development] Abnormally Large Tor node accepting
only Bitcoin traffic
From: Michael Wozniak <mw@osfda.org>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>, alex@stamos.=
org
Date: Sun, 27 Jul 2014 22:49:11 -0400
> It=92s in my logs:
>=20
> 2014-07-28 02:00:24 receive version message: /Satoshi:0.9.2/: version 7=
0002, blocks=3D302684, us=3D******:8333, them=3D0.0.0.0:0, peer=3D5.9.93.=
101:33928
>=20
>=20
> On Jul 27, 2014, at 10:45 PM, Gregory Maxwell <gmaxwell@gmail.com> wrot=
e:
>=20
>> On Sun, Jul 27, 2014 at 7:40 PM, Peter Todd <pete@petertodd.org> wrote=
:
>>> Anyway, just goes to show that we need to implement better incoming
>>> connection limiting. gmaxwell has a good scheme with interactive
>>> proof-of-memory - where's your latest writeup?
>>
>> Or its a complete snipe hunt, I'm unable to find any nodes with it
>> connected to them. Does anyone here have any?
>>
>> Last discussion on the measures for anti-global-resource-consumption
>> was at https://bitcointalk.org/index.php?topic=3D310323.0 but it hasn=
't
>> seemed to be a huge issue such that adding more protocol surface area
>> was justified.
>>
>> ----------------------------------------------------------------------=
--------
>> Infragistics Professional
>> Build stunning WinForms apps today!
>> Reboot your WinForms applications with our WinForms controls.=20
>> Build a bridge from your legacy apps to the future.
>> http://pubads.g.doubleclick.net/gampad/clk?id=3D153845071&iu=3D/4140/o=
stg.clktrk
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>=20
>=20
> -----------------------------------------------------------------------=
-------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.=20
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=3D153845071&iu=3D/4140/os=
tg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>=20
|
