public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Weiwu Zhang <a@colourful.land>
To: Ronald van der Meer <ronald@vandermeer.frl>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Suggestion to remove word from BIP39 English wordlist
Date: Thu, 18 Jan 2018 09:07:53 +0800	[thread overview]
Message-ID: <CAEvpD62pd_s17VoGw8B+=3_cmMq2cWneAR0MZ_CT_7DqooBnLQ@mail.gmail.com> (raw)
In-Reply-To: <31430A55-57AD-4648-8D6D-DE2A45CC013C@vandermeer.frl>

2018-01-09 19:20 GMT+08:00 Ronald van der Meer via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org>:
> After reviewing some bitcoin improvement proposals, I noticed that one of the words that can be found on the BIP39 English wordlist is “satoshi”.
> I suggest removing this word from the list so it’s less obvious that it’s a bitcoin seed when found by a malicious third party.

If a malicious third party discovers a word list that look like a
seed, they would try using it as Bitcoin seed first anyway, with or
without finding the word 'satoshi' in it. The security threat is that
a malicious third party may index what they found and test every
occurrence of 'satoshi' for a lead to a seed.

For example, a hard-disk recycling service would add this word to
their salvage tools. Any successfully hacked gmail account will be
'satoshi' tested too.

So I see this as a reasonable improvement:)


  reply	other threads:[~2018-01-18  1:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 11:20 [bitcoin-dev] Suggestion to remove word from BIP39 English wordlist Ronald van der Meer
2018-01-18  1:07 ` Weiwu Zhang [this message]
2018-01-18  1:14   ` CryptAxe
2018-01-18  6:55     ` Jonathan Sterling
2018-01-18 19:50       ` Alan Evans
2018-01-18 20:49 Matthew Clancy
2018-01-18 21:29 ` Alan Evans
2018-01-23 19:40   ` Ronald van der Meer

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='CAEvpD62pd_s17VoGw8B+=3_cmMq2cWneAR0MZ_CT_7DqooBnLQ@mail.gmail.com' \
    --to=a@colourful.land \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=ronald@vandermeer.frl \
    /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