Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.218.52 as permitted sender)
	client-ip=209.85.218.52; envelope-from=mh.in.england@gmail.com;
	helo=mail-oi0-f52.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CAAS2fgRVUbEM=7KQt-Haue=+sgAFu=HrfDdS0hhatNawci_eZQ@mail.gmail.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>
Date: Mon, 28 Jul 2014 12:16:16 +0200
Message-ID: <CANEZrP10sFWiBv=yi0YaPszzxrygfRhwTP8fdqKapSL1yucfow@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b41cc74a5e36a04ff3e3695
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Abnormally Large Tor node accepting only
 Bitcoin traffic
Precedence: list

--047d7b41cc74a5e36a04ff3e3695
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> 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)
>

The "exit" flag doesn't mean what you would expect it to mean. The reason
such a node won't get much traffic is that Tor speculatively builds
circuits at startup on the assumption they'll be used for web browsing.
Thus if you don't exit web traffic you won't get much in the way of traffic
at least not until bitcoinj based wallets start shipping Tor mode.

There's a perfectly reasonable explanation for why someone would run such a
node. In fact I run a Tor exit that only allows port 8333 too: it's a way
to contribute exit bandwidth without much risk of getting raided by the
cops.

Occam's razor and all ....

--047d7b41cc74a5e36a04ff3e3695
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">As I pointed out above, =E2=
=80=94 it isn&#39;t really. =C2=A0Without the exit flag, I<br>
</div>
believe no tor node will select it to exit 8333 unless manually<br>
configured. (someone following tor more closely than I could correct<br>
if I&#39;m wrong here)<br></blockquote><div><br></div><div>The &quot;exit&q=
uot; flag doesn&#39;t mean what you would expect it to mean. The reason suc=
h a node won&#39;t get much traffic is that Tor speculatively builds circui=
ts at startup on the assumption they&#39;ll be used for web browsing. Thus =
if you don&#39;t exit web traffic you won&#39;t get much in the way of traf=
fic at least not until bitcoinj based wallets start shipping Tor mode.</div=
>
<div><br></div><div>There&#39;s a perfectly reasonable explanation for why =
someone would run such a node. In fact I run a Tor exit that only allows po=
rt 8333 too: it&#39;s a way to contribute exit bandwidth without much risk =
of getting raided by the cops.</div>
</div><br></div><div class=3D"gmail_extra">Occam&#39;s razor and all ....</=
div></div>

--047d7b41cc74a5e36a04ff3e3695--