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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1V9tRZ-0004t1-EQ
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Aug 2013 09:02:09 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.178 as permitted sender)
client-ip=209.85.214.178; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f178.google.com;
Received: from mail-ob0-f178.google.com ([209.85.214.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V9tRX-0001lT-Kl
for bitcoin-development@lists.sourceforge.net;
Thu, 15 Aug 2013 09:02:09 +0000
Received: by mail-ob0-f178.google.com with SMTP id ef5so540124obb.37
for <bitcoin-development@lists.sourceforge.net>;
Thu, 15 Aug 2013 02:02:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.145.241 with SMTP id sx17mr213995oeb.57.1376557322231;
Thu, 15 Aug 2013 02:02:02 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.80.165 with HTTP; Thu, 15 Aug 2013 02:02:02 -0700 (PDT)
In-Reply-To: <CAJna-HhS=iNcTcTzEm_GDtjzxbSTDJ0KvEjLvpnR_HngRYjHeA@mail.gmail.com>
References: <CABsx9T3DM72+8HgNWWZ2HaAgZMQGAPn87L9VVKdkbVkS7sd8Tg@mail.gmail.com>
<CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
<CAJna-HhS=iNcTcTzEm_GDtjzxbSTDJ0KvEjLvpnR_HngRYjHeA@mail.gmail.com>
Date: Thu, 15 Aug 2013 11:02:02 +0200
X-Google-Sender-Auth: VBxWFO9feYq6aY_XmeM5UcGF6qY
Message-ID: <CANEZrP3-SV0=PB5rkXbAEKv1CFqfS4hjuBTY3YbU-yNGKde8tg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=047d7b5d474a34682504e3f8baa5
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: 1V9tRX-0001lT-Kl
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Version 0.9 goals
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: Thu, 15 Aug 2013 09:02:09 -0000
--047d7b5d474a34682504e3f8baa5
Content-Type: text/plain; charset=UTF-8
On Thu, Aug 15, 2013 at 10:22 AM, slush <slush@centrum.cz> wrote:
> We're planning to support payment protocol in Trezor as well, if it
> counts. I think it's a missing piece in absolute security of hardware
> wallets.
>
Yup, that's always been the plan :-)
Any idea how much work it is, and would it be a v1 feature of the Trezor or
added later via firmware update?
--047d7b5d474a34682504e3f8baa5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Thu, Aug 15, 2013 at 10:22 AM, slush <span dir=3D"ltr">=
<<a href=3D"mailto:slush@centrum.cz" target=3D"_blank">slush@centrum.cz<=
/a>></span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">We're planning to support payment protocol in Trezor a=
s well, if it counts. I think it's a missing piece in absolute security=
of hardware wallets.<br></div></blockquote><div><br></div><div>Yup, that&#=
39;s always been the plan :-)=C2=A0</div>
<div><br></div><div>Any idea how much work it is, and would it be a v1 feat=
ure of the Trezor or added later via firmware update?</div></div></div></di=
v>
--047d7b5d474a34682504e3f8baa5--
|
