📅 Original date posted:2014-07-15
📝 Original message:I think generally control-characters (such as \u0000) should be
disallowed in passphrases. (Even the use of whitespaces is very
questionable.)
I'm ok with allowing pile-of-poo's. On mobile phones there is keyboards
just containing emoticons -- why not allow those? Assuming NFC works of
course.
On 07/15/2014 03:07 PM, Eric Winer wrote:
> I don't know for sure if the test vector is correct NFC form. But for
> what it's worth, the Pile of Poo character is pretty easily accessible
> on the iPhone and Android keyboards, and in this string it's already in
> NFC form (f09f92a9 in the test result). I've certainly seen it in
> usernames around the internet, and wouldn't be surprised to see it in
> passphrases entered on smartphones, especially if the author of a
> BIP38-compatible app includes a (possibly ill-advised) suggestion to
> have your passphrase "include special characters".
>
> I haven't seen the NULL character on any smartphone keyboards, though -
> I assume the iOS and Android developers had the foresight to know how
> much havoc that would wreak on systems assuming null-terminated strings.
> It seems unlikely that NULL would be in a real-world passphrase entered
> by a sane user.
>
>
> On Tue, Jul 15, 2014 at 8:03 AM, Mike Hearn <mike at plan99.net
> <mailto:mike at plan99.net>> wrote:
>
> [+cc aaron]
>
> We recently added an implementation of BIP 38 (password protected
> private keys) to bitcoinj. It came to my attention that the third
> test vector may be broken. It gives a hex version of what the NFC
> normalised version of the input string should be, but this does not
> match the results of the Java unicode normaliser, and in fact I
> can't even get Python to print the names of the characters past the
> embedded null. I'm curious where this normalised version came from.
>
> Given that "pile of poo" is not a character I think any sane user
> would put into a passphrase, I question the value of this test
> vector. NFC form is intended to collapse things like umlaut control
> characters onto their prior code point, but here we're feeding the
> algorithm what is basically garbage so I'm not totally surprised
> that different implementations appear to disagree on the outcome.
>
> Proposed action: we remove this test vector as it does not represent
> any real world usage of the spec, or if we desperately need to
> verify NFC normalisation I suggest using a different, more realistic
> test string, like Zürich, or something written in Thai.
>
>
>
> Test 3:
>
> * Passphrase ϓ␀𐐀💩 (\u03D2\u0301\u0000\U00010400\U0001F4A9; GREEK
> UPSILON WITH HOOK <http://codepoints.net/U+03D2>;, COMBINING
> ACUTE ACCENT <http://codepoints.net/U+0301>;, NULL
> <http://codepoints.net/U+0000>;, DESERET CAPITAL LETTER LONG I
> <http://codepoints.net/U+10400>;, PILE OF POO
> <http://codepoints.net/U+1F4A9>;)
> * Encrypted key:
> 6PRW5o9FLp4gJDDVqJQKJFTpMvdsSGJxMYHtHaQBF3ooa8mwD69bapcDQn
> * Bitcoin Address: 16ktGzmfrurhbhi6JGqsMWf7TyqK9HNAeF
> * Unencrypted private key (WIF):
> 5Jajm8eQ22H3pGWLEVCXyvND8dQZhiQhoLJNKjYXk9roUFTMSZ4
> * /Note:/ The non-standard UTF-8 characters in this passphrase
> should be NFC normalized to result in a passphrase
> of0xcf9300f0909080f09f92a9 before further processing
>
>
>
>
> ------------------------------------------------------------------------------
> 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 at lists.sourceforge.net
> <mailto:Bitcoin-development at 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:23:49
in reply to nevent1q…nsty
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:23:49Event JSON
{
"id": "43ed14a8651d543cc27d7f10355454c20202a175f473aa118a07579e48204003",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686151429,
"kind": 1,
"tags": [
[
"e",
"60726055f5690f49a0698605fd9e440f1a7b0fbf2e702b7f0382a84f86474ca9",
"",
"root"
],
[
"e",
"b74ef9eac3e364a7ac84a02805403004c230f3b134c46f0eadc78756ffa91d71",
"",
"reply"
],
[
"p",
"6027530bb57e40433157353aa0d1f514caa4d54031dd8671860babdabbc7e11f"
]
],
"content": "📅 Original date posted:2014-07-15\n📝 Original message:I think generally control-characters (such as \\u0000) should be\ndisallowed in passphrases. (Even the use of whitespaces is very\nquestionable.)\n\nI'm ok with allowing pile-of-poo's. On mobile phones there is keyboards\njust containing emoticons -- why not allow those? Assuming NFC works of\ncourse.\n\n\nOn 07/15/2014 03:07 PM, Eric Winer wrote:\n\u003e I don't know for sure if the test vector is correct NFC form. But for\n\u003e what it's worth, the Pile of Poo character is pretty easily accessible\n\u003e on the iPhone and Android keyboards, and in this string it's already in\n\u003e NFC form (f09f92a9 in the test result). I've certainly seen it in\n\u003e usernames around the internet, and wouldn't be surprised to see it in\n\u003e passphrases entered on smartphones, especially if the author of a\n\u003e BIP38-compatible app includes a (possibly ill-advised) suggestion to\n\u003e have your passphrase \"include special characters\".\n\u003e \n\u003e I haven't seen the NULL character on any smartphone keyboards, though -\n\u003e I assume the iOS and Android developers had the foresight to know how\n\u003e much havoc that would wreak on systems assuming null-terminated strings.\n\u003e It seems unlikely that NULL would be in a real-world passphrase entered\n\u003e by a sane user.\n\u003e \n\u003e \n\u003e On Tue, Jul 15, 2014 at 8:03 AM, Mike Hearn \u003cmike at plan99.net\n\u003e \u003cmailto:mike at plan99.net\u003e\u003e wrote:\n\u003e \n\u003e [+cc aaron]\n\u003e \n\u003e We recently added an implementation of BIP 38 (password protected\n\u003e private keys) to bitcoinj. It came to my attention that the third\n\u003e test vector may be broken. It gives a hex version of what the NFC\n\u003e normalised version of the input string should be, but this does not\n\u003e match the results of the Java unicode normaliser, and in fact I\n\u003e can't even get Python to print the names of the characters past the\n\u003e embedded null. I'm curious where this normalised version came from.\n\u003e \n\u003e Given that \"pile of poo\" is not a character I think any sane user\n\u003e would put into a passphrase, I question the value of this test\n\u003e vector. NFC form is intended to collapse things like umlaut control\n\u003e characters onto their prior code point, but here we're feeding the\n\u003e algorithm what is basically garbage so I'm not totally surprised\n\u003e that different implementations appear to disagree on the outcome.\n\u003e \n\u003e Proposed action: we remove this test vector as it does not represent\n\u003e any real world usage of the spec, or if we desperately need to\n\u003e verify NFC normalisation I suggest using a different, more realistic\n\u003e test string, like 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\n\u003e ACUTE 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\n\u003e should be NFC normalized to result in a passphrase\n\u003e of0xcf9300f0909080f09f92a9 before further processing\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 \u003cmailto:Bitcoin-development at lists.sourceforge.net\u003e\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\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 \n\u003e \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",
"sig": "4b7e095e86c91b16b0bb32d759ff467d26c089138eab48bb3e42f4359af8824a6a9648d720fda80bf4f5fd81fc9b87402c8ebdfec87447846436a2d9490a32c2"
}