Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.53 as permitted sender)
	client-ip=209.85.216.53; envelope-from=jan.moller@gmail.com;
	helo=mail-qa0-f53.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAAS2fgQJ2EULensrGfB-Rj95+MyxtkQFUHaKs_bJOOBBTqPE_Q@mail.gmail.com>
References: <CAC7yFxSE8-TWPN-kuFiqdPKMDuprbiVJi7-z-ym+AUyA_f-xJw@mail.gmail.com>
	<6669921.kYEqrMqt0u@crushinator>
	<CAAS2fgSfiYwD-M7+k65JF0Kjeod1zEiPcxPN1iDBHLzYV7UQyA@mail.gmail.com>
	<16848732.PiyLLsBBZa@crushinator>
	<CAC7yFxR7XWtFSMeHgbMZOMKbr+kK_7Ezb7zBUQP08rfC0am9sQ@mail.gmail.com>
	<CABh=4qNaJht-MnnjEguZ=UOuXN3uQ-s4-dkDUVErbHj6W44J_g@mail.gmail.com>
	<CAAS2fgQJ2EULensrGfB-Rj95+MyxtkQFUHaKs_bJOOBBTqPE_Q@mail.gmail.com>
Date: Tue, 22 Apr 2014 10:49:41 +0200
Message-ID: <CABh=4qPMtnZsPfanJgi63vo6Bt4TTQLx7EqJh268+NUxb4gC7A@mail.gmail.com>
From: =?UTF-8?Q?Jan_M=C3=B8ller?= <jan.moller@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c0ff125ca7b904f79db2d9
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Presenting a BIP for Shamir's Secret
 Sharing of Bitcoin private keys
Precedence: list
Reply-To: jan.moller@gmail.com

--001a11c0ff125ca7b904f79db2d9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I did comment on it back in october (
https://bitcointalk.org/index.php?topic=3D258678.msg3298089#msg3298089) :-)
But I must admit that I haven't been tracking it since then.

I have never been a proponent of BIP 38 (which this BIP is derived from)
and generally think that encrypting a secret with a human generated
password is silly for many reasons (Let me know if I should repeat my list
of concerns). As far as I remember we are pretty much on the same page here=
.
Using SSS is superior in every way that I can think of.


On Tue, Apr 22, 2014 at 10:15 AM, Gregory Maxwell <gmaxwell@gmail.com>wrote=
:

> On Tue, Apr 22, 2014 at 1:06 AM, Jan M=C3=B8ller <jan.moller@gmail.com> w=
rote:
> > This is a very useful BIP, and I am very much looking forward to
> > implementing it in Mycelium, in particular for bip32 wallets.
>
> I haven't seen commentary from you on the Kogelman draft, it would be
> helpful there: https://bitcointalk.org/index.php?topic=3D258678.0
>

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

<div dir=3D"ltr">I did comment on it back in october (<a href=3D"https://bi=
tcointalk.org/index.php?topic=3D258678.msg3298089#msg3298089">https://bitco=
intalk.org/index.php?topic=3D258678.msg3298089#msg3298089</a>) :-)<div>But =
I must admit that I haven&#39;t been tracking it since then.</div>
<div><br></div><div>I have never been a proponent of BIP 38 (which this BIP=
 is derived from) and generally think that encrypting a secret with a human=
 generated password is silly for many reasons (Let me know if I should repe=
at my list of concerns). As far as I remember we are pretty much on the sam=
e page here.</div>
<div>Using SSS is superior in every way that I can think of.</div></div><di=
v class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Apr 22, =
2014 at 10:15 AM, Gregory Maxwell <span dir=3D"ltr">&lt;<a href=3D"mailto:g=
maxwell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On Tue, Apr 22, 2014 at 1:06=
 AM, Jan M=C3=B8ller &lt;<a href=3D"mailto:jan.moller@gmail.com">jan.moller=
@gmail.com</a>&gt; wrote:<br>

&gt; This is a very useful BIP, and I am very much looking forward to<br>
&gt; implementing it in Mycelium, in particular for bip32 wallets.<br>
<br>
</div>I haven&#39;t seen commentary from you on the Kogelman draft, it woul=
d be<br>
helpful there: <a href=3D"https://bitcointalk.org/index.php?topic=3D258678.=
0" target=3D"_blank">https://bitcointalk.org/index.php?topic=3D258678.0</a>=
<br>
</blockquote></div><br></div>

--001a11c0ff125ca7b904f79db2d9--