From mboxrd@z Thu Jan 1 00:00:00 1970 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 1YUQ7H-0004J3-UA for bitcoin-development@lists.sourceforge.net; Sun, 08 Mar 2015 01:34:51 +0000 X-ACL-Warn: Received: from mail-wg0-f49.google.com ([74.125.82.49]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YUQ7E-0001Xi-Pb for bitcoin-development@lists.sourceforge.net; Sun, 08 Mar 2015 01:34:51 +0000 Received: by wgha1 with SMTP id a1so16948193wgh.1 for ; Sat, 07 Mar 2015 17:34:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qy46IMZVoXy+OySpdGPu62G/htnn4ZCT7f6MP3L2QcY=; b=EWolq3wiV8ArGZCQxz6XxuVWrv+UNhAqwtauLxB/M1Zs/NvqseY5AtkTEOSdpip1RP R0Ko+cK1JsZBG0Fas3kxW4oBgo5N+Bw/P4D33zt+f7TQIicsG9ZUSxGwjEQNzjJ9odD+ OvNmD4ubZFHdg8mI7hwoEt25dwFMc6OrQEW6+7OmrLgwLkT/Ns6is7O8RLAaD34sasW7 d8X2vbzBoEqI2+k9vMhGpefsU4ZUYcvj+VMdiDaJ7smRWzksVRmtfMtcEowYBJBfgkTe RJQjXumLMw3IRnZV83+mGV3m8FOIdsA1wyAqVOaGeZD+Wz4THWo20R1OxY3GR95aKvw3 p7Wg== X-Gm-Message-State: ALoCoQn3Lsh79TeowX6z8icOia05GXb5I8Qpy6LlESYzNV49GFLwaNd8zzyMugD54Pl+IUuM4otA X-Received: by 10.194.83.66 with SMTP id o2mr44966109wjy.55.1425778482432; Sat, 07 Mar 2015 17:34:42 -0800 (PST) Received: from tetra.site ([185.68.217.48]) by mx.google.com with ESMTPSA id lb6sm21729491wjb.22.2015.03.07.17.34.39 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Mar 2015 17:34:41 -0800 (PST) Message-ID: <54FBA72E.4040308@gk2.sk> Date: Sun, 08 Mar 2015 02:34:38 +0100 From: Pavol Rusnak User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Mem Wallet , bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1YUQ7E-0001Xi-Pb Subject: Re: [Bitcoin-development] bip44 GPG identities - POC demo 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: Sun, 08 Mar 2015 01:34:52 -0000 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