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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <brian.erdelyi@gmail.com>) id 1YHh69-0000jG-SE
for bitcoin-development@lists.sourceforge.net;
Sat, 31 Jan 2015 23:05:05 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.172 as permitted sender)
client-ip=209.85.216.172; envelope-from=brian.erdelyi@gmail.com;
helo=mail-qc0-f172.google.com;
Received: from mail-qc0-f172.google.com ([209.85.216.172])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YHh69-0000nh-1p
for bitcoin-development@lists.sourceforge.net;
Sat, 31 Jan 2015 23:05:05 +0000
Received: by mail-qc0-f172.google.com with SMTP id x3so1714089qcv.3
for <bitcoin-development@lists.sourceforge.net>;
Sat, 31 Jan 2015 15:04:59 -0800 (PST)
X-Received: by 10.229.236.129 with SMTP id kk1mr27026501qcb.20.1422745499625;
Sat, 31 Jan 2015 15:04:59 -0800 (PST)
Received: from [192.168.1.58] ([64.147.83.112])
by mx.google.com with ESMTPSA id
c67sm13986095qgd.45.2015.01.31.15.04.58
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 31 Jan 2015 15:04:59 -0800 (PST)
Content-Type: multipart/alternative;
boundary="Apple-Mail=_4DDEA5CE-C5E8-4855-8FF4-4D678FA003D0"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Brian Erdelyi <brian.erdelyi@gmail.com>
In-Reply-To: <CAAt2M18kRgJeNGu9GeKabRpTKPX9rVeoYiKoanz99bmV2jaf4w@mail.gmail.com>
Date: Sat, 31 Jan 2015 19:04:57 -0400
Message-Id: <1348028F-26F8-42CB-9859-C9CB751BF0C9@gmail.com>
References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com>
<CAAt2M18kRgJeNGu9GeKabRpTKPX9rVeoYiKoanz99bmV2jaf4w@mail.gmail.com>
To: Natanael <natanael.l@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(brian.erdelyi[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: 1YHh69-0000nh-1p
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal to address Bitcoin malware
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: Sat, 31 Jan 2015 23:05:06 -0000
--Apple-Mail=_4DDEA5CE-C5E8-4855-8FF4-4D678FA003D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
> See vanitygen. Yes, 8 characters can be brute forced.
>=20
Thank you for this reference. Interesting to see that there is a tool =
to generate a vanity bitcoin address.
I am still researching viruses that are designed to manipulate a bitcoin =
address. I suspect they are primitive in that they use a hardcoded =
rogue bitcoin address as opposed to dynamically generating one.
As a start, this would help protect against malware that uses a static =
rogue bitcoin address. The next thing would be for the malware to =
brute-force the legitimate bitcoin address and generate a rogue bitcoin =
address that would produce the same 8 digit code. Curious to know how =
long this brute force would take? Or perhaps, before converting to 8 =
digits there is some other hashing function that is performed.
Brian Erdelyi=
--Apple-Mail=_4DDEA5CE-C5E8-4855-8FF4-4D678FA003D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><div><blockquote type=3D"cite" class=3D""><p =
dir=3D"ltr" class=3D"">See vanitygen. Yes, 8 characters can be brute =
forced.</p></blockquote><div><br class=3D""></div><div>Thank you for =
this reference. Interesting to see that there is a tool to =
generate a vanity bitcoin address.</div><div><br class=3D""></div><div>I =
am still researching viruses that are designed to manipulate a bitcoin =
address. I suspect they are primitive in that they use a hardcoded =
rogue bitcoin address as opposed to dynamically generating =
one.</div><div><br class=3D""></div><div>As a start, this would help =
protect against malware that uses a static rogue bitcoin address. =
The next thing would be for the malware to brute-force the =
legitimate bitcoin address and generate a rogue bitcoin address that =
would produce the same 8 digit code. Curious to know how long this =
brute force would take? Or perhaps, before converting to 8 digits =
there is some other hashing function that is performed.</div><br =
class=3D""></div><div>Brian Erdelyi</div></div></body></html>=
--Apple-Mail=_4DDEA5CE-C5E8-4855-8FF4-4D678FA003D0--
|
