blob: 04589b3b696f6018a4c08b1ef6159c8be8af14b5 (
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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <brian.erdelyi@gmail.com>) id 1YIKyz-0000Ly-8H
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Feb 2015 17:40:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.169 as permitted sender)
client-ip=209.85.216.169; envelope-from=brian.erdelyi@gmail.com;
helo=mail-qc0-f169.google.com;
Received: from mail-qc0-f169.google.com ([209.85.216.169])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YIKyy-0004mh-E4
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Feb 2015 17:40:21 +0000
Received: by mail-qc0-f169.google.com with SMTP id b13so31284185qcw.0
for <bitcoin-development@lists.sourceforge.net>;
Mon, 02 Feb 2015 09:40:15 -0800 (PST)
X-Received: by 10.140.81.208 with SMTP id f74mr6602277qgd.94.1422898814428;
Mon, 02 Feb 2015 09:40:14 -0800 (PST)
Received: from [192.168.1.58] ([64.147.83.112])
by mx.google.com with ESMTPSA id a1sm18880853qab.28.2015.02.02.09.40.13
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 02 Feb 2015 09:40:13 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Brian Erdelyi <brian.erdelyi@gmail.com>
In-Reply-To: <54CE3816.6020505@bitwatch.co>
Date: Mon, 2 Feb 2015 13:40:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com>
References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com>
<54CE3816.6020505@bitwatch.co>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
X-Mailer: Apple Mail (2.2070.6)
X-Spam-Score: -1.2 (-)
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
-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
0.4 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YIKyy-0004mh-E4
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 17:40:21 -0000
Another concept...
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 =
is placed in cold storage and anther sent to a third-party.
It is now possible to generate and sign transactions on the users =
computer and send this signed transaction to the third-party for the =
second signature. This now permits the use of out of band transaction =
verification techniques before the third party signs the transaction and =
sends to the blockchain.
If the third-party is malicious or becomes compromised they would not =
have the ability to complete transactions as they only have one private =
key. If the third-party disappeared, the user could use the key in cold =
storage to sign transactions and send funds to a new wallet.
Thoughts?=
|
