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 ) 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 ; 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: References: <20131102050144.5850@gmx.com> Date: Fri, 6 Dec 2013 11:44:32 +0100 Message-ID: From: Melvin Carvalho To: slush 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" , 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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



On 6 November 2013 07:41, slush <slush@centrum.cz> wr= ote:

> 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>

Trezor, my friend.


Looking for= ward to the trezor release, best of luck.

This may be an = interesting read too:

= https://www.grc.com/sqrl/sqrl.htm
=A0

Slush

Sent from mobile phone.


--047d7bd76b00e0955d04ecdb54b1--