-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Licensing: AGPL and OpenSSL #3
Comments
Hi, |
This should be almost resolved since eeab357, which changed our License to LGPL and replaced MIRACL with Relic. One question remains: is OpenSSL compatible (enough) with the LGPL, or do we need to add an exemption for that case? (I am also no expert regarding software licenses.) |
OpenSSL was relicensed under the Apache License 2.0 version some time ago. That license is compatible to be used in (L)GPLv3 projects according to the Apache Software Foundation so this is not an issue if a version is used which used the Apache license and not the old OpenSSL license. |
The relicensing applies to the currently unreleased version 3.0.0 of OpenSSL (OpenSSL Blog). According to debian-legal:
So if we want that other people who want to use our code in GPL software together with OpenSSL, we would need that exemption (if I understood that correctly). |
Hi,
this project is licensed under GNU AGPL-3.0 and uses MIRACL (APGL) and OpenSSL (OpenSSL License) as dependencies. However, the OpenSSL License is listed as GPL-incompatible. So this is probably an issue.
(I am no expert regarding software licenses.)
The text was updated successfully, but these errors were encountered: