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
|
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 <tamas@bitsofproof.com>) id 1YEgn6-0002su-IG
for bitcoin-development@lists.sourceforge.net;
Fri, 23 Jan 2015 16:09:00 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1YEgn4-0008Uu-Oa
for bitcoin-development@lists.sourceforge.net;
Fri, 23 Jan 2015 16:09:00 +0000
Received: from [37.143.74.116] (helo=[192.168.0.100]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1YEgmy-0003nh-1k; Fri, 23 Jan 2015 17:08:52 +0100
Content-Type: multipart/signed;
boundary="Apple-Mail=_1B1F76C1-12D0-4FC7-8F9C-731372F5789F";
protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <CAJna-HiXxt5E=FBiDuWMCKrK4C0dcvhHEjTAoK3LGQLafJOqtQ@mail.gmail.com>
Date: Fri, 23 Jan 2015 17:08:50 +0100
Message-Id: <954BF4E3-8DF2-4927-9E25-C5D66127FFA5@bitsofproof.com>
References: <CAJna-HjwMRff_+7BvcR2YME9f2yUQPvfKOGZ1qq9d0nOGqORkg@mail.gmail.com>
<78662993-6C67-4480-8062-55CC9FA63908@bitsofproof.com>
<54C26BFE.1080103@gmail.com>
<CAJna-HiXxt5E=FBiDuWMCKrK4C0dcvhHEjTAoK3LGQLafJOqtQ@mail.gmail.com>
To: slush <slush@centrum.cz>
X-Mailer: Apple Mail (2.1878.6)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1422029338;
34f509fa;
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [80.237.132.66 listed in list.dnswl.org]
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1YEgn4-0008Uu-Oa
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] SIGHASH_WITHINPUTVALUE
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, 23 Jan 2015 16:09:00 -0000
--Apple-Mail=_1B1F76C1-12D0-4FC7-8F9C-731372F5789F
Content-Type: multipart/alternative;
boundary="Apple-Mail=_1AD4CE2E-A24F-4777-A6D9-D23C8BF5E694"
--Apple-Mail=_1AD4CE2E-A24F-4777-A6D9-D23C8BF5E694
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=iso-8859-1
You mean an isolated signing device without memory right?=20
An isolated node would still know the transactions substantiating its =
coins, why would it sign them away to fees ?
Tamas Blummer
On Jan 23, 2015, at 4:47 PM, slush <slush@centrum.cz> wrote:
> Correct, plus the most likely scenario in such attack is that the =
malware even don't push such tx with excessive fees to the network, but =
send it directly to attacker's pool/miner.
>=20
> M.
>=20
> On Fri, Jan 23, 2015 at 4:42 PM, Alan Reiner <etotheipi@gmail.com> =
wrote:
> Unfortunately, one major attack vector is someone isolating your node, =
getting you to sign away your whole wallet to fee, and then selling it =
to a mining pool to mine it before you can figure why your transactions =
aren't making it to the network. In such an attack, the relay rules =
aren't relevant, and if the attacker can DoS you for 24 hours, it =
doesn't take a ton of mining power to make the attack extremely likely =
to succeed.
>=20
>=20
>=20
>=20
> On 01/23/2015 10:31 AM, Tamas Blummer wrote:
>> Not a fix, but would reduce the financial risk, if nodes were not =
relaying excessive fee transactions.
>>=20
>> Tamas Blummer
>>=20
>>=20
>=20
>=20
--Apple-Mail=_1AD4CE2E-A24F-4777-A6D9-D23C8BF5E694
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=iso-8859-1
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">You =
mean an isolated signing device without memory =
right? <div><br></div><div><div>An isolated node would still know =
the transactions substantiating its coins, why would it sign them away =
to fees ?</div><div><br><div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Tamas =
Blummer</div><div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><br></div></div><div><div>On Jan 23, 2015, at 4:47 PM, slush =
<<a href=3D"mailto:slush@centrum.cz">slush@centrum.cz</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">Correct, plus the most likely scenario in =
such attack is that the malware even don't push such tx with excessive =
fees to the network, but send it directly to attacker's =
pool/miner.<div><br></div><div>M.</div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Jan 23, =
2015 at 4:42 PM, Alan Reiner <span dir=3D"ltr"><<a =
href=3D"mailto:etotheipi@gmail.com" =
target=3D"_blank">etotheipi@gmail.com</a>></span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px =
0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto;">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
Unfortunately, one major attack vector is someone isolating your
node, getting you to sign away your whole wallet to fee, and then
selling it to a mining pool to mine it before you can figure why
your transactions aren't making it to the network. In such an
attack, the relay rules aren't relevant, and if the attacker can DoS
you for 24 hours, it doesn't take a ton of mining power to make the
attack extremely likely to succeed.<span class=3D""><br>
<br>
<br>
<br>
<br>
<div>On 01/23/2015 10:31 AM, Tamas Blummer
wrote:<br>
</div>
<blockquote type=3D"cite">
=20
<div>Not a fix, but would reduce the financial risk, if nodes were
not relaying excessive fee transactions.</div>
<div><br>
</div>
<div>
<div style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px;">Tamas
Blummer</div>
<div style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px;"><br>
</div>
</div>
<br>
</blockquote>
<br>
</span></div>
=
<br></blockquote></div></div></blockquote></div><br></div></div></body></h=
tml>=
--Apple-Mail=_1AD4CE2E-A24F-4777-A6D9-D23C8BF5E694--
--Apple-Mail=_1B1F76C1-12D0-4FC7-8F9C-731372F5789F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQEcBAEBCgAGBQJUwnISAAoJEPZykcUXcTkca98IAKH1uuS2IclmtiPtwurxcCmD
GNdK2KjaLgC0k4ZDPlvIZxEZxgmmVmOp7WgGoSF0dGh3EnhQimayn+IvWd3bKFRA
Qpl2QRPhcPYFRaTsjavY5BJ5ft90LIdHK26Q66GXgfzINCtZCWWrVrNEDW5A4rKQ
kMHl4VSHHX//DOG8/ZrD42wZaagAl03S4xQ94J8vj29jjJxLuGq0AcwYHpvDHFFe
vUUGORHEjOLrm/K2EQVb5lOaV14jHdLJK7wzEt4pdZOxoLSlyrzD6HzDbtcMwArX
GzTdXUGuSu0NQ6XYxr6jHVmShUzp8BldqrKcTiH3wZlQL8lAB6FD6+G6KEPCtfY=
=hsah
-----END PGP SIGNATURE-----
--Apple-Mail=_1B1F76C1-12D0-4FC7-8F9C-731372F5789F--
|
