Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <memwallet.info@gmail.com>) id 1YUH2u-00011o-Ke
	for bitcoin-development@lists.sourceforge.net;
	Sat, 07 Mar 2015 15:53:44 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.172 as permitted sender)
	client-ip=209.85.213.172; envelope-from=memwallet.info@gmail.com;
	helo=mail-ig0-f172.google.com; 
Received: from mail-ig0-f172.google.com ([209.85.213.172])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YUH2s-000752-PY
	for bitcoin-development@lists.sourceforge.net;
	Sat, 07 Mar 2015 15:53:44 +0000
Received: by igbhl2 with SMTP id hl2so10967205igb.3
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 07 Mar 2015 07:53:37 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.50.111.168 with SMTP id ij8mr11505875igb.43.1425743617451;
	Sat, 07 Mar 2015 07:53:37 -0800 (PST)
Received: by 10.36.78.78 with HTTP; Sat, 7 Mar 2015 07:53:37 -0800 (PST)
Date: Sat, 7 Mar 2015 10:53:37 -0500
Message-ID: <CAKzHBKnh+yzTwXkZXmezRaOkTTnUO4Z1dJnvKjYGnZBKoNQNEQ@mail.gmail.com>
From: Mem Wallet <memwallet.info@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b414534dbeaf70510b4cd24
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
	(memwallet.info[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	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: 1YUH2s-000752-PY
Subject: [Bitcoin-development] bip44 GPG identities - POC demo
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: Sat, 07 Mar 2015 15:53:44 -0000

--047d7b414534dbeaf70510b4cd24
Content-Type: text/plain; charset=UTF-8

If anyone is interested in using a bip44 Wallet to generate
deterministic GPG identities, I have implemented a demonstration in
javascript.

http://memwallet.info/bip44ext/test.html

this allows a user to manage a GPG identity for encryption
and signing with zero bytes of permanent storage. (on tails for example)


Paper is here still:

https://github.com/taelfrinn/bip44extention/blob/master/README.md

One minor correction added which specifies that the smallest S value
should be used, to prevent different ecdsa implementations from creating
non-canonical/identical outputs.

comments welcome

--047d7b414534dbeaf70510b4cd24
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><br></div>If anyone is interested=
 in using a bip44 Wallet to generate<br></div>deterministic GPG identities,=
 I have implemented a demonstration in<br></div>javascript. <br><br><a href=
=3D"http://memwallet.info/bip44ext/test.html">http://memwallet.info/bip44ex=
t/test.html</a><br><br></div>this allows a user to manage a GPG identity fo=
r encryption<br></div>and signing with zero bytes of permanent storage. (on=
 tails for example)<br><div><div><div><div><div><br><br>Paper is here still=
:<br><br><a href=3D"https://github.com/taelfrinn/bip44extention/blob/master=
/README.md">https://github.com/taelfrinn/bip44extention/blob/master/README.=
md</a><br><br></div><div>One minor correction added which specifies that th=
e smallest S value<br></div><div>should be used, to prevent different ecdsa=
 implementations from creating<br></div><div>non-canonical/identical output=
s.<br><br></div><div>comments welcome<br></div></div></div></div></div></di=
v>

--047d7b414534dbeaf70510b4cd24--