Re: OpenSSL licence compatibility

[Dmitriy Setrakyan]

The license looks very much like FreeBSD license [1] with additional
clauses. I doubt that ASF will be receptive to the additional restriction
clauses in the license.

However, I came across this OpenSSL blog [2] which states that they are
relicensing under Apache v.2.0 license. If you are willing to wait for this
process to complete, then you can use OpenSSL in Apache Ignite.

Also, I would advise looking into how other Apache projects worked around
this issue. I am sure we are not the first ones.

[1] - https://en.wikipedia.org/wiki/BSD_licenses
[2] - https://www.openssl.org/blog/blog/2017/03/22/license/

On Wed, Oct 11, 2017 at 6:36 AM, Igor Sapego  wrote:

> Hi guys,
>
> Lately I've been wondering about adding SSL to our ODBC driver.
> Of course I'm not going to write my own SSL implementation from
> the scratch, and going to use third-party library for that instead.
> OpenSSL library is the standard de-facto for implementation of SSL
> connectivity, but it uses its own OpenSSL license [1].
>
> So, the question is, is it compatible with the Apache 2.0 license? Can
> we use it?
>
> [1] - https://github.com/openssl/openssl/blob/master/LICENSE
>
> Best Regards,
> Igor
>

OpenSSL licence compatibility

[Igor Sapego]

Hi guys,

Lately I've been wondering about adding SSL to our ODBC driver.
Of course I'm not going to write my own SSL implementation from
the scratch, and going to use third-party library for that instead.
OpenSSL library is the standard de-facto for implementation of SSL
connectivity, but it uses its own OpenSSL license [1].

So, the question is, is it compatible with the Apache 2.0 license? Can
we use it?

[1] - https://github.com/openssl/openssl/blob/master/LICENSE

Best Regards,
Igor