| 1 |
License Mixing with apps, libcurl and Third Party Libraries |
| 2 |
=========================================================== |
| 3 |
|
| 4 |
libcurl can be built to use a fair amount of various third party libraries, |
| 5 |
libraries that are written and provided by other parties that are distributed |
| 6 |
using their own licenses. Even libcurl itself contains code that may cause |
| 7 |
problems to some. This document attempts to describe what licenses libcurl and |
| 8 |
the other libraries use and what possible dilemmas linking and mixing them all |
| 9 |
can lead to for end users. |
| 10 |
|
| 11 |
I am not a lawyer and this is not legal advice! |
| 12 |
|
| 13 |
One common dilemma is that GPL[1]-licensed code is not allowed to be linked |
| 14 |
with code licensed under the Original BSD license (with the announcement |
| 15 |
clause, unless there's a specified exception in the GPL-licensed module). You |
| 16 |
may still build your own copies that use them all, but distributing them as |
| 17 |
binaries would be to violate the GPL license - unless you accompany your |
| 18 |
license with an exception[2]. This particular problem was addressed when the |
| 19 |
Modified BSD license was created, which does not have the annoncement clause |
| 20 |
that collides with GPL. |
| 21 |
|
| 22 |
libcurl http://curl.haxx.se/docs/copyright.html |
| 23 |
|
| 24 |
Uses an MIT (or Modified BSD)-style license that is as liberal as |
| 25 |
possible. Some of the source files that deal with KRB4 have Original |
| 26 |
BSD-style announce-clause licenses. You may not distribute binaries |
| 27 |
with krb4-enabled libcurl that also link with GPL-licensed code! |
| 28 |
|
| 29 |
OpenSSL http://www.openssl.org/source/license.html |
| 30 |
|
| 31 |
Uses an Original BSD-style license with an announement clause that |
| 32 |
makes it "incompatible" with GPL. You are not allowed to ship binaries |
| 33 |
that link with OpenSSL that includes GPL code (unless that specific |
| 34 |
GPL code includes an exception for OpenSSL - a habit that is growing |
| 35 |
more and more common). If OpenSSL's licensing is a problem for you, |
| 36 |
consider using GnuTLS instead. |
| 37 |
|
| 38 |
GnuTLS http://www.gnutls.org/ |
| 39 |
|
| 40 |
Uses the LGPL[3] license. If this is a problem for you, consider using |
| 41 |
OpenSSL instead. Also note that GnuTLS itself depends on and uses |
| 42 |
other libs (libgcrypt and libgpg-error) and they too are LGPL- or |
| 43 |
GPL-licensed. |
| 44 |
|
| 45 |
c-ares http://daniel.haxx.se/projects/c-ares/license.html |
| 46 |
|
| 47 |
Uses an MIT license that is very liberal and imposes no restrictions |
| 48 |
on any other library or part you may link with. |
| 49 |
|
| 50 |
zlib http://www.gzip.org/zlib/zlib_license.html |
| 51 |
|
| 52 |
Uses an MIT-style license that shouldn't collide with any other |
| 53 |
library. |
| 54 |
|
| 55 |
krb4 |
| 56 |
|
| 57 |
While nothing in particular says that a Kerberos4 library must use any |
| 58 |
particular license, the one I've tried and used successfully so far |
| 59 |
(kth-krb4) is Original BSD-licensed with the announcement clause. Some |
| 60 |
of the code in libcurl that is written to deal with Kerberos4 likewise |
| 61 |
have such a license. |
| 62 |
|
| 63 |
GSSAPI |
| 64 |
|
| 65 |
While nothing in particular says that a GSS/Kerberos5 library must use |
| 66 |
any particular license, the one I've used (Heimdal) is Original BSD- |
| 67 |
licensed with the announcement clause. |
| 68 |
|
| 69 |
fbopenssl |
| 70 |
|
| 71 |
Unclear license. Based on its name, I assume that it uses the OpenSSL |
| 72 |
license and thus shares the same issues as described for OpenSSL |
| 73 |
above. |
| 74 |
|
| 75 |
libidn http://www.gnu.org/licenses/lgpl.html |
| 76 |
|
| 77 |
Uses the GNU Lesser General Public License. LGPL is a variation of GPL |
| 78 |
with slightly less aggressive "copyleft". This license requires more |
| 79 |
requirements to be met when distributing binaries, see the license for |
| 80 |
details. Also note that if you distribute a binary that includes this |
| 81 |
library, you must also include the full LGPL license text. Please |
| 82 |
properly point out what parts of the distributed package that the |
| 83 |
license addresses. |
| 84 |
|
| 85 |
OpenLDAP http://www.openldap.org/software/release/license.html |
| 86 |
|
| 87 |
Uses a Modified BSD-style license. Since libcurl uses OpenLDAP as a |
| 88 |
shared library only, I have not heard of anyone that ships OpenLDAP |
| 89 |
linked with libcurl in an app. |
| 90 |
|
| 91 |
|
| 92 |
[1] = GPL - GNU General Public License: http://www.gnu.org/licenses/gpl.html |
| 93 |
[2] = http://www.fsf.org/licenses/gpl-faq.html#GPLIncompatibleLibs details on |
| 94 |
how to write such an exception to the GPL |
| 95 |
[3] = LGPL - GNU Lesser General Public License: |
| 96 |
http://www.gnu.org/licenses/lgpl.html |