Since there is misinformation on this floating around, even in the
openssl.org FAQ itself, here are the GPL+OpenSSL, and LGPL+OpenSSL
rules:
1. Code under LGPL (any version) can link to OpenSSL with each of
part (OpenSSL and the code under LGPL) remaining under its own
license. LGPL considers OpenSSL as "a program that uses the
library". This is why there is no problem linking OpenSSL to
GNU libc (which is LGPL and/or GPL+general library exception).
2. Code under GPL plus a special exception (from the GPL) to allow
linking to OpenSSL or other similarly licensed libraries, can
link against OpenSSL. Note that all the copyright holders on
the specific code under GPL must agree to add the exception, and
they cannot cut/paste code from other GPL projects that don't
include the exception.
3. Code under GPL version 2 can be linked to OpenSSL only if both
the following are true:
A. OpenSSL is included "with the kernel, compiler or other major
OS component"
B. The GPL code is NOT included "with the kernel, compiler or
other major OS component"
This combination triggers the GPL rule about linking GPL to
non-open-source libraries that might be part of an OS, such as
the built in libraries on Windows or AIX.
The OpenSSL FAQ has (or used to) have this backwards.
4. Code under GPL version 3 may have other options under some
clauses of the GPL version 3 license, I have not studied this
closely enough to know this.
(I am not a lawyer and this is not legal advice, you should read
the original license documents carefully, then ask a real lawyer
if you don't understand them completely).
On 5/24/2012 4:31 PM, Antti Peuhkurinen wrote:
Thanks!
Binary we include from FFmpeg uses OpenSSL's .so and so FFmpeg can't
be "just" LGPL anymore. Seems that many programs having this case list
FFmpeg with LGPL license without any clause and list OpenSSL
separately with OpenSSL's license. Might be that we do the same :)
-Antti
On Wed, May 23, 2012 at 6:22 PM, Jakob Bohm<jb-open...@wisemo.com> wrote:
On 5/23/2012 4:47 PM, Antti Peuhkurinen wrote:
Hi!
I am using both FFmpeg and OpenSSL in my project (FFmpeg uses
openssl's .so on Android platform). Which kind of license text should
be put to marketing etc. material? Is "This software is using FFmpeg
<LINK> and OpenSSL<LINK>" enough?
For ffmpeg I have no idea.
For OpenSSL, the OpenSSL license contains 3 very specific sentences
that you need to copy verbatim, even though they all sound similar.
You typically need to use all 3 statements. No link is required I
think, though in our product we do link to openssl.org. We also
duplicate the full two-part license text in an appendix to the
form of the acknowledgements included with the product, as that
seems to be required too.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
