In this case, you will need to ask ffmpeg very closely why
they think linking to OpenSSL makes it "nonfree and
unredistributable", then run the result by your legal
department.
In particular, you need to pay attention to:
1. The SSLeay and OpenSSL license clause that you cannot
redistribute Open
Thanks for the information again.
If enabling OpenSSL usage on FFmpeg when configuring it, there is need
to enable also flag "non-free". This makes the configuration say:
"License: nonfree and unredistributable" and makes the legal guys bit
nervous here. When asking from #ffmpeg-devel about the re
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 consider
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 2
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
and OpenSSL" enough?
For ffmpeg I have
