From: Pavol Rusnak <stick@gk2•sk>
To: Mem Wallet <memwallet.info@gmail•com>,
bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] bip44 GPG identities - POC demo
Date: Sun, 08 Mar 2015 02:34:38 +0100 [thread overview]
Message-ID: <54FBA72E.4040308@gk2.sk> (raw)
In-Reply-To: <CAKzHBKnh+yzTwXkZXmezRaOkTTnUO4Z1dJnvKjYGnZBKoNQNEQ@mail.gmail.com>
On 07/03/15 16:53, Mem Wallet wrote:
> this allows a user to manage a GPG identity for encryption
> and signing with zero bytes of permanent storage. (on tails for example)
Hi!
As an author of BIP44 I don't think that you should use BIP44 for this
and a new BIP number should be allocated. To me it does not make much
sense to create GPG key hierarchy per Bitcoin account, but rather create
a GPG key hierarchy per device/master seed.
I am currently in process of implementing a SignIdentity message for
TREZOR, which will be used for HTTPS/SSH/etc. logins.
See PoC here:
https://github.com/trezor/trezor-emu/commit/9f612c286cc7b8268ebaec4a36757e1c19548717
The idea is to derive the BIP32 path from HTTPS/SSH URI (by hashing it
and use m/46'/a'/b'/c'/d' where a,b,c,d are first 4*32 bits of the hash)
and use that to derive the private key. This scheme might work for GPG
keys (just use gpg://user@host.com for the URI) as well.
--
Best Regards / S pozdravom,
Pavol Rusnak <stick@gk2•sk>
next prev parent reply other threads:[~2015-03-08 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 15:53 Mem Wallet
2015-03-08 1:34 ` Pavol Rusnak [this message]
2015-03-08 8:20 ` Natanael
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=54FBA72E.4040308@gk2.sk \
--to=stick@gk2$(echo .)sk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=memwallet.info@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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