1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1W5YJ8-00051U-HX
for bitcoin-development@lists.sourceforge.net;
Tue, 21 Jan 2014 10:11:46 +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 1W5YJ7-0001Ue-Ey
for bitcoin-development@lists.sourceforge.net;
Tue, 21 Jan 2014 10:11:46 +0000
Received: by mail-ob0-f177.google.com with SMTP id wp18so6458614obc.36
for <bitcoin-development@lists.sourceforge.net>;
Tue, 21 Jan 2014 02:11:40 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.16.230 with SMTP id j6mr6027626oed.47.1390299099913; Tue,
21 Jan 2014 02:11:39 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.99.112 with HTTP; Tue, 21 Jan 2014 02:11:39 -0800 (PST)
In-Reply-To: <CAKm8k+0xa5-b=gjfZmH760TbYaQUVf5fGvVK9Jx5jwBGAvcX4g@mail.gmail.com>
References: <mailman.423274.1390277261.21953.bitcoin-development@lists.sourceforge.net>
<300D31FC-FB89-4386-8DD9-F5FA792D0B40@bitsofproof.com>
<CAKm8k+0xa5-b=gjfZmH760TbYaQUVf5fGvVK9Jx5jwBGAvcX4g@mail.gmail.com>
Date: Tue, 21 Jan 2014 10:11:39 +0000
X-Google-Sender-Auth: _vpFjLUwi4yEgyzcSGxJV0zivo4
Message-ID: <CANEZrP0Us2+2_ThvRpy4hvny9i8q8avud5gteXzyJB_C1+m7qQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gary Rowe <g.rowe@froot.co.uk>
Content-Type: multipart/alternative; boundary=e89a8f503bb2fb6b5f04f0783bc8
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: 1W5YJ7-0001Ue-Ey
Cc: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP0039: Final call
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, 21 Jan 2014 10:11:46 -0000
--e89a8f503bb2fb6b5f04f0783bc8
Content-Type: text/plain; charset=UTF-8
We should just perform Unicode canonicalization before any text hits the
crypto code. There are algorithms that automatically resolve such issues.
Although with an English wordlist it would seem to make no difference
anyway.
On Tue, Jan 21, 2014 at 10:01 AM, Gary Rowe <g.rowe@froot.co.uk> wrote:
> MultiBit here.
>
> >At least Trezor and bitcoinj (Multibit) seems to be going in this way,
> >which is 100% of clients which expressed interest in bip39 :-).
> >
> >slush
>
> We'll be using the BIP39 implementation present in Bitcoinj as slush says.
>
> >Proper Unicode handling is a serious issue however. You don't want
> >someone to move from one input method / machine to another and
> >suddenly find that their coins are inaccessible, because of an issue
> >of decomposed vs. compatibility forms or whatever.
>
> We generate the word list internally (12,18,24) and confirm it is entered
> correctly through a retyping operation. This will allow us to detect
> character encoding transpositions (e.g. u0032 vs u00a0) and alert the user
> before it becomes an issue.
>
> While English is the language of the first word list to be implemented, we
> would definitely integrate alternative non-English word lists to make life
> easier for the global community. In general the approach would be for the
> user to select their language (implying a locale) and then the word list to
> be selected from that locale if available with a fallback to English. This
> follows the same approach as resource bundles in Java.
>
>
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--e89a8f503bb2fb6b5f04f0783bc8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">We should just perform Unicode canonicalization before any=
text hits the crypto code. =C2=A0There are algorithms that automatically r=
esolve such issues. Although with an English wordlist it would seem to make=
no difference anyway.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Jan 2=
1, 2014 at 10:01 AM, Gary Rowe <span dir=3D"ltr"><<a href=3D"mailto:g.ro=
we@froot.co.uk" target=3D"_blank">g.rowe@froot.co.uk</a>></span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">MultiBit here.=C2=A0<div><div class=3D"im"><br>>At leas=
t Trezor and bitcoinj (Multibit) seems to be going in this way,<br>>whic=
h is 100% of clients which expressed interest in bip39 :-).<br>><br>>=
slush<br>
<br></div><div class=3D"gmail_extra">
We'll be using the BIP39 implementation present in Bitcoinj as slush sa=
ys.=C2=A0</div><div class=3D"im"><div class=3D"gmail_extra"><br></div><div =
class=3D"gmail_extra"><span style=3D"font-family:arial,sans-serif;font-size=
:12.800000190734863px">>Proper Unicode handling is a serious issue howev=
er. You don't want</span><br style=3D"font-family:arial,sans-serif;font=
-size:12.800000190734863px">
<span style=3D"font-family:arial,sans-serif;font-size:12.800000190734863px"=
>>someone to move from one input method / machine to another and</span><=
br style=3D"font-family:arial,sans-serif;font-size:12.800000190734863px"><s=
pan style=3D"font-family:arial,sans-serif;font-size:12.800000190734863px">&=
gt;suddenly find that their coins are inaccessible, because of an issue</sp=
an><br style=3D"font-family:arial,sans-serif;font-size:12.800000190734863px=
">
<span style=3D"font-family:arial,sans-serif;font-size:12.800000190734863px"=
>>of decomposed vs. compatibility forms or whatever.</span><br></div><di=
v class=3D"gmail_extra"><span style=3D"font-family:arial,sans-serif;font-si=
ze:12.800000190734863px"><br>
</span></div></div><div class=3D"gmail_extra">We generate the word list int=
ernally (12,18,24) and confirm it is entered correctly through a retyping o=
peration. This will allow us to detect character encoding transpositions (e=
.g. u0032 vs u00a0) and alert the user before it becomes an issue.<br>
</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">While=
English is the language of the first word list to be implemented, we would=
definitely integrate alternative non-English word lists to make life easie=
r for the global community. In general the approach would be for the user t=
o select their language (implying a locale) and then the word list to be se=
lected from that locale if available with a fallback to English. This follo=
ws the same approach as resource bundles in Java.</div>
</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br><=
/div></div>
<br>-----------------------------------------------------------------------=
-------<br>
CenturyLink Cloud: The Leader in Enterprise Cloud Services.<br>
Learn Why More Businesses Are Choosing CenturyLink Cloud For<br>
Critical Workloads, Development Environments & Everything In Between.<b=
r>
Get a Quote or Start a Free Trial Today.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D119420431&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D119420431&iu=3D/4140/ostg.clktrk</a><br>__________________=
_____________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>
--e89a8f503bb2fb6b5f04f0783bc8--
|
