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-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1VdwoW-0005JC-QW
for bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 06:42:04 +0000
X-ACL-Warn:
Received: from mail-ve0-f180.google.com ([209.85.128.180])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VdwoV-00008q-PI
for bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 06:42:04 +0000
Received: by mail-ve0-f180.google.com with SMTP id oy12so3336556veb.11
for <bitcoin-development@lists.sourceforge.net>;
Tue, 05 Nov 2013 22:41:58 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=n9jf53EKpFmYpttdVtNlMJIoTa+ZuSk39U9L19KmUvQ=;
b=FPiuA6zPsvLJJyXnO2Muv6k3Sz6te4e8aavSfXL6wXpUxEDanDzQJ+CeCZiJB3J61E
c5PytE/Y+1gN4gSTZGNlYwYCH2zZIyqM5bZhhLIYEfwo0AWLcFKAWdNcvEuOdaghc/oO
oOjuGOcHT2zBRyNMC+B3quArprxEEHfkDQrYINvW6LAQepCxvFpjIJF7BaqrNPe67drR
AqiV0EPd0YrxJAoKaC4QurGWvAWtEmEC+WWmJlReDSQX+M5+A9afpPASDvJ9yFEKo84P
wj1P54RO7qt3ESfNiG2iCTHS3P9/FpKSWV3Ok+Hb/BpfudtTAnehCq6s8OGlNVbVwPr1
kVgQ==
X-Gm-Message-State: ALoCoQnHsHTsL4E78bXKY5yxFx+l/QBI4V7GCahuUdD1S5TVXgo/Fo2C82xNYkx3XxF/sN8DrE7E
MIME-Version: 1.0
X-Received: by 10.58.210.66 with SMTP id ms2mr1147126vec.10.1383720118249;
Tue, 05 Nov 2013 22:41:58 -0800 (PST)
Sender: marek@palatinus.cz
Received: by 10.59.1.2 with HTTP; Tue, 5 Nov 2013 22:41:57 -0800 (PST)
Received: by 10.59.1.2 with HTTP; Tue, 5 Nov 2013 22:41:57 -0800 (PST)
In-Reply-To: <CAKaEYh+bAVcK0tUrE75HvSf0PJ5Ps1j_yUheBeOM5Q1EHADdCw@mail.gmail.com>
References: <20131102050144.5850@gmx.com>
<CAJna-HgUT2u+nhdz3e8mT99R+TR6o1FFQ4c8KBz_vpc_oSOzSQ@mail.gmail.com>
<CAKaEYh+bAVcK0tUrE75HvSf0PJ5Ps1j_yUheBeOM5Q1EHADdCw@mail.gmail.com>
Date: Wed, 6 Nov 2013 07:41:57 +0100
X-Google-Sender-Auth: 5bu1HNFCKvnQdKijXxIGw-1ClJo
Message-ID: <CAJna-HhuQZHb49-UGjpg3-T+wK7PPRa34=0xk4=Dw=6FeFBEpg@mail.gmail.com>
From: slush <slush@centrum.cz>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6ae8c1e080a04ea7c72f8
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VdwoV-00008q-PI
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>, bitcoingrant@gmx.com
Subject: Re: [Bitcoin-development] Message Signing based authentication
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: Wed, 06 Nov 2013 06:42:05 -0000
--047d7bd6ae8c1e080a04ea7c72f8
Content-Type: text/plain; charset=ISO-8859-1
> But where are the private keys stored? Crypto in the browser with help,
but although they will expose ECC via the NSS, I dont think bitcoin's
particular curve will be supported, because it's not NIST approved. If the
use case was presented though, they may add it.
Trezor, my friend.
Slush
Sent from mobile phone.
--047d7bd6ae8c1e080a04ea7c72f8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<p>> But where are the private keys stored? Crypto in the browser with h=
elp, but although they will expose ECC via the NSS, I dont think bitcoin=
9;s particular curve will be supported, because it's not NIST approved.=
If the use case was presented though, they may add it. </p>
<p>Trezor, my friend.</p>
<p>Slush</p>
<p>Sent from mobile phone.</p>
--047d7bd6ae8c1e080a04ea7c72f8--
|
