4 ms·
Summary: - Next version will be 3.0.0 which is major.minor.patch (v2 was used for OpenSSL FIPS). The letter will not be used anymore. - Next version will be u
by lucb1e 8y ago
Summary:
- Next version will be 3.0.0 which is major.minor.patch (v2 was used for OpenSSL FIPS). The letter will not be used anymore.
- Next version will be under the Apache 2.0 license instead of "Apache License 1.0 and 4-clause BSD License"[1].
The main difference between Apache License version 1 and 2 is that v2 is compatible with GPLv3. There are some other changes like clarifications and requiring a patent if you contribute code that would infringe a patent that you own. For an overview of Apache2, see [2].
Overall, doesn't sound like a large change.
[1] https://en.wikipedia.org/wiki/OpenSSL https://en.wikipedia.org/wiki/OpenSSL
[2] https://choosealicense.com/licenses/apache-2.0/ https://choosealicense.com/licenses/apache-2.0/
- colejohnson66 8y agoI view the license change as a pretty big one. You said it too: Apache 2.0 is compatible with the GPL.
- johannes1234321 8y agoCompatible with GPLv3, not GPLv2, to best of my knowledge
- xorcist 8y agoToo bad they couldn't find a way to allow linking GPLv2 code with OpenSSL. As it stands every author has to add an OpenSSL exception to their licensing, which benefits nobody. It all seems a bit outdated and unnecessary. I guess that means OpenBSD can't use OpenSSL going forward either? They have previously excluded Apache 2.0 licensed software.
- protomyth 8y agoI guess that means OpenBSD can't use OpenSSL going forward either? They have previously excluded Apache 2.0 licensed software. They've switched to LibreSSL in base, but Apache 2.0 is fine in ports. I guess it might affect adding patches from OpenSSL.
- loeg 8y agoThere's also some dispute over whether OpenSSL has the right to relicense all of its codebase to Apache 2.0; they didn't require a copyright transfer from individual authors and don't have 100% authorial consent.
- yellowapple 8y agoOpenBSD's already using LibreSSL (their OpenSSL fork in response to Heartbleed), so they're already not using OpenSSL. The license change at this point only means that further upstream work can't be ported back over to LibreSSL.