Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.192.46 as permitted sender)
	client-ip=209.85.192.46; envelope-from=will.yager@gmail.com;
	helo=mail-qg0-f46.google.com; 
MIME-Version: 1.0
Date: Mon, 21 Apr 2014 19:05:04 -0500
Message-ID: <CAG8oi1NDfoDBT_DmcBVhc0tMMhO55oDcrQBbGmqh9OfgsnG4Lg@mail.gmail.com>
From: William Yager <will.yager@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a113a9b8235eb2f04f7965eb7
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet
 root key with optional encryption
Precedence: list

--001a113a9b8235eb2f04f7965eb7
Content-Type: text/plain; charset=UTF-8

The spec has been updated a bit.

Even if the bulk of the key-stretching work has been outsourced to another
device, and that device is compromised, the passphrase is now protected by
minimum 8192 rounds of salted PBKDF2-HMAC-SHA512.

The idea is that more powerful devices (mobile phones, laptops, etc.) can
do all the key-stretching on their own, whereas weaker devices with access
to another device with more computing power (like Trezors) do a fair amount
of key-stretching on their own, but can safely export the rest of the
key-stretching to the other device.

Will

On Tue, Mar 11, 2014 at 10:17 PM, Jean-Paul Kogelman <
jeanpaulkogelman@me.com> wrote:

> Hi everyone,
>
> We've been hard at work updating the spec to include features that were
> requested. We've removed the Scrypt dependency that was present in the
> initial drafts, added new KDFs, added plausible deniability and have a
> reference implementation.
>
>
> Kind regards,
>
>
> Jean-Paul Kogelman
>

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

<div dir=3D"ltr">The spec has been updated a bit.<div><br></div><div>Even i=
f the bulk of the key-stretching work has been outsourced to another device=
, and that device is compromised, the passphrase is now protected by minimu=
m 8192 rounds of salted PBKDF2-HMAC-SHA512.=C2=A0</div>
<div><br></div><div>The idea is that more powerful devices (mobile phones, =
laptops, etc.) can do all the key-stretching on their own, whereas weaker d=
evices with access to another device with more computing power (like Trezor=
s) do a fair amount of key-stretching on their own, but can safely export t=
he rest of the key-stretching to the other device.</div>
<div><br></div><div>Will</div><div><br></div><div><div class=3D"gmail_extra=
"><div class=3D"gmail_quote">On Tue, Mar 11, 2014 at 10:17 PM, Jean-Paul Ko=
gelman <span dir=3D"ltr">&lt;<a href=3D"mailto:jeanpaulkogelman@me.com" tar=
get=3D"_blank">jeanpaulkogelman@me.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>Hi =
everyone,</div><div><br></div><div>We&#39;ve been hard at work updating the=
 spec to include features that were requested. We&#39;ve removed the Scrypt=
 dependency that was present in the initial drafts, added new KDFs, added p=
lausible deniability and have a reference implementation.</div>
<div><br></div><div><br></div><div>Kind regards,</div><div><br></div><div><=
br></div><div>Jean-Paul Kogelman</div></div></blockquote></div></div></div>=
</div>

--001a113a9b8235eb2f04f7965eb7--