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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YILI1-0004OM-Ob
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Feb 2015 18:00:01 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.177 as permitted sender)
client-ip=209.85.212.177; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f177.google.com;
Received: from mail-wi0-f177.google.com ([209.85.212.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YILI0-0000Sk-Io
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Feb 2015 18:00:01 +0000
Received: by mail-wi0-f177.google.com with SMTP id r20so16820248wiv.4
for <bitcoin-development@lists.sourceforge.net>;
Mon, 02 Feb 2015 09:59:54 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.207.10 with SMTP id ls10mr26857523wic.7.1422899994475;
Mon, 02 Feb 2015 09:59:54 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Mon, 2 Feb 2015 09:59:54 -0800 (PST)
In-Reply-To: <CALkkCJbk0czFj5mdMB6_0+Umw5V-fo-4tdBHgvg92zhyRZWiYQ@mail.gmail.com>
References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com>
<54CE3816.6020505@bitwatch.co>
<68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com>
<CALkkCJbk0czFj5mdMB6_0+Umw5V-fo-4tdBHgvg92zhyRZWiYQ@mail.gmail.com>
Date: Mon, 2 Feb 2015 18:59:54 +0100
X-Google-Sender-Auth: HXsdESQSizQERakkw9E9QpZ_O3Y
Message-ID: <CANEZrP0QjPm+TTgV9Fh84vt2zLaGp0R2Wt2ZL2ZXYhxzOFPHVA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= <martin.habovstiak@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3f51ab8c6cb050e1eb87c
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1YILI0-0000Sk-Io
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: Mon, 02 Feb 2015 18:00:01 -0000
--001a11c3f51ab8c6cb050e1eb87c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
We're way ahead of you guys ;)
On Mon, Feb 2, 2015 at 6:54 PM, Martin Habov=C5=A1tiak <
martin.habovstiak@gmail.com> wrote:
> Good idea. I think this could be even better:
>
> instead of using third party, send partially signed TX from computer
> to smartphone. In case, you are paranoid, make 3oo5 address made of
> two cold storage keys, one on desktop/laptop, one on smartphone, one
> using third party.
>
https://www.bitcoinauthenticator.org/ - does this already, currently
in alpha
> > It should be possible to use multisig wallets to protect against
> malware. For example, a user could generate a wallet with 3 keys and
> require a transaction that has been signed by 2 of those keys. One key i=
s
> placed in cold storage and anther sent to a third-party.
>
BitGo, CryptoCorp and (slight variant) GreenAddress all offer this model.
--001a11c3f51ab8c6cb050e1eb87c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">We're way ahead of you guys ;)<br><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Mon, Feb 2, 2015 at 6:54 PM, Marti=
n Habov=C5=A1tiak <span dir=3D"ltr"><<a href=3D"mailto:martin.habovstiak=
@gmail.com" target=3D"_blank">martin.habovstiak@gmail.com</a>></span> wr=
ote:<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">Good idea. I think this could be even better:<br>
<br>
instead of using third party, send partially signed TX from computer<br>
to smartphone. In case, you are paranoid, make 3oo5 address made of<br>
two cold storage keys, one on desktop/laptop, one on smartphone, one<br>
using third party.<br></blockquote><div><br></div><div><a href=3D"https://w=
ww.bitcoinauthenticator.org/">https://www.bitcoinauthenticator.org/</a> =C2=
=A0 =C2=A0 =C2=A0- does this already, currently in alpha</div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex"><div class=3D""><div class=3D"h5">> It should be po=
ssible to use multisig wallets to protect against malware.=C2=A0 For exampl=
e, a user could generate a wallet with 3 keys and require a transaction tha=
t has been signed by 2 of those keys.=C2=A0 One key is placed in cold stora=
ge and anther sent to a third-party.<br></div></div></blockquote><div><br><=
/div><div>BitGo, CryptoCorp and (slight variant) GreenAddress all offer thi=
s model.=C2=A0</div></div></div></div>
--001a11c3f51ab8c6cb050e1eb87c--
|
