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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1Vostj-0002EP-5f
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Dec 2013 10:44:39 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.172 as permitted sender)
client-ip=209.85.223.172; envelope-from=melvincarvalho@gmail.com;
helo=mail-ie0-f172.google.com;
Received: from mail-ie0-f172.google.com ([209.85.223.172])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vosti-0001KB-3v
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Dec 2013 10:44:39 +0000
Received: by mail-ie0-f172.google.com with SMTP id qd12so884269ieb.3
for <bitcoin-development@lists.sourceforge.net>;
Fri, 06 Dec 2013 02:44:32 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.25.227 with SMTP id f3mr1890545igg.21.1386326672828; Fri,
06 Dec 2013 02:44:32 -0800 (PST)
Received: by 10.64.17.167 with HTTP; Fri, 6 Dec 2013 02:44:32 -0800 (PST)
In-Reply-To: <CAJna-HhuQZHb49-UGjpg3-T+wK7PPRa34=0xk4=Dw=6FeFBEpg@mail.gmail.com>
References: <20131102050144.5850@gmx.com>
<CAJna-HgUT2u+nhdz3e8mT99R+TR6o1FFQ4c8KBz_vpc_oSOzSQ@mail.gmail.com>
<CAKaEYh+bAVcK0tUrE75HvSf0PJ5Ps1j_yUheBeOM5Q1EHADdCw@mail.gmail.com>
<CAJna-HhuQZHb49-UGjpg3-T+wK7PPRa34=0xk4=Dw=6FeFBEpg@mail.gmail.com>
Date: Fri, 6 Dec 2013 11:44:32 +0100
Message-ID: <CAKaEYh+jKZ+MZ3p4Gf7pmmEnnkaXhBqSonD_-v=4mA1ppxNUHQ@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=047d7bd76b00e0955d04ecdb54b1
X-Spam-Score: -0.6 (/)
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
(melvincarvalho[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: centrum.cz]
1.0 HTML_MESSAGE BODY: HTML included in message
-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
X-Headers-End: 1Vosti-0001KB-3v
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: Fri, 06 Dec 2013 10:44:39 -0000
--047d7bd76b00e0955d04ecdb54b1
Content-Type: text/plain; charset=ISO-8859-1
On 6 November 2013 07:41, slush <slush@centrum.cz> wrote:
> > 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.
>
Looking forward to the trezor release, best of luck.
This may be an interesting read too:
https://www.grc.com/sqrl/sqrl.htm
> Slush
>
> Sent from mobile phone.
>
--047d7bd76b00e0955d04ecdb54b1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 6 November 2013 07:41, slush <span dir=3D"ltr"><<a href=3D"ma=
ilto:slush@centrum.cz" target=3D"_blank">slush@centrum.cz</a>></span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=3D"im"><p>> But where are the private keys stored? Crypto in =
the browser with help, but although they will expose ECC via the NSS, I don=
t 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. <=
/p>
</div><p>Trezor, my friend.</p></blockquote><div><br></div><div>Looking for=
ward to the trezor release, best of luck.<br><br></div><div>This may be an =
interesting read too:<br><br><a href=3D"https://www.grc.com/sqrl/sqrl.htm">=
https://www.grc.com/sqrl/sqrl.htm</a><br>
</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<p>Slush</p>
<p>Sent from mobile phone.</p>
</blockquote></div><br></div></div>
--047d7bd76b00e0955d04ecdb54b1--
|