From: Melvin Carvalho <melvincarvalho@gmail.com>
To: slush <slush@centrum.cz>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>,
bitcoingrant@gmx.com
Subject: Re: [Bitcoin-development] Message Signing based authentication
Date: Fri, 6 Dec 2013 11:44:32 +0100 [thread overview]
Message-ID: <CAKaEYh+jKZ+MZ3p4Gf7pmmEnnkaXhBqSonD_-v=4mA1ppxNUHQ@mail.gmail.com> (raw)
In-Reply-To: <CAJna-HhuQZHb49-UGjpg3-T+wK7PPRa34=0xk4=Dw=6FeFBEpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
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.
>
[-- Attachment #2: Type: text/html, Size: 1141 bytes --]
prev parent reply other threads:[~2013-12-06 10:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 5:01 [Bitcoin-development] Message Signing based authentication bitcoingrant
2013-11-02 5:54 ` Luke-Jr
2013-11-02 13:02 ` Mike Hearn
2013-11-02 13:16 ` Melvin Carvalho
2013-11-02 13:19 ` Hannu Kotipalo
2013-11-02 16:26 ` Mike Hearn
2013-11-02 16:26 ` Mike Hearn
2013-11-02 16:52 ` Melvin Carvalho
2013-11-02 17:08 ` Jeff Garzik
2013-11-02 17:16 ` Hannu Kotipalo
2013-11-02 21:14 ` Johnathan Corgan
2013-11-02 21:51 ` Mark Friedenbach
2013-11-03 0:29 ` Allen Piscitello
2013-11-03 0:33 ` Luke-Jr
2013-11-03 1:19 ` Allen Piscitello
2013-11-03 1:27 ` Luke-Jr
2013-11-03 1:36 ` Allen Piscitello
2013-11-03 6:23 ` Timo Hanke
2013-11-06 3:38 ` Melvin Carvalho
2013-11-02 21:57 ` slush
2013-11-06 3:01 ` Melvin Carvalho
2013-11-06 6:41 ` slush
2013-12-06 10:44 ` Melvin Carvalho [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKaEYh+jKZ+MZ3p4Gf7pmmEnnkaXhBqSonD_-v=4mA1ppxNUHQ@mail.gmail.com' \
--to=melvincarvalho@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=bitcoingrant@gmx.com \
--cc=slush@centrum.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox