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. > > -- > Jakob Bohm, CIO, partner, WiseMo A/S. http://www.wisemo.com > Transformervej 29, 2730 Herlev, Denmark. direct: +45 31 13 16 10 > <call:+4531131610> > This message is only for its intended recipient, delete if misaddressed. > 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 -- -Antti ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
