{"type":"rich","version":"1.0","author_name":"npub1vqn4xza40eqyxv2hx5a2p504zn92f42qx8wcvuvxpw4a4w78uy0sf2g27t","author_url":"https://nostr.ae/npub1vqn4xza40eqyxv2hx5a2p504zn92f42qx8wcvuvxpw4a4w78uy0sf2g27t","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-07-15\n📝 Original message:I don't know for sure if the test vector is correct NFC form.  But for what\nit's worth, the Pile of Poo character is pretty easily accessible on the\niPhone and Android keyboards, and in this string it's already in NFC form\n(f09f92a9 in the test result).  I've certainly seen it in usernames around\nthe internet, and wouldn't be surprised to see it in passphrases entered on\nsmartphones, especially if the author of a BIP38-compatible app includes a\n(possibly ill-advised) suggestion to have your passphrase \"include special\ncharacters\".\n\nI haven't seen the NULL character on any smartphone keyboards, though - I\nassume the iOS and Android developers had the foresight to know how much\nhavoc that would wreak on systems assuming null-terminated strings.  It\nseems unlikely that NULL would be in a real-world passphrase entered by a\nsane user.\n\n\nOn Tue, Jul 15, 2014 at 8:03 AM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\n\u003e [+cc aaron]\n\u003e\n\u003e We recently added an implementation of BIP 38 (password protected private\n\u003e keys) to bitcoinj. It came to my attention that the third test vector may\n\u003e be broken. It gives a hex version of what the NFC normalised version of the\n\u003e input string should be, but this does not match the results of the Java\n\u003e unicode normaliser, and in fact I can't even get Python to print the names\n\u003e of the characters past the embedded null. I'm curious where this normalised\n\u003e version came from.\n\u003e\n\u003e Given that \"pile of poo\" is not a character I think any sane user would\n\u003e put into a passphrase, I question the value of this test vector. NFC form\n\u003e is intended to collapse things like umlaut control characters onto their\n\u003e prior code point, but here we're feeding the algorithm what is basically\n\u003e garbage so I'm not totally surprised that different implementations appear\n\u003e to disagree on the outcome.\n\u003e\n\u003e Proposed action: we remove this test vector as it does not represent any\n\u003e real world usage of the spec, or if we desperately need to verify NFC\n\u003e normalisation I suggest using a different, more realistic test string, like\n\u003e Zürich, or something written in Thai.\n\u003e\n\u003e\n\u003e\n\u003e Test 3:\n\u003e\n\u003e    - Passphrase ϓ␀𐐀💩 (\\u03D2\\u0301\\u0000\\U00010400\\U0001F4A9; GREEK\n\u003e    UPSILON WITH HOOK \u003chttp://codepoints.net/U+03D2\u003e, COMBINING ACUTE\n\u003e    ACCENT \u003chttp://codepoints.net/U+0301\u003e, NULL\n\u003e    \u003chttp://codepoints.net/U+0000\u003e, DESERET CAPITAL LETTER LONG I\n\u003e    \u003chttp://codepoints.net/U+10400\u003e, PILE OF POO\n\u003e    \u003chttp://codepoints.net/U+1F4A9\u003e)\n\u003e    - Encrypted key:\n\u003e    6PRW5o9FLp4gJDDVqJQKJFTpMvdsSGJxMYHtHaQBF3ooa8mwD69bapcDQn\n\u003e    - Bitcoin Address: 16ktGzmfrurhbhi6JGqsMWf7TyqK9HNAeF\n\u003e    - Unencrypted private key (WIF):\n\u003e    5Jajm8eQ22H3pGWLEVCXyvND8dQZhiQhoLJNKjYXk9roUFTMSZ4\n\u003e    - *Note:* The non-standard UTF-8 characters in this passphrase should\n\u003e    be NFC normalized to result in a passphrase of0xcf9300f0909080f09f92a9 before\n\u003e    further processing\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Want fast and easy access to all the code in your enterprise? Index and\n\u003e search up to 200,000 lines of code with a free copy of Black Duck\n\u003e Code Sight - the same software that powers the world's largest code\n\u003e search on Ohloh, the Black Duck Open Hub! Try it now.\n\u003e http://p.sf.net/sfu/bds\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140715/6bed40c7/attachment.html\u003e"}