From: Zach Lym <zachlym@indolering•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] BIP39 (mnemonic seeds) Unicode normalization compatibility issue
Date: Wed, 17 May 2017 10:01:04 -0700 [thread overview]
Message-ID: <CABWuLVf6zUhyTSDkXv26WqUE43q7PHqtOtfm5SNs_LkbmGt9dQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
I am working on a replacement for BIP39 and noticed that the password
section mandates a Unicode normalization pass but does not prohibit
unassigned character points.
I believe that this is problematic as newer drafts of Unicode alter the
output of normalization passes. So if a user assigned a password using a
wallet that linked to Unicode 9 but input a code point reserved in Unicode
10, updating the wallet to Unicode 10 could incorrectly remap that code
point [0].
Thank you,
-Zach Lym
P.S. The relevant RFC on this subject specifies a different normalization
procedure [1]
[BIP39]: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
[0]: http://unicode.org/reports/tr15/#Stabilized_Strings
[1]: https://tools.ietf.org/html/rfc7564
[-- Attachment #2: Type: text/html, Size: 1445 bytes --]
reply other threads:[~2017-05-17 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABWuLVf6zUhyTSDkXv26WqUE43q7PHqtOtfm5SNs_LkbmGt9dQ@mail.gmail.com \
--to=zachlym@indolering$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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