summaryrefslogtreecommitdiff
path: root/d9/214e8a5e3bff1c870895d38fcaa5495b854fc3
blob: be09807113dc8cb5c59be15e49e94cf0f612467a (plain)
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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pedro@worcel.com>) id 1XFYew-0005Hs-HY
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Aug 2014 01:07:54 +0000
X-ACL-Warn: 
Received: from mail-lb0-f175.google.com ([209.85.217.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XFYeu-0003b7-R6
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Aug 2014 01:07:54 +0000
Received: by mail-lb0-f175.google.com with SMTP id 10so3249821lbg.6
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 07 Aug 2014 18:07:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type;
	bh=VIpoUebX6pTObFVokhzJJyFm93YcqExq8o5XtPD+wNc=;
	b=AiD/8+7zDd4av0G46AkhVkKfiGikNXL0zTBAm1xw1fAefUipSZik62233atuVSd7uE
	32xslp6/VFZ7lsFIzMNOBxad+EKUEI+UqnThwa1Ky99D4SD/UNeM76pyiN8s036lb5yB
	3Lg79PeDKEJ1U9lj4RDKRH4f+s9Fu01s8JPiNVi/8y2y4EPU+xUCd0vzHEfp/3x6oIZW
	BlIaHjHu8n1F5KnILkIe0sq2X9WPtgHIxinZesdKjZMD6Kd7AWABMXjleGEVPYiBC5OL
	54/PeLs7le4Gf8+AsDpd/AUEQI1c4RGT0nJF7sHeJlSLrzU1czljSF+uxpJ86qrAsU+L
	3L2w==
X-Gm-Message-State: ALoCoQm4If8qTDO7/UsXxvneD6Jug8Qi2uyQC367oiamyPF2Z6lpquYZcdNGGIZ68ysG/wI8Tm91
X-Received: by 10.153.11.162 with SMTP id ej2mr19340945lad.15.1407460065689;
	Thu, 07 Aug 2014 18:07:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.136.131 with HTTP; Thu, 7 Aug 2014 18:07:04 -0700 (PDT)
In-Reply-To: <CAH99vakZLWe_auKb0iuKY0EJn2wWT13bThY-y5Y5O0u+AWRj3g@mail.gmail.com>
References: <CAPS+U9-ze_-gcYh1WNVJ5h8AZ8owoQX=8OUgNcKnaxgvjxZATA@mail.gmail.com>
	<201408072345.45363.luke@dashjr.org>
	<CAJna-HjzMO68KSXYG++X-8vzQCLurkrAAhfrVo9-AbaoYdqZhw@mail.gmail.com>
	<CAH99vakZLWe_auKb0iuKY0EJn2wWT13bThY-y5Y5O0u+AWRj3g@mail.gmail.com>
From: Pedro Worcel <pedro@worcel.com>
Date: Fri, 8 Aug 2014 13:07:04 +1200
Message-ID: <CAPS+U99pnqrGiYb-1MMf_GjR2eCiwaX3MvDHX3kGjepEf0=4nQ@mail.gmail.com>
To: Christopher Franko <chrisjfranko@gmail.com>
Content-Type: multipart/alternative; boundary=001a11346d604057e9050013d549
X-Spam-Score: 2.7 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.7 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
	[URIs: dashjr.org]
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1XFYeu-0003b7-R6
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Miners MiTM
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: Fri, 08 Aug 2014 01:07:54 -0000

--001a11346d604057e9050013d549
Content-Type: text/plain; charset=UTF-8

> the only protection is SSL + certificate validation on client side.
However certificate revocation and updates in miners are pain in the ass,
that's why majority of pools (mine including) don't want to play with
that...

Another solution which would have less overhead would be to implement
something akin to what openssh does. The OpenSSH client stores a
certificate fingerprint, which is then verified automatically upon further
connections to the server.

The initial connection needs to be verified manually by the operator,
though.

> Certificate validation isn't needed unless the attacker can do a direct
MITM
at connection time, which is a lot harder to maintain than injecting a
client.reconnect. This, combined with your concern about up to date
certs/revokes/etc, is why BFGMiner defaults to TLS without cert checking for
stratum.

Seems to me that it would correctly mitigate the attack mentioned in the
wired article. I am surprised that miners are not worried about losing
their profits, I would personally be quite annoyed.



2014-08-08 12:37 GMT+12:00 Christopher Franko <chrisjfranko@gmail.com>:

> What exactly makes bitcoin less of a target than a "scamcoin" which I
> suspect means anything that != bitcoin?
>
>
> On 7 August 2014 20:29, slush <slush@centrum.cz> wrote:
>
>> AFAIK the only protection is SSL + certificate validation on client side.
>> However certificate revocation and updates in miners are pain in the ass,
>> that's why majority of pools (mine including) don't want to play with
>> that...
>>
>> slush
>>
>>
>> On Fri, Aug 8, 2014 at 1:45 AM, Luke Dashjr <luke@dashjr.org> wrote:
>>
>>> On Thursday, August 07, 2014 11:02:21 PM Pedro Worcel wrote:
>>> > Hi there,
>>> >
>>> > I was wondering if you guys have come across this article:
>>> >
>>> > http://www.wired.com/2014/08/isp-bitcoin-theft/
>>> >
>>> > The TL;DR is that somebody is abusing the BGP protocol to be in a
>>> position
>>> > where they can intercept the miner traffic. The concerning point is
>>> that
>>> > they seem to be having some degree of success in their endeavour and
>>> > earning profits from it.
>>> >
>>> > I do not understand the impact of this (I don't know much about BGP,
>>> the
>>> > mining protocol nor anything else, really), but I thought it might be
>>> worth
>>> > putting it up here.
>>>
>>> This is old news; both BFGMiner and Eloipool were hardened against it a
>>> long
>>> time ago (although no Bitcoin pools have deployed it so far). I'm not
>>> aware of
>>> any actual case of it being used against Bitcoin, though - the target has
>>> always been scamcoins.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>>
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">&gt;  the only protection is SSL + certificate validation on cl=
ient side.=20
However certificate revocation and updates in miners are pain in the=20
ass, that&#39;s why majority of pools (mine including) don&#39;t want to pl=
ay=20
with that...<br><br></div><div class=3D"gmail_default" style=3D"font-family=
:verdana,sans-serif">Another solution which would have less overhead would =
be to implement something akin to what openssh does. The OpenSSH client sto=
res a certificate fingerprint, which is then verified automatically upon fu=
rther connections to the server. <br>

<br>The initial connection needs to be verified manually by the operator, t=
hough.<br><br>&gt; Certificate validation isn&#39;t needed unless the attac=
ker can do a direct MITM<br>
at connection time, which is a lot harder to maintain than injecting a<br>
client.reconnect. This, combined with your concern about up to date<br>
certs/revokes/etc, is why BFGMiner defaults to TLS without cert checking fo=
r<br>
stratum.<br><br></div><div class=3D"gmail_default" style=3D"font-family:ver=
dana,sans-serif">Seems to me that it would correctly mitigate the attack me=
ntioned in the wired article. I am surprised that miners are not worried ab=
out losing their profits, I would personally be quite annoyed.<br>

</div><div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"=
><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">2014-08-08 12:37 GMT+12:00 Christopher Franko <span dir=3D"ltr">&lt;<a =
href=3D"mailto:chrisjfranko@gmail.com" target=3D"_blank">chrisjfranko@gmail=
.com</a>&gt;</span>:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">What exactly makes bitcoin =
less of a target than a &quot;scamcoin&quot; which I suspect means anything=
 that !=3D bitcoin?</div>

<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote"><div><div cla=
ss=3D"h5">On 7 August 2014 20:29, slush <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:slush@centrum.cz" target=3D"_blank">slush@centrum.cz</a>&gt;</span> wr=
ote:<br>


</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5"><div dir=
=3D"ltr">AFAIK the only protection is SSL + certificate validation on clien=
t side. However certificate revocation and updates in miners are pain in th=
e ass, that&#39;s why majority of pools (mine including) don&#39;t want to =
play with that...<span><font color=3D"#888888"><div>




<br></div><div>slush</div></font></span></div><div><div><div class=3D"gmail=
_extra"><br><br><div class=3D"gmail_quote">On Fri, Aug 8, 2014 at 1:45 AM, =
Luke Dashjr <span dir=3D"ltr">&lt;<a href=3D"mailto:luke@dashjr.org" target=
=3D"_blank">luke@dashjr.org</a>&gt;</span> wrote:<br>




<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div>On Thursday, August 07, 2014 11:02=
:21 PM Pedro Worcel wrote:<br>
&gt; Hi there,<br>
&gt;<br>
&gt; I was wondering if you guys have come across this article:<br>
&gt;<br>
&gt; <a href=3D"http://www.wired.com/2014/08/isp-bitcoin-theft/" target=3D"=
_blank">http://www.wired.com/2014/08/isp-bitcoin-theft/</a><br>
&gt;<br>
&gt; The TL;DR is that somebody is abusing the BGP protocol to be in a posi=
tion<br>
&gt; where they can intercept the miner traffic. The concerning point is th=
at<br>
&gt; they seem to be having some degree of success in their endeavour and<b=
r>
&gt; earning profits from it.<br>
&gt;<br>
&gt; I do not understand the impact of this (I don&#39;t know much about BG=
P, the<br>
&gt; mining protocol nor anything else, really), but I thought it might be =
worth<br>
&gt; putting it up here.<br>
<br>
</div></div>This is old news; both BFGMiner and Eloipool were hardened agai=
nst it a long<br>
time ago (although no Bitcoin pools have deployed it so far). I&#39;m not a=
ware of<br>
any actual case of it being used against Bitcoin, though - the target has<b=
r>
always been scamcoins.<br>
<br>
---------------------------------------------------------------------------=
---<br>
Infragistics Professional<br>
Build stunning WinForms apps today!<br>
Reboot your WinForms applications with our WinForms controls.<br>
Build a bridge from your legacy apps to the future.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D153845071&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D153845071&amp;iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
</div></div><br></div></div>-----------------------------------------------=
-------------------------------<br>
Want fast and easy access to all the code in your enterprise? Index and<br>
search up to 200,000 lines of code with a free copy of Black Duck<br>
Code Sight - the same software that powers the world&#39;s largest code<br>
search on Ohloh, the Black Duck Open Hub! Try it now.<br>
<a href=3D"http://p.sf.net/sfu/bds" target=3D"_blank">http://p.sf.net/sfu/b=
ds</a><div class=3D""><br>_______________________________________________<b=
r>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></div></blockquote></div><br></div>
<br>-----------------------------------------------------------------------=
-------<br>
Want fast and easy access to all the code in your enterprise? Index and<br>
search up to 200,000 lines of code with a free copy of Black Duck<br>
Code Sight - the same software that powers the world&#39;s largest code<br>
search on Ohloh, the Black Duck Open Hub! Try it now.<br>
<a href=3D"http://p.sf.net/sfu/bds" target=3D"_blank">http://p.sf.net/sfu/b=
ds</a><br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>

--001a11346d604057e9050013d549--