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
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
Return-Path: <cory@atlastechnologiesinc.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E266DB2B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Sep 2017 21:20:29 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com
[209.85.218.47])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2192A46B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Sep 2017 21:20:27 +0000 (UTC)
Received: by mail-oi0-f47.google.com with SMTP id n82so13710673oib.8
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Sep 2017 14:20:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=coryfields-com.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=5wMAkKgJBBdmusX2r5iaqSzsTs4LTWBhhZZspXkJs9s=;
b=BaDIcUmHA1RGOfWBhZLOdkmjejBd18aWUzMt4GKhqiEkYVSlfcw14ik7eEFCRZMH+O
kZm+W0cUn3k49jYKjEhyN/SOXoaYhu1UxiD1x4cnUP/7w7k7juvJg/daW/UnF2lL4MgH
S/VUR9SpFa15o5fLa4CDWxYxWMwz9+N4zF91qYnb7qWByXu2G8XJQCp/j5IrACya6ep5
3pAB0VuoFRLQUGMV7kno3NmurOPGrwvtLK0a66riBuRQpvbtnIjgFvpRBNDGwyflVZBC
QFockwlwOkshW/FbYMkKE/AwJzRqh9n5morXxrXIgd1j+BPHNSaBFq7Irj+o+ymAjvTi
fEAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=5wMAkKgJBBdmusX2r5iaqSzsTs4LTWBhhZZspXkJs9s=;
b=OvS9CN5VRKsZ26857nW6x+IINrG8j0dnBI+KHY3K2Ik2Du7jWZw9T66chNwnelzW07
EJ3BVPuefvN7Ch+mPrbdUPhvSHYH+cRuEjLfmWNPfi+qRbL+TZpw16uMgHnClalRPqY7
hyyo1m+Fb0pFdvyao5Mrrlc05Dmsy1UQEt66T+lx2fx74ktQDO8l7DH4+D482EDfbrk3
ZNbNurnWA6uUpQteTdImHofQ5l5tFz8kuJQaD/OqYhrf+/ZjOw1RFmJJiIseg/u+9FSR
D2bZmptHOAV/V0qzHgm78U2YFItryRljIhBAOHjE9xXVbgB1ugiEznKAtEkx3PASiJIg
hspA==
X-Gm-Message-State: AMCzsaVHCDi8otxcRM5AEkJ/2VVZPgylehc0zI2JAJjMqw9FT6pxXPga
7F5ZPoVZNqXYIksxjoVgszMi1k5Pj0wWzuR7y7Mmxg==
X-Google-Smtp-Source: AOwi7QB2to9Z+6SmLv3jr7wK2IvyySEchyCg8h1thTDNcaRLd4RjlCSVx797iaWMGNTfZN8zeZp6s4cYlaNXupPuZr4=
X-Received: by 10.157.11.199 with SMTP id 65mr280248oth.19.1506547227187; Wed,
27 Sep 2017 14:20:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.162.38 with HTTP; Wed, 27 Sep 2017 14:20:26 -0700 (PDT)
In-Reply-To: <CAE3EOfjD5aW05DTOF1yC3R3Jf4w4m+kajT8rs4faH-n+WZpuog@mail.gmail.com>
References: <E682AA2FC88ADD4589420BFC6BE3A92141FC460F@SANDMBX01v.piper.root.local>
<CAE3EOfjD5aW05DTOF1yC3R3Jf4w4m+kajT8rs4faH-n+WZpuog@mail.gmail.com>
From: Cory Fields <lists@coryfields.com>
Date: Wed, 27 Sep 2017 17:20:26 -0400
Message-ID: <CAApLimhdKtQnx4CPwRsiB0LiOiWAQxJds3MhumXRqSpfMnEMnQ@mail.gmail.com>
To: Omar Shibli <omarshib@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="001a113543165074fb055a325c36"
X-Spam-Status: No, score=0.5 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=disabled
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: "Radcliffe, Mark" <Mark.Radcliffe@dlapiper.com>, "Roay,
Leslie" <Leslie.Roay@dlapiper.com>
Subject: Re: [bitcoin-dev] Bitcoin Assistance
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: Wed, 27 Sep 2017 21:20:30 -0000
--001a113543165074fb055a325c36
Content-Type: text/plain; charset="UTF-8"
Hi Mark
Thank you very much for posting the findings. I took a look through our
repository and I think I can provide a bit of context.
I'll go through each one, annotating what I've found.
> Apache License 2.0
This is used by a few java files in the libsecp256k1 project. That library
(which lives here: https://github.com/bitcoin-core/secp256k1) is a
sub-module created and maintained by Bitcoin Core developers. The files in
question are bindings that allow other applications to use libsecp256k1
from Java. Bitcoin Core makes no use of them.
> Boost Software License 1.0
This comes from tinyformat.h. Bitcoin Core indeed uses it.
> BSD 2-clause "Simplified" License
I'm unable to find any 2-clause BSD licensed files.
> BSD 3-clause "New" or "Revised" License
This comes from leveldb, which is database software used by Bitcoin Core.
Because database software version inconsistencies can cause accidental
forks (this actually happened in 2013), we include these files in our
repository and use them rather than linking to arbitrary versions at
runtime.
There are a few non-upstream files we use in our leveldb tree to provide
windows support. Quoting from src/leveldb/util/env_win.cc:
This file contains source that originates from:
http://code.google.com/p/leveldbwin/source/browse/trunk/win32_impl_src/env_win32.h
http://code.google.com/p/leveldbwin/source/browse/trunk/win32_impl_src/port_win32.cc
Those files don't have any explicit license headers but the
project (http://code.google.com/p/leveldbwin/) lists the 'New BSD License'
> Creative Commons Attribution Share Alike 3.0
I didn't manage to find any CC-licensed files. The match probably comes
from our gui svg icons, which contain an xml tag with a link to
creativecommons.org. This seems to be the default behavior of inkscape,
which was used to create those icons. Any icons that we have not created
ourselves are listed in contrib/debian/copyright (they're all expat/public
domain).
> Expat License
See MIT.
> GNU General Public License v2.0 or later
The debian folder, which holds the files used to create debian/ubuntu
packages is licensed gplv2+. These are packaging resources only,
unnecessary for use of the code.
Additionally, some gplv2 m4 macros are used to bootstrap the code that is
used to build the Bitcoin code. These contain the additional exception:
As a special exception, the respective Autoconf Macro's copyright owner
gives unlimited permission to copy, distribute and modify the configure
scripts that are the output of Autoconf when processing the Macro. You
need not follow the terms of the GNU General Public License when using
or distributing such scripts, even though portions of the text of the
Macro appear in them. The GNU General Public License (GPL) does govern
all other use of the material that constitutes the Autoconf Macro.
> GNU General Public License v3.0 or later
The macdeploy script, useful for creating DMG files for macOS is gplv3. It
is not necessary for any other platform, and is only used during the build
process. Additionally, it is not the only way to create DMG files (apple's
native tools can be used as well).
Additionally, config.guess and config.sub are gplv3 scripts used to build
our buildsystem.
> GNU Lesser General Public License v2.1 or later
authproxy.py, A python script used in our test suite is licensed lgpl
v2.1+. It is only necessary for running optional tests during development.
> License for A fast alternative to the modulo reduction
This references a comment cuckoocache.h. No code from the site is used. The
link to the site was added after the code, as the site provides a helpful
explanation for the technique used.
> License for atomic by Timm Kosse
Another m4 file. As explained with the others above, this is a macro which
builds code which builds code. It is used in the build process only.
> MIT License
The primary and default license for all contributions.
> Public Domain
> University of Illinois/NCSA Open Source License
clang-format-diff.py, a python script optionally used by developers to
clean up code changes.
tl;dr: Best I can tell, all source files that comprise Bitcoin Core
binaries are licensed (excluding the public domain ones) as MIT, BSD, or
Boost.
It's also worth repeating Omar's point that many of the files in the
Bitcoin Core repository are used for optional programs/libraries. None of
the artwork, for example, is needed for the primary bitcoin daemon.
Hope that helps!
Regards,
Cory
--001a113543165074fb055a325c36
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>Hi Mark<br><br>Thank you very much for post=
ing the findings. I took a look through our repository and I think I can pr=
ovide a bit of context.<br><br>I'll go through each one, annotating wha=
t I've found.<br><br>> Apache License 2.0<br><br>This is used by a f=
ew java files in the libsecp256k1 project. That library (which lives here: =
<a href=3D"https://github.com/bitcoin-core/secp256k1">https://github.com/bi=
tcoin-core/secp256k1</a>) is a sub-module created and maintained by Bitcoin=
Core developers. The files in question are bindings that allow other appli=
cations to use libsecp256k1 from Java. Bitcoin Core makes no use of them.<b=
r><br>> Boost Software License 1.0<br><br>This comes from tinyformat.h. =
Bitcoin Core indeed uses it.<br><br>> BSD 2-clause "Simplified"=
; License<br><br>I'm unable to find any 2-clause BSD licensed files.<br=
><br>> BSD 3-clause "New" or "Revised" License<br><b=
r>This comes from leveldb, which is database software used by Bitcoin Core.=
Because database software version inconsistencies can cause accidental for=
ks (this actually happened in 2013), we include these files in our reposito=
ry and use them rather than linking to arbitrary versions at runtime.<br><b=
r>There are a few non-upstream files we use in our leveldb tree to provide =
windows support. Quoting from src/leveldb/util/env_win.cc:<br>=C2=A0 This f=
ile contains source that originates from:<br>=C2=A0 <a href=3D"http://code.=
google.com/p/leveldbwin/source/browse/trunk/win32_impl_src/env_win32.h">htt=
p://code.google.com/p/leveldbwin/source/browse/trunk/win32_impl_src/env_win=
32.h</a><br>=C2=A0 <a href=3D"http://code.google.com/p/leveldbwin/source/br=
owse/trunk/win32_impl_src/port_win32.cc">http://code.google.com/p/leveldbwi=
n/source/browse/trunk/win32_impl_src/port_win32.cc</a><br>=C2=A0 Those file=
s don't have any explicit license headers but the <br>=C2=A0 project (<=
a href=3D"http://code.google.com/p/leveldbwin/">http://code.google.com/p/le=
veldbwin/</a>) lists the 'New BSD License'<br><br>> Creative Com=
mons Attribution Share Alike 3.0<br><br>I didn't manage to find any CC-=
licensed files. The match probably comes from our gui svg icons, which cont=
ain an xml tag with a link to <a href=3D"http://creativecommons.org">creati=
vecommons.org</a>. This seems to be the default behavior of inkscape, which=
was used to create those icons. Any icons that we have not created ourselv=
es are listed in contrib/debian/copyright (they're all expat/public dom=
ain).<br><br>> Expat License<br><br>See MIT.<br><br>> GNU General Pub=
lic License v2.0 or later<br><br>The debian folder, which holds the files u=
sed to create debian/ubuntu packages is licensed gplv2+. These are packagin=
g resources only, unnecessary for use of the code.<br><br>Additionally, som=
e gplv2 m4 macros are used to bootstrap the code that is used to build the =
Bitcoin code. These contain the additional exception:<br><br>=C2=A0=C2=A0 A=
s a special exception, the respective Autoconf Macro's copyright owner<=
br>=C2=A0=C2=A0 gives unlimited permission to copy, distribute and modify t=
he configure<br>=C2=A0=C2=A0 scripts that are the output of Autoconf when p=
rocessing the Macro. You<br>=C2=A0=C2=A0 need not follow the terms of the G=
NU General Public License when using<br>=C2=A0=C2=A0 or distributing such s=
cripts, even though portions of the text of the<br>=C2=A0=C2=A0 Macro appea=
r in them. The GNU General Public License (GPL) does govern<br>=C2=A0=C2=A0=
all other use of the material that constitutes the Autoconf Macro.<br><br>=
> GNU General Public License v3.0 or later<br><br>The macdeploy script, =
useful for creating DMG files for macOS is gplv3. It is not necessary for a=
ny other platform, and is only used during the build process. Additionally,=
it is not the only way to create DMG files (apple's native tools can b=
e used as well).<br><br>Additionally, config.guess and config.sub are gplv3=
scripts used to build our buildsystem.<br><br>> GNU Lesser General Publ=
ic License v2.1 or later<br><br>authproxy.py, A python script used in our t=
est suite is licensed lgpl v2.1+. It is only necessary for running optional=
tests during development.<br><br>> License for A fast alternative to th=
e modulo reduction<br><br>This references a comment cuckoocache.h. No code =
from the site is used. The link to the site was added after the code, as th=
e site provides a helpful explanation for the technique used.<br><br>> L=
icense for atomic by Timm Kosse<br><br>Another m4 file. As explained with t=
he others above, this is a macro which builds code which builds code. It is=
used in the build process only.<br><br>> MIT License<br><br>The primary=
and default license for all contributions.<br><br>> Public Domain<br><b=
r>> University of Illinois/NCSA Open Source License<br><br>clang-format-=
diff.py, a python script optionally used by developers to clean up code cha=
nges.<br><br>tl;dr: Best I can tell, all source files that comprise Bitcoin=
Core binaries are licensed (excluding the public domain ones) as MIT, BSD,=
or Boost.<br><br>It's also worth repeating Omar's point that many =
of the files in the Bitcoin Core repository are used for optional programs/=
libraries. None of the artwork, for example, is needed for the primary bitc=
oin daemon.<br><br></div>Hope that helps!<br><br></div>Regards,<br></div>Co=
ry<br></div>
--001a113543165074fb055a325c36--
|
