Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X7WPY-00069L-S9 for bitcoin-development@lists.sourceforge.net; Wed, 16 Jul 2014 21:06:48 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.218.53 as permitted sender) client-ip=209.85.218.53; envelope-from=voisine@gmail.com; helo=mail-oi0-f53.google.com; Received: from mail-oi0-f53.google.com ([209.85.218.53]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X7WPX-0000lN-G0 for bitcoin-development@lists.sourceforge.net; Wed, 16 Jul 2014 21:06:48 +0000 Received: by mail-oi0-f53.google.com with SMTP id e131so256056oig.12 for ; Wed, 16 Jul 2014 14:06:42 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.200.169 with SMTP id jt9mr40024789obc.0.1405544801928; Wed, 16 Jul 2014 14:06:41 -0700 (PDT) Received: by 10.60.169.109 with HTTP; Wed, 16 Jul 2014 14:06:41 -0700 (PDT) In-Reply-To: References: Date: Wed, 16 Jul 2014 14:06:41 -0700 Message-ID: From: Aaron Voisine To: Andreas Schildbach Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (voisine[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1X7WPX-0000lN-G0 Cc: Bitcoin Development Subject: Re: [Bitcoin-development] BIP 38 NFC normalisation issue X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2014 21:06:49 -0000 If I first remove \u0000, so the non-normalized passphrase is "\u03D2\u0301\U00010400\U0001F4A9", and then NFC normalize it, it becomes "\u03D3\U00010400\U0001F4A9" UTF-8 encoded this is: 0xcf93f0909080f09f92a9 (not the same as what you got, Andreas!) Encoding private key: 5Jajm8eQ22H3pGWLEVCXyvND8dQZhiQhoLJNKjYXk9roUFTMSZ4 with this passphrase, I get a BIP38 key of: 6PRW5o9FMb4hAYRQPmgcvVDTyDtr6R17VMXGLmvKjKVpGkYhBJ4uYuR9wZ I recommend rather than simply removing control characters from the password that instead the spec require that passwords containing control characters are invalid. We don't want people trying to be clever and putting them in thinking they are adding to the password entropy. Also for UI compatibility across many platforms, I'm also in favor disallowing any character below U+0020 (space) I can submit a PR once we figure out why Andreas's passphrase was different than what I got. Aaron Voisine breadwallet.com On Wed, Jul 16, 2014 at 4:04 AM, Andreas Schildbach wrote: > Damn, I just realized that I implement only the decoding side of BIP38. > So I cannot propose a complete test vector. Here is what I have: > > > Passphrase: =CF=92=CC=81=E2=90=80=F0=90=90=80=F0=9F=92=A9 (\u03D2\u0301\u= 0000\U00010400\U0001F4A9; GREEK > UPSILON WITH HOOK, COMBINING ACUTE ACCENT, NULL, DESERET CAPITAL LETTER > LONG I, PILE OF POO) > > Passphrase bytes after removing ISO control characters and NFC > normalization: 0xcf933034303066346139 > > Bitcoin Address: 16ktGzmfrurhbhi6JGqsMWf7TyqK9HNAeF > > Unencrypted private key (WIF): > 5Jajm8eQ22H3pGWLEVCXyvND8dQZhiQhoLJNKjYXk9roUFTMSZ4 > > > Can someone calculate the encrypted key from it (using whatever > implementation) and I will verify it decodes properly in bitcoinj? > > > > On 07/16/2014 12:46 PM, Andreas Schildbach wrote: >> I will change the bitcoinj implementation and propose a new test vector. >> >> >> >> On 07/16/2014 11:29 AM, Mike Hearn wrote: >>> Yes sorry, you're right, the issue starts with the null code point. >>> Python seems to have problems starting there too. It might work if we >>> took that out. >>> >>> >>> On Wed, Jul 16, 2014 at 11:17 AM, Andreas Schildbach >>> > wrote: >>> >>> Guys, you are always talking about the Unicode astral plane, but in= fact >>> its a plain old (ASCII) control character where this problem starts= and >>> likely ends: \u0000. >>> >>> Let's ban/filter ISO control characters and be done with it. Most >>> control characters will never be enterable by any keyboard into a >>> password field. Of course I assume that Character.isISOControl() wo= rks >>> consistently across platforms. >>> >>> http://docs.oracle.com/javase/7/docs/api/java/lang/Character.html#i= sISOControl%28char%29 >>> >>> >>> On 07/16/2014 12:23 AM, Aaron Voisine wrote: >>> > If the user creates a password on an iOS device with an astral >>> > character and then can't enter that password on a JVM wallet, tha= t >>> > sucks. If JVMs really can't support unicode NFC then that's a str= ong >>> > case to limit the spec to the subset of unicode that all popular >>> > platforms can support, but it sounds like it might just be a JVM >>> > string library bug that could hopefully be reported and fixed. I = get >>> > the same result as in the test case using apple's >>> > CFStringNormalize(passphrase, kCFStringNormalizationFormC); >>> > >>> > Aaron Voisine >>> > breadwallet.com >>> > >>> > >>> > On Tue, Jul 15, 2014 at 11:20 AM, Mike Hearn >> > wrote: >>> >> Yes, we know, Andreas' code is indeed doing normalisation. >>> >> >>> >> However it appears the output bytes end up being different. What >>> I get back >>> >> is: >>> >> >>> >> cf930001303430300166346139 >>> >> >>> >> vs >>> >> >>> >> cf9300f0909080f09f92a9 >>> >> >>> >> from the spec. >>> >> >>> >> I'm not sure why. It appears this is due to the character from >>> the astral >>> >> planes. Java is old and uses 16 bit characters internally - it >>> wouldn't >>> >> surprise me if there's some weirdness that means it doesn't/won'= t >>> support >>> >> this kind of thing. >>> >> >>> >> I recommend instead that any implementation that wishes to be >>> compatible >>> >> with JVM based wallets (I suspect Android is the same) just >>> refuse any >>> >> passphrase that includes characters outside the BMP. At least >>> unless someone >>> >> can find a fix. I somehow doubt this will really hurt anyone. >>> >> >>> >> >>> -------------------------------------------------------------------= ----------- >>> >> Want fast and easy access to all the code in your enterprise? >>> Index and >>> >> search up to 200,000 lines of code with a free copy of Black Duc= k >>> >> Code Sight - the same software that powers the world's largest c= ode >>> >> search on Ohloh, the Black Duck Open Hub! Try it now. >>> >> http://p.sf.net/sfu/bds >>> >> _______________________________________________ >>> >> Bitcoin-development mailing list >>> >> Bitcoin-development@lists.sourceforge.net >>> >>> >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >>> >> >>> > >>> > >>> -------------------------------------------------------------------= ----------- >>> > Want fast and easy access to all the code in your enterprise? >>> Index and >>> > search up to 200,000 lines of code with a free copy of Black Duck >>> > Code Sight - the same software that powers the world's largest co= de >>> > search on Ohloh, the Black Duck Open Hub! Try it now. >>> > http://p.sf.net/sfu/bds >>> > >>> >>> >>> >>> -------------------------------------------------------------------= ----------- >>> Want fast and easy access to all the code in your enterprise? Index= and >>> search up to 200,000 lines of code with a free copy of Black Duck >>> Code Sight - the same software that powers the world's largest code >>> search on Ohloh, the Black Duck Open Hub! Try it now. >>> http://p.sf.net/sfu/bds >>> _______________________________________________ >>> Bitcoin-development mailing list >>> Bitcoin-development@lists.sourceforge.net >>> >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >>> >>> >>> >>> >>> -----------------------------------------------------------------------= ------- >>> Want fast and easy access to all the code in your enterprise? Index and >>> search up to 200,000 lines of code with a free copy of Black Duck >>> Code Sight - the same software that powers the world's largest code >>> search on Ohloh, the Black Duck Open Hub! Try it now. >>> http://p.sf.net/sfu/bds >>> >>> >>> >>> _______________________________________________ >>> Bitcoin-development mailing list >>> Bitcoin-development@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >>> >> >> >> >> ------------------------------------------------------------------------= ------ >> Want fast and easy access to all the code in your enterprise? Index and >> search up to 200,000 lines of code with a free copy of Black Duck >> Code Sight - the same software that powers the world's largest code >> search on Ohloh, the Black Duck Open Hub! Try it now. >> http://p.sf.net/sfu/bds >> > > > > -------------------------------------------------------------------------= ----- > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development