From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XBnYU-0006Ij-TG for bitcoin-development@lists.sourceforge.net; Mon, 28 Jul 2014 16:13:43 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of sky-ip.org designates 162.222.225.28 as permitted sender) client-ip=162.222.225.28; envelope-from=s7r@sky-ip.org; helo=outbound.mailhostbox.com; Received: from outbound.mailhostbox.com ([162.222.225.28]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XBnYN-0002Zn-Ed for bitcoin-development@lists.sourceforge.net; Mon, 28 Jul 2014 16:13:42 +0000 Received: from [0.0.0.0] (manning1.torservers.net [96.44.189.100]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: s7r@sky-ip.org) by outbound.mailhostbox.com (Postfix) with ESMTPSA id 540A18690E2 for ; Mon, 28 Jul 2014 16:13:30 +0000 (GMT) Message-ID: <53D6769F.4050909@sky-ip.org> Date: Mon, 28 Jul 2014 19:13:19 +0300 From: s7r 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: <20140728024030.GA17724@savin> <53D5BB5F.2060200@bitwatch.co> <06e8ee730ac511617e6c3c4a4bbae4bb@webmail.mckay.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 X-CTCH-RefID: str=0001.0A020205.53D676AA.003B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CTCH-SenderID: s7r@sky-ip.org X-CTCH-SenderID-TotalMessages: 1 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalRecipients: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-BlueWhiteFlag: 0 X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.4 (-) 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 SPF_PASS SPF: sender matches SPF record 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Headers-End: 1XBnYN-0002Zn-Ed 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 Reply-To: s7r@sky-ip.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2014 16:13:43 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/28/2014 5:08 PM, Gregory Maxwell wrote: > On Mon, Jul 28, 2014 at 5:31 AM, Robert McKay > wrote: >> I don't think Sybil attack is the right term for this.. there is >> only one IP address.. one "identity". >=20 > 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. >=20 >> 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. >=20 > It isn't relaying transactions or blocks as far as anyone with a=20 > connection to it can tell. >=20 > and sure, probably not much to worry about=E2=80=94 people have been > running spy nodes for a long time, at least that much is not new. >=20 > -----------------------------------------------------------------------= ------- > >=20 Infragistics Professional > Build stunning WinForms apps today! Reboot your WinForms > applications with our WinForms controls. Build a bridge from your > legacy apps to the future.=20 > http://pubads.g.doubleclick.net/gampad/clk?id=3D153845071&iu=3D/4140/os= tg.clktrk > >=20 _______________________________________________ > Bitcoin-development mailing list=20 > Bitcoin-development@lists.sourceforge.net=20 > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >=20 gmaxwell - I wanted to ask you a non-expert question. Let's say I use my bitcoin-qt on my laptop with Tor, and send some BTC or receive some, what can my Tor exit node see / do / harm? He can alter the content, by modifying and transmitting invalid transactions to the network but this will have no effect on me, e.g. can't steal coins or send them on my behalf or intercept my payments, right? It's not clear for me what data would such a node see? Why would you spend money to setup a spy node for this what relevant data can it give you? - --=20 s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJT1nafAAoJEIN/pSyBJlsR8GYIAL9LkZvPbKjJ6cUxlC4yRKay YUumAafCKYMvp8Ywvz3CWpC4Gncn+v29hhJu/Nc0wSItAnf4suwrAFtBAwAYlUx8 a1J6S1hgGXCBWDZcGHDc1Xt2lLzvijDcilSZfQWXnAdoEaZyln/7Kn+o/fFcXG6h DUkSCSe9M3tN/tZBcZrhBXTENhoJ6MZldcgey6Ky0qLkmI3GCd0MhM+D15xl1LkT 6IS2r2y0RUOxkbg/SuSzFS8vnNTTWmZpbECo3Qq98W41X0M3ZtjOlaByPZXFX5K9 +HUeiptV9zukSdIRcuGH1PUQvU9nk+G1rFKr0dXu4oPvAUxqyw9uCTFgHXczuQY=3D =3Dgw3W -----END PGP SIGNATURE-----