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
|
Return-Path: <arthur.chen@btcc.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id AA0C571
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 4 Jul 2016 01:23:18 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f65.google.com (mail-oi0-f65.google.com
[209.85.218.65])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 087641A7
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 4 Jul 2016 01:23:15 +0000 (UTC)
Received: by mail-oi0-f65.google.com with SMTP id w141so21132109oia.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 03 Jul 2016 18:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=btcc-com.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=kfLZKgU+ud7nYWm1oJmfkCekreeuBhNdyPFO7+xEn5Y=;
b=xJl+SouXG8Ddtk+Qx+gaaoTKymC/CqnB4+G0t7ZoSGatIwSoZ0tRjz7uwDrOq2Nb+I
bovzeXeT2+f3kw48qtOemW4O/V1UDOmpbM7KyTg3436Ouf1CqdLGX5zGtD1fK5t/EXYv
aZ9V8IjU259GKGglXRhtW5wpnpBVTj9LUDcz+/Ur0lLq1D4YnGDDIC0P7jqm7wTDetcL
50odSe+A+R29JyodpTcFdF5S+GSrCmkOrX20je0LMsbUSPD09nnBYiPqAES4/r/PMfdm
NABE+QqhGfJ+f3Ug36r/nismKT5CJWrIhCDzSW3bVdaWYu1pFIbYmJj0IiZUBbGL9r1z
FV3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=kfLZKgU+ud7nYWm1oJmfkCekreeuBhNdyPFO7+xEn5Y=;
b=P5FVme9BKvWUcX2OplvYz6lh7Q76ga8iGM29KNasQEYrP9R6rsgVZN/9gjHldiMxgn
U6eTqatbckCl4meA2cM3ztyzBTLnr5B5IjZiKK66vP815nxERh6JmPQWXcySTqgtxkDn
d6N/UTWVJvc0KouiwFWLRGKP7rmNrbSK1XTrDQzddbTK7I0uZ+TEWePzzO0GPQYY7XCy
qCaOBpg1FE8ig/vbH1mPw2ucE3NiPk4YZIp1Rb6QTbfobfb78FMAfZUVL23tvR84k04i
dtLocsx5I3GZXogH4mg51WzTYFAlxlJrp6aUGV1bjYSERkPvGi1xkaWJMKmay+MQULhE
sVrQ==
X-Gm-Message-State: ALyK8tL7p8yM1ViXU72F/5IRghbBuSnXGH9bagagBJCgucrJE3O4SNsMDtweDN16q6rsHyccyj2IsJKD7zXA8ZnL
X-Received: by 10.202.79.83 with SMTP id d80mr5418602oib.64.1467595395074;
Sun, 03 Jul 2016 18:23:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.87.140 with HTTP; Sun, 3 Jul 2016 18:23:14 -0700 (PDT)
In-Reply-To: <CADorodhC=UvQmiNVSd91dA57PyYydDH+uUUp_Aj5CsN-EG-e4g@mail.gmail.com>
References: <87h9cecad5.fsf@rustcorp.com.au>
<577224E8.6070307@jonasschnelli.ch>
<8760ssdd1u.fsf@rustcorp.com.au>
<CAEM=y+XKQZVz6UieB-nDy_C9xTmXiBB3-atuuZkxzmPoSVPOJw@mail.gmail.com>
<87oa6iavky.fsf@rustcorp.com.au>
<CADorodhC=UvQmiNVSd91dA57PyYydDH+uUUp_Aj5CsN-EG-e4g@mail.gmail.com>
From: Arthur Chen <arthur.chen@btcc.com>
Date: Mon, 4 Jul 2016 01:23:14 +0000
Message-ID: <CAP+0UNJ9mBCWCNf_kSo+4xJWjmO=eVmrrRi7=dD9_zmU2h3cDw@mail.gmail.com>
To: Zooko Wilcox <zooko@z.cash>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a113d7f1432a0900536c52ecf
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] BIP 151 use of HMAC_SHA512
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2016 01:23:18 -0000
--001a113d7f1432a0900536c52ecf
Content-Type: text/plain; charset=UTF-8
I strongly agree!
In crypto we should always follow well-studied open standard rather than
custom construction.
On Fri, Jul 1, 2016 at 10:42 PM, Zooko Wilcox via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> I haven't been able to find the beginning of this thread, so apologies
> if I've misunderstood what this is for, but it _sounds_ like we're
> re-inventing HKDF.
>
> I'd recommend reading the paper about HKDF. It stands out among crypto
> papers for having a nice clear justification for each of its design
> decisions, so you can see why they did it (very slightly) differently
> than the various constructions proposed up-thread.
>
> https://eprint.iacr.org/2010/264
>
> Also, of course, it is a great idea to re-use a standard
> (https://tools.ietf.org/html/rfc5869) and widely-understood crypto
> algorithm to reduce risk of both cryptographer errors and implementor
> errors.
>
> Of course, the cost of that is the you sometimes end up computing
> something that is a tiny bit more complicated or inefficient than a
> custom algorithm for our current use case. IMHO that's a cheap price
> to pay.
>
> Regards,
>
> Zooko
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
Xuesong (Arthur) Chen
Senior Principle Engineer
BlockChain Technologist
BTCC
--001a113d7f1432a0900536c52ecf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I strongly agree!<br></div>In crypto we should always=
follow well-studied open standard rather than custom construction.<br></di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Jul 1, =
2016 at 10:42 PM, Zooko Wilcox via bitcoin-dev <span dir=3D"ltr"><<a hre=
f=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoi=
n-dev@lists.linuxfoundation.org</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">I haven't been able to find the beginning of this thread,=
so apologies<br>
if I've misunderstood what this is for, but it _sounds_ like we're<=
br>
re-inventing HKDF.<br>
<br>
I'd recommend reading the paper about HKDF. It stands out among crypto<=
br>
papers for having a nice clear justification for each of its design<br>
decisions, so you can see why they did it (very slightly) differently<br>
than the various constructions proposed up-thread.<br>
<br>
<a href=3D"https://eprint.iacr.org/2010/264" rel=3D"noreferrer" target=3D"_=
blank">https://eprint.iacr.org/2010/264</a><br>
<br>
Also, of course, it is a great idea to re-use a standard<br>
(<a href=3D"https://tools.ietf.org/html/rfc5869" rel=3D"noreferrer" target=
=3D"_blank">https://tools.ietf.org/html/rfc5869</a>) and widely-understood =
crypto<br>
algorithm to reduce risk of both cryptographer errors and implementor<br>
errors.<br>
<br>
Of course, the cost of that is the you sometimes end up computing<br>
something that is a tiny bit more complicated or inefficient than a<br>
custom algorithm for our current use case. IMHO that's a cheap price<br=
>
to pay.<br>
<br>
Regards,<br>
<br>
Zooko<br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">Xu=
esong (Arthur) Chen<div>Senior Principle Engineer</div><div>BlockChain Tech=
nologist</div><div>BTCC</div></div></div>
</div>
--001a113d7f1432a0900536c52ecf--
|
