1  Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
 2  	helo=mx.sourceforge.net)
 3  	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
 4  	(envelope-from <luke@dashjr.org>) id 1XFXNb-00071o-3k
 5  	for bitcoin-development@lists.sourceforge.net;
 6  	Thu, 07 Aug 2014 23:45:55 +0000
 7  X-ACL-Warn: 
 8  Received: from zinan.dashjr.org ([192.3.11.21])
 9  	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
10  	id 1XFXNY-0006Dy-HY for bitcoin-development@lists.sourceforge.net;
11  	Thu, 07 Aug 2014 23:45:55 +0000
12  Received: from ishibashi.localnet (unknown
13  	[IPv6:2001:470:5:265:be5f:f4ff:febf:4f76])
14  	(Authenticated sender: luke-jr)
15  	by zinan.dashjr.org (Postfix) with ESMTPSA id 3757B1080209;
16  	Thu,  7 Aug 2014 23:36:47 +0000 (UTC)
17  From: Luke Dashjr <luke@dashjr.org>
18  To: bitcoin-development@lists.sourceforge.net
19  Date: Thu, 7 Aug 2014 23:45:44 +0000
20  User-Agent: KMail/1.13.7 (Linux/3.15.5-gentoo; KDE/4.12.5; x86_64; ; )
21  References: <CAPS+U9-ze_-gcYh1WNVJ5h8AZ8owoQX=8OUgNcKnaxgvjxZATA@mail.gmail.com>
22  In-Reply-To: <CAPS+U9-ze_-gcYh1WNVJ5h8AZ8owoQX=8OUgNcKnaxgvjxZATA@mail.gmail.com>
23  X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
24  X-PGP-Key-ID: BD02942421F4889F
25  X-PGP-Keyserver: hkp://pgp.mit.edu
26  MIME-Version: 1.0
27  Content-Type: Text/Plain;
28    charset="iso-8859-15"
29  Content-Transfer-Encoding: 7bit
30  Message-Id: <201408072345.45363.luke@dashjr.org>
31  X-Spam-Score: -0.7 (/)
32  X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
33  	See http://spamassassin.org/tag/ for more details.
34  	-0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
35  	domain
36  X-Headers-End: 1XFXNY-0006Dy-HY
37  Subject: Re: [Bitcoin-development] Miners MiTM
38  X-BeenThere: bitcoin-development@lists.sourceforge.net
39  X-Mailman-Version: 2.1.9
40  Precedence: list
41  List-Id: <bitcoin-development.lists.sourceforge.net>
42  List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
43  	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
44  List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
45  List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
46  List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
47  List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
48  	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
49  X-List-Received-Date: Thu, 07 Aug 2014 23:45:55 -0000
50  
51  On Thursday, August 07, 2014 11:02:21 PM Pedro Worcel wrote:
52  > Hi there,
53  > 
54  > I was wondering if you guys have come across this article:
55  > 
56  > http://www.wired.com/2014/08/isp-bitcoin-theft/
57  > 
58  > The TL;DR is that somebody is abusing the BGP protocol to be in a position
59  > where they can intercept the miner traffic. The concerning point is that
60  > they seem to be having some degree of success in their endeavour and
61  > earning profits from it.
62  > 
63  > I do not understand the impact of this (I don't know much about BGP, the
64  > mining protocol nor anything else, really), but I thought it might be worth
65  > putting it up here.
66  
67  This is old news; both BFGMiner and Eloipool were hardened against it a long 
68  time ago (although no Bitcoin pools have deployed it so far). I'm not aware of 
69  any actual case of it being used against Bitcoin, though - the target has 
70  always been scamcoins.
71  
72