Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XBbrg-0005NS-Ud for bitcoin-development@lists.sourceforge.net; Mon, 28 Jul 2014 03:44:45 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.182 as permitted sender) client-ip=209.85.223.182; envelope-from=gmaxwell@gmail.com; helo=mail-ie0-f182.google.com; Received: from mail-ie0-f182.google.com ([209.85.223.182]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XBbrd-0008LU-3R for bitcoin-development@lists.sourceforge.net; Mon, 28 Jul 2014 03:44:44 +0000 Received: by mail-ie0-f182.google.com with SMTP id y20so6207128ier.13 for ; Sun, 27 Jul 2014 20:44:35 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.68.15 with SMTP id v15mr7499428ici.79.1406519075726; Sun, 27 Jul 2014 20:44:35 -0700 (PDT) Received: by 10.107.14.67 with HTTP; Sun, 27 Jul 2014 20:44:35 -0700 (PDT) In-Reply-To: <53D5BB5F.2060200@bitwatch.co> References: <20140728024030.GA17724@savin> <53D5BB5F.2060200@bitwatch.co> Date: Sun, 27 Jul 2014 20:44:35 -0700 Message-ID: From: Gregory Maxwell To: "mbde@bitwatch.co" 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: 1XBbrd-0008LU-3R Cc: Bitcoin Development 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2014 03:44:45 -0000 On Sun, Jul 27, 2014 at 7:54 PM, mbde@bitwatch.co wrote: > 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 As I pointed out above, =E2=80=94 it isn't really. Without the exit flag, = I believe no tor node will select it to exit 8333 unless manually configured. (someone following tor more closely than I could correct if I'm wrong here) > 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 dsnrk and mr_burdell on freenode show that the bitnodes crawler showed it accepting _inbound_ bitcoin connections 2-3 weeks ago, though it doesn't now. Fits a pattern of someone running a bitcoin node widely connecting to everyone it can on IPv4 in order to try to deanonymize people, and also running a tor exit (and locally intercepting 8333 there), but I suspect the tor exit part is not actually working=E2=80=94 though they're trying to get it working by accepting huge amounts of relay bandwidth. I'm trying to manually exit through it so I can see if its intercepting the connections, but I seem to not be able. Some other data from the hosts its connecting out to proves that its lying about what software its running (I'm hesitant to just say how I can be sure of that, since doing so just tells someone how to do a more faithful emulation; so that that for whatever its worth).