From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X7OTL-0004BX-9m for bitcoin-development@lists.sourceforge.net; Wed, 16 Jul 2014 12:38:11 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.171 as permitted sender) client-ip=209.85.213.171; envelope-from=laanwj@gmail.com; helo=mail-ig0-f171.google.com; Received: from mail-ig0-f171.google.com ([209.85.213.171]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X7OTK-0004I5-JK for bitcoin-development@lists.sourceforge.net; Wed, 16 Jul 2014 12:38:11 +0000 Received: by mail-ig0-f171.google.com with SMTP id l13so4068494iga.10 for ; Wed, 16 Jul 2014 05:38:05 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.38.137 with SMTP id c9mr3520350ice.94.1405514285268; Wed, 16 Jul 2014 05:38:05 -0700 (PDT) Received: by 10.64.27.228 with HTTP; Wed, 16 Jul 2014 05:38:05 -0700 (PDT) In-Reply-To: References: Date: Wed, 16 Jul 2014 14:38:05 +0200 Message-ID: From: Wladimir To: Mike Hearn Content-Type: text/plain; charset=UTF-8 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 (laanwj[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: 1X7OTK-0004I5-JK Cc: Bitcoin Dev , Andreas Schildbach 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 12:38:11 -0000 On Wed, Jul 16, 2014 at 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. Forbidding control characters, at least anything < 32 makes a lot of sense to me. Carriage returns, linefeeds, formfeeds, null characters, I see no valid reason to allow them and lots of reasons they could cause havoc. PILE OF POO or GRINNING CAT FACE WITH SMILING EYES should be allowed in this day and age though. Wladimir