public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: William Yager <will.yager@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet root key with optional encryption
Date: Mon, 21 Apr 2014 19:05:04 -0500	[thread overview]
Message-ID: <CAG8oi1NDfoDBT_DmcBVhc0tMMhO55oDcrQBbGmqh9OfgsnG4Lg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 1507 bytes --]

             reply	other threads:[~2014-04-22  0:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  0:05 William Yager [this message]
2014-04-24 19:39 ` [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet root key with optional encryption William Yager
  -- strict thread matches above, loose matches on Subject: below --
2013-07-22 13:14 [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet master seed " Mike Hearn
2013-07-22 21:37 ` Jean-Paul Kogelman
2013-11-16  2:47   ` Gregory Maxwell
2013-11-16  3:09     ` Jean-Paul Kogelman
2013-12-26 11:48       ` Jean-Paul Kogelman
2014-03-12  3:17         ` [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet root key " Jean-Paul Kogelman
2014-03-12 13:11           ` Pavol Rusnak
2014-03-12 15:45             ` Jean-Paul Kogelman
2014-03-12 15:55               ` Pavol Rusnak
2014-03-12 16:49                 ` Gary Rowe
2014-03-12 18:00                   ` William Yager
2014-03-12 19:35                   ` Jean-Paul Kogelman
2014-03-12 19:41                     ` Gary Rowe
2014-03-12 19:26                 ` Jean-Paul Kogelman
2014-03-12 19:39                   ` Pavol Rusnak
2014-03-12 19:55                     ` William Yager
2014-03-12 20:04                       ` Pavol Rusnak
2014-03-12 20:10                         ` William Yager
2014-03-12 20:24                           ` Pavol Rusnak
2014-03-12 20:37                             ` William Yager
2014-03-12 20:42                               ` Pavol Rusnak
2014-03-12 20:49                                 ` William Yager
2014-03-12 21:08                             ` Jean-Paul Kogelman
2014-03-12 21:15                               ` William Yager

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=CAG8oi1NDfoDBT_DmcBVhc0tMMhO55oDcrQBbGmqh9OfgsnG4Lg@mail.gmail.com \
    --to=will.yager@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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