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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <martin.habovstiak@gmail.com>) id 1YHuch-0002li-Cy
for bitcoin-development@lists.sourceforge.net;
Sun, 01 Feb 2015 13:31:35 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.51 as permitted sender)
client-ip=209.85.192.51;
envelope-from=martin.habovstiak@gmail.com;
helo=mail-qg0-f51.google.com;
Received: from mail-qg0-f51.google.com ([209.85.192.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YHucg-0004T5-Cv
for bitcoin-development@lists.sourceforge.net;
Sun, 01 Feb 2015 13:31:35 +0000
Received: by mail-qg0-f51.google.com with SMTP id z107so44130747qgd.10
for <bitcoin-development@lists.sourceforge.net>;
Sun, 01 Feb 2015 05:31:29 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.224.55.71 with SMTP id t7mr31777819qag.53.1422797488952;
Sun, 01 Feb 2015 05:31:28 -0800 (PST)
Received: by 10.140.19.18 with HTTP; Sun, 1 Feb 2015 05:31:28 -0800 (PST)
In-Reply-To: <88211D58-DE9D-4B4A-B3A5-2EEFDFC5E02B@gmail.com>
References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com>
<CAAt2M18kRgJeNGu9GeKabRpTKPX9rVeoYiKoanz99bmV2jaf4w@mail.gmail.com>
<1348028F-26F8-42CB-9859-C9CB751BF0C9@gmail.com>
<CAAt2M1_3BdKQTVxsN7Hc-W=q0_NWyhBg1UAuSwxRQ8BePDa-8g@mail.gmail.com>
<CAAt2M1-b7ByF0yVSmwD_nj3uUSo5GFOmH860n1k6oKX_sqvEkw@mail.gmail.com>
<88211D58-DE9D-4B4A-B3A5-2EEFDFC5E02B@gmail.com>
Date: Sun, 1 Feb 2015 15:31:28 +0200
Message-ID: <CALkkCJbiv3o-oGoKY6sQkiLSeaCUfKVKHj1wqZUjfprmf9M5BA@mail.gmail.com>
From: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= <martin.habovstiak@gmail.com>
To: Brian Erdelyi <brian.erdelyi@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
(martin.habovstiak[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1YHucg-0004T5-Cv
Cc: Bitcoin Dev <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: Sun, 01 Feb 2015 13:31:35 -0000
BIP70 is quite safe agains MitB. If user copies URL belonging to other
merchant, he would see the fact after entering it into his wallet
application. The only problem is, attacker can buy from the same
merchant with user's money. (sending him different URL) This can be
mitigated by merchant setting "memo" to the description of the basket
and some user info (e.g. address to which goods are sent).
But if whole computer is compromised, you're already screwed. Trezor
should help, but I'm not sure if it supports BIP70.
2015-02-01 14:49 GMT+02:00 Brian Erdelyi <brian.erdelyi@gmail.com>:
>
> In online banking, the banks generate account numbers. An attacker canno=
t
> generate their own account number and the likelihood of an attacker havin=
g
> the same account number that I am trying to transfer funds to is low and
> this is why OCRA is effective with online banking.
>
> With Bitcoin, the Bitcoin address is comparable to the recipient=E2=80=99=
s bank
> account number. I now see how an an attacker can brute force the bitcoi=
n
> address with vanitygen. Is there any way to generate an 8 digit number f=
rom
> the bitcoin address that can be used to verify transactions in such a way
> (possibly with hashing?) that brute forcing a bitcoin address would take
> longer than a reasonable period of time (say 60 seconds) so a system coul=
d
> time out if a transaction was not completed in that time?
>
> I=E2=80=99ve also looked into BIP70 (Payment Protocol) that claims protec=
tion
> against man-in-the-middle/man-in-the-browser (MitB) based attacks. A com=
mon
> way to protect against this is with out-of-band transaction verification
> (http://en.wikipedia.org/wiki/Man-in-the-browser#Out-of-band_transaction_=
verification).
> I see how BIP 70 verifies the payment request, however, is there any way =
to
> verify that the transaction signed by the wallet matches the request befo=
re
> it is sent to the blockchain (and how can this support out of band
> verification)? Perhaps this is something that can only be supported when
> sending money with web based wallets.
>
> Brian Erdelyi
>
> -------------------------------------------------------------------------=
-----
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is y=
our
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take =
a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
|
