summaryrefslogtreecommitdiff
path: root/7a/b59598d8ba6656081afbb3f84704617192eb9e
blob: 6d270b8b2857c7cd57652d2e4678857cb1d99abc (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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <startithub@gmail.com>) id 1Vdl2p-0003lH-7U
	for bitcoin-development@lists.sourceforge.net;
	Tue, 05 Nov 2013 18:08:03 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.182 as permitted sender)
	client-ip=209.85.212.182; envelope-from=startithub@gmail.com;
	helo=mail-wi0-f182.google.com; 
Received: from mail-wi0-f182.google.com ([209.85.212.182])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Vdl2o-000890-1i
	for bitcoin-development@lists.sourceforge.net;
	Tue, 05 Nov 2013 18:08:03 +0000
Received: by mail-wi0-f182.google.com with SMTP id ez12so2502361wid.15
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 05 Nov 2013 10:07:55 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.5.7 with SMTP id o7mr18708261wjo.17.1383674875866; Tue,
	05 Nov 2013 10:07:55 -0800 (PST)
Received: by 10.216.208.67 with HTTP; Tue, 5 Nov 2013 10:07:55 -0800 (PST)
In-Reply-To: <CANEZrP0itd3xW7yyg9FBJVuJNttcmMhnqWGOaWxjz37ATrR8qA@mail.gmail.com>
References: <CABT1wWkOukEzxK5fLbnA4ZgJGN1hb_DMteCJOfA13FE_QZCi=Q@mail.gmail.com>
	<20131105170541.GA13660@petertodd.org>
	<20131105171445.GA13710@petertodd.org>
	<CABT1wW=XgDfxfxMxyjcNhtNTzXkGLtgSLz3JJcUAq9ywgpymyg@mail.gmail.com>
	<CANEZrP0itd3xW7yyg9FBJVuJNttcmMhnqWGOaWxjz37ATrR8qA@mail.gmail.com>
Date: Tue, 5 Nov 2013 19:07:55 +0100
Message-ID: <CADre0dm0PGARSXXdwoa1ZOnpbEw_bx0aKP17q4PSFLTayyoRJw@mail.gmail.com>
From: Alessandro Parisi <startithub@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=047d7b5d8d4575f8fb04ea71e9da
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
	See
	http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
	for more information. [URIs: doubleclick.net]
	-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
	(startithub[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1Vdl2o-000890-1i
Cc: Ittay <ittay.eyal@cornell.edu>,
	Gavin Andresen <gavin@bitcoinfoundation.org>,
	=?ISO-8859-1?Q?Emin_G=FCn_Sirer?= <egs@systems.cs.cornell.edu>,
	Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP proposal - patch to raise selfish
 mining threshold.
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: Tue, 05 Nov 2013 18:08:03 -0000

--047d7b5d8d4575f8fb04ea71e9da
Content-Type: text/plain; charset=ISO-8859-1

I agree with Ittay: when bugs are found, they must be fixed ASAP,
expecially when they affect a sensitive sw such as Bitcon; in IT security,
every flaw that is exploitable in abstract, is going to be exploited in
real, sooner or later, also taking into account the increasing parallel
computing power; beware of false sense of security

WebSite: http://www.startithub.com
Per rimanere aggiornato in merito a Startup, Innovazione e Normativa di
settore, sottoscrivi la nostra newsletter:
http://www.startithub.com/blog/sottoscrivi-newsletter/


2013/11/5 Mike Hearn <mike@plan99.net>

> On Tue, Nov 5, 2013 at 6:43 PM, Ittay <ittay.eyal@cornell.edu> wrote:
>
>> The attack can be easily hidden. And be sure that before today, today,
>> and after today, very smart people are at their computer planning attacks
>> on Bitcoin. Exploits must be published and fixed FAST.
>>
>
> I think it would be helpful if you actually implemented and pulled off
> this attack, by becoming the dominant miner capable of reversing spends at
> will. Then we'd know how quickly it can be done.
>
>
>
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models.
> Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and
> register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

--047d7b5d8d4575f8fb04ea71e9da
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree with Ittay: when bugs are found, they must be fixe=
d ASAP, expecially when they affect a sensitive sw such as Bitcon; in IT se=
curity, every flaw that is exploitable in abstract, is going to be exploite=
d in real, sooner or later, also taking into account the increasing paralle=
l computing power; beware of false sense of security</div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr">WebSite:=
 <a href=3D"http://www.startithub.com" target=3D"_blank">http://www.startit=
hub.com</a><br>Per rimanere aggiornato in merito a Startup, Innovazione e N=
ormativa di settore, sottoscrivi la nostra newsletter:=A0<a href=3D"http://=
www.startithub.com/blog/sottoscrivi-newsletter/" target=3D"_blank">http://w=
ww.startithub.com/blog/sottoscrivi-newsletter/</a></div>
</div>
<br><br><div class=3D"gmail_quote">2013/11/5 Mike Hearn <span dir=3D"ltr">&=
lt;<a href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>=
&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"im">On Tue, Nov 5, 2013 at 6:43 PM, Ittay <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:ittay.eyal@cornell.edu" target=3D"_bl=
ank">ittay.eyal@cornell.edu</a>&gt;</span> wrote:<br></div><div class=3D"gm=
ail_extra">
<div class=3D"gmail_quote"><div class=3D"im">
<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"><div><span style=3D"color:r=
gb(34,34,34)">The attack can be easily hidden. And be sure that before toda=
y, today,=A0</span><br>

</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>and after =
today, very smart people are at their computer planning attacks=A0</div>

<div>on Bitcoin. Exploits must be published and fixed FAST.=A0</div></div><=
/div></div></blockquote><div><br></div></div><div>I think it would be helpf=
ul if you actually implemented and pulled off this attack, by becoming the =
dominant miner capable of reversing spends at will. Then we&#39;d know how =
quickly it can be done.</div>

<div><br></div><div><br></div></div><br></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
November Webinars for C, C++, Fortran Developers<br>
Accelerate application performance with scalable programming models. Explor=
e<br>
techniques for threading, error checking, porting, and tuning. Get the most=
<br>
from the latest Intel processors and coprocessors. See abstracts and regist=
er<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60136231&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D60136231&amp;iu=3D/4140/ostg.clktrk</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>

--047d7b5d8d4575f8fb04ea71e9da--