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
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 6C4F7941
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 17 Aug 2016 00:14:16 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148102.authsmtp.net (outmail148102.authsmtp.net
[62.13.148.102])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id C566A1A9
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 17 Aug 2016 00:14:15 +0000 (UTC)
Received: from mail-c247.authsmtp.com (mail-c247.authsmtp.com [62.13.128.247])
by punt20.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u7H0EDJJ026734;
Wed, 17 Aug 2016 01:14:13 +0100 (BST)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u7H0EAhF061756
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Wed, 17 Aug 2016 01:14:11 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id F08B0400DD;
Wed, 17 Aug 2016 00:11:05 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id ED05520B3A; Tue, 16 Aug 2016 17:14:07 -0700 (PDT)
Date: Tue, 16 Aug 2016 17:14:07 -0700
From: Peter Todd <pete@petertodd.org>
To: Aiqin Li <liaiqin.lanzhou@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20160817001407.GA6571@fedora-21-dvm>
References: <57B31EBC.1030806@jonasschnelli.ch>
<0501f5c2-611c-53c1-5fd1-d4da5ba5137b@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0"
Content-Disposition: inline
In-Reply-To: <0501f5c2-611c-53c1-5fd1-d4da5ba5137b@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: 860127ef-640f-11e6-bcde-0015176ca198
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdwUUGUATAgsB AmAbW1VeUVl7WGI7 bghPaBtcak9QXgdq
T0pMXVMcUQIQAWlw XmgeVBh1cgMIcHlx bQhqWHBaXkMvI1t7
Rk4CCGwHMGF9OjNL BV1YdwJRcQRMLU5E Y1gxNiYHcQ5VPz4z
GA41ejw8IwAXCC1P Th4EN19afk8PGjMg DyseFDMjFFcJLwAA
X-Authentic-SMTP: 61633532353630.1038:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Hardware Wallet Standard
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 00:14:16 -0000
--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Aug 17, 2016 at 09:36:02AM +1000, Aiqin Li via bitcoin-dev wrote:
> Out of curiosity, what is the technical reason a normal ECC-enabled
> smart-card cannot be used for the hardware signing component of a wallet
> app? (Since if it can, its standardization must have been discussed.)
>=20
> Debian wiki gives a list of such cards with related opensource software to
> access them.
I'm not aware of any ECC-enabled smart-cards that can sign the specific cur=
ve
that Bitcoin uses, not to mention the fact that those smartcards generally =
only
speak higher level protocols than raw signature generation, precluding the
signing of bitcoin transactions.
The other serious problem - and this is a problem with smartcards in general
anyway - is that without Bitcoin-specific logic you're just signing blindly=
; we
recently saw the problems with that with the Bitfinex/BitGo hack. And even
then, without a screen most of the hardware wallets in are still just signi=
ng
blindly, with at best hard-to-use limits on maximum funds moved
per-transaction. Also note how even hardware wallets with a screen, like
Trezor, aren't yet able to authenticate who you are paying.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--6TrnltStXW4iwmi0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJXs6xNAAoJEGOZARBE6K+yNtUH/Rq3yQdaiGiGylRJg9L4r4AD
Pt6o5Svs/bD5yFYutcQkBP7O/u3JVCy+suK4s9gPRJ9ryzAY8Ca96HRfzP1AZZDt
NOpoDi9SyyuvymZoiM0uR3Z9SHGBkHTIdDFze4cG28hR2xsPAIYlneAKq9mxLtrZ
A6u1jGH38Ee+y5C5G+Ekj/L9/O/+I/kBlK9sYmLVsgRZAQCl6AZxtn9KO/ttjjhd
udUt9Eybx45kpxk2AE/QeLFttWdesYgqJUF5d3eveAupW7PI5s6VQIqZQNPCbF9+
g499A4T8NR0ntL4nD5uZviXzqqhtObqHy9uG1A2QOHqTJSHZIcaCrZTy177sXFI=
=1b6E
-----END PGP SIGNATURE-----
--6TrnltStXW4iwmi0--
|
