This is something I would like to be contributed to OpenSSL. Sure, I'm talking about new engine and new files.
And I agree that using the same license as OpenSSL itself would be the best solution. But, if for some reasons licensing of it will be possible under Apache v2 only - what issues could it cause? On 10 December 2014 at 05:54, Salz, Rich <rs...@akamai.com> wrote: > > Let's imagine someone develop extension module to OpenSSL, and release > it under Apache v2 license. > > Do you see any possible issues with using this extension module as a > part of OpenSSL? > > Are you writing an extension that you are going to distribute, or is it > something you want to contribute to OpenSSL? > > You cannot change the license on openssl files, and any work derived from > them such as modifications to those source files, must have the same > license. And if you want to to contribute it to the project, it is easiest > for us if the license is the same. > > But if it is your own code, and you are distributing it, then you can do > anything you want :) > _______________________________________________ > openssl-dev mailing list > openssl-dev@openssl.org > https://mta.opensslfoundation.net/mailman/listinfo/openssl-dev >
_______________________________________________ openssl-dev mailing list openssl-dev@openssl.org https://mta.opensslfoundation.net/mailman/listinfo/openssl-dev