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 <mh.in.england@gmail.com>) id 1X74WW-0007e1-W8
	for bitcoin-development@lists.sourceforge.net;
	Tue, 15 Jul 2014 15:20:09 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.177 as permitted sender)
	client-ip=209.85.214.177; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f177.google.com; 
Received: from mail-ob0-f177.google.com ([209.85.214.177])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X74WV-0002KZ-6Q
	for bitcoin-development@lists.sourceforge.net;
	Tue, 15 Jul 2014 15:20:08 +0000
Received: by mail-ob0-f177.google.com with SMTP id wp18so5718426obc.8
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 15 Jul 2014 08:20:01 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.163.46 with SMTP id yf14mr15022499obb.40.1405437600362; 
	Tue, 15 Jul 2014 08:20:00 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Tue, 15 Jul 2014 08:20:00 -0700 (PDT)
In-Reply-To: <CAJHLa0MMaQU7Xu=vo0Z2C5h5M-Oa9_a648yDRrw6UR=r81X66w@mail.gmail.com>
References: <CANEZrP3ZzCBohXWZmZxE=ofP74Df4Hd-hCLH6jYn=JKbiqNQXA@mail.gmail.com>
	<CAObn+gfbH61kyv_ttT4vsQuNFRWLB5H3xaux7GQ0co82ucO_eA@mail.gmail.com>
	<CAJHLa0MMaQU7Xu=vo0Z2C5h5M-Oa9_a648yDRrw6UR=r81X66w@mail.gmail.com>
Date: Tue, 15 Jul 2014 17:20:00 +0200
X-Google-Sender-Auth: _nXWMGW6wUwHh08InST59-h4bCk
Message-ID: <CANEZrP1ee5wnekmoA-R+x30XB13bfhHcdyKS96BXac8POfPoNg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=e89a8f8389bfec7aba04fe3cf0ec
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1X74WV-0002KZ-6Q
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andreas Schildbach <andreas@schildbach.de>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2014 15:20:09 -0000

--e89a8f8389bfec7aba04fe3cf0ec
Content-Type: text/plain; charset=UTF-8

>
> Unicode guarantees that null-terminated strings still work.


UTF-8 guarantees that. Other encodings do not, you can have null bytes in
UTF-16 strings for example. Indeed most languages that use pascal-style
encodings internally allow null characters in strings, it's just not a good
idea to exploit that fact ...

--e89a8f8389bfec7aba04fe3cf0ec
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">Unicode guarantees that null-terminated strings =
still work. </blockquote>
<div><br></div><div>UTF-8 guarantees that. Other encodings do not, you can =
have null bytes in UTF-16 strings for example. Indeed most languages that u=
se pascal-style encodings internally allow null characters in strings, it&#=
39;s just not a good idea to exploit that fact ...</div>
</div></div></div>

--e89a8f8389bfec7aba04fe3cf0ec--