6 ms·
This is a huge win. The incompatibility between OpenSSL and the GPL has been one of the most notable license incompatibilities regularly encountered in practic
by JoshTriplett 10y ago
This is a huge win. The incompatibility between OpenSSL and the GPL has been one of the most notable license incompatibilities regularly encountered in practice. With this change, OpenSSL will become compatible with GPLv3, which also makes it compatible with software licensed "version 2 or later". People will no longer need to choose and port to another crypto library for license reasons.
- kibwen 10y agoThough worth noting that ASLv2 is not compatible with straight GPLv2 (the "or later" part of "version 2 or later" is crucial). This is why some projects dual-license as MIT/ASLv2, because MIT is compatible with GPLv2.
- KenoFischer 10y agoLLVM's proposed switch included a provision to make it explicitly compatible with GPLv2. That seems like a nice precedent to follow for other projects that are considering Apache 2 as their license.
- kibwen 10y agoI'd say that works for LLVM only because Apple can afford lawyers who can argue that provision if it ever came to that (not that I think it ever would). AFAICT, ASLv2 is superior to BSD/MIT in all practical respects except for the GPLv2 compatibility, and if it were so trivially easy to make a version of ASLv2 that didn't have that downside, then I feel like some company would have already done that and instantly created The One Permissive License To Rule Them All (and in the eyes of the law, bind them). Until such an exceptional provision becomes established precedent, I'd suggest that small projects stick to vetted licenses rather than pitching in with anything novel.
- int_19h 10y ago> AFAICT, ASLv2 is superior to BSD/MIT in all practical respects except for the GPLv2 compatibility Not for the companies. Many prefer MIT over ASL precisely because they don't want any sort of patent grants.
- riffraff 10y agoWhy do they prefer to avoid patent grants? It seems unreasonable to me.
- yarrel 10y agoIt is, but it's what they want.
- kibwen 10y agoAFAICT this is overstating the patent-related aspects of ASL. It doesn't require a patent grant or nullify any parents you hold, or even prevent you from suing others over misuse of those patents. All it does is provide mutually assured destruction: if you sue someone over the use of your patent within this software, then you forfeit any legal protection from others who have patents within this software. This is extremely company-friendly, because companies are the ones who tend to go around suing over patents, and also the ones who feel compelled to stock up on patents to use defensively.
- jabl 10y agoIf you're worried about the GPLv2 and ASLv2 incompatibility, why not dual license as ASLv2/GPLv2 then instead of ASLv2/MIT?
- JoshTriplett 10y agoBecause porcine flight seems more likely than many OpenSSL developers agreeing to license anything under the GPL?
- jabl 10y agoI wasn't thinking of OpenSSL specifically but rather as a general question. E.g. why is Rust ASL2/MIT licensed (my guess is that it's just what Graydon originally chose for whichever reasons and nobody cares enough to change it)?
- steveklabnik 10y agoIt was originally only Apache2, but MIT was added later to add GPLv2 compatibility.
- bonzini 10y agoDual-license MIT/ASLv2 is pointless, since MIT is not incompatible with ASLv2: it allows relicensing and is pretty much a subset of ASLv2. Likewise, LGPL/GPL/MPL is pointless because LGPL already allows you to take the work and relicense it under the GPL.
- hsivonen 10y agoDual MIT/ASLv2 is how Rust achieves GPLv2 compatibility while requiring contributions to be under the superior (to MIT) ASLv2 language, too. ASLv2/GPLv2 dual would achieve the GPLv2 compat goal without potential unintended other consequences arising from the MIT part. The old Mozilla tri-license had both LGPL and GPL to relieve recipients from following the (impractical) letter of LGPLv2.1 when choosing to do the LGPLv2.1 to GPLv2 step.
- stonogo 10y agoA "huge win" being enacted by a complete disregard for the copyright holders who were kind enough to contribute to the project. I find this behavior utterly unacceptable. If more projects attempted this bullshit the whole world would be a mess. What's to stop someone from relicensing a GPL program to closed-source, and assuming that anyone who might object would have spoken up? This is breathtakingly idiotic.
- Spivak 10y ago> What's to stop someone from relicensing a GPL program to closed-source. Nothing, but it doesn't retroactively affect anyone who already has a copy of the software under the GPL. What might stand in the way is a copyright holder refusing to go along with the relicensing.
- Manishearth 10y ago> A "huge win" being enacted by a complete disregard for the copyright holders who were kind enough to contribute to the project. Uh, no. That's not how this works. OpenSSL cannot change the license without say-so from all of the contributors, unless a CLA was signed. They do have a CLA, but just one granting a license, not one transferring ownership (and the right to relicense). At least, doesn't look like it. OpenSSL emailed everyone with commits on the project (e.g. me) a link to a page where you could say yes/no on this. In most cases this isn't a vote, it's all-or-nothing, though the choices of people with extremely minor (non copyrightable) contributions can be excluded IIRC. IANAL. (There is some discussion below about "if you don't reply we take that as a yes" being okay, though)
- caf 10y agoI would guess that if only a small number of contributors disagree, they'll follow-up by asking those contributors which parts they claim a copyright interest in. Then it can be determined if it's feasible to go forward without those contributions or not.
- Manishearth 10y ago
- hedora 10y agoIt is also (according to the OpenBSD mailing list) a huge loss for LibreSSL and OpenBSD because they can no longer take patches from openssl. There is no explicit mention of tools like OpenSSH that are part of OpenBSD, but are more widely distributed. I don't know enough details to know if they are impacted or not (but would love to hear from someone that does know).
- JoshTriplett 10y ago> It is also (according to the OpenBSD mailing list) a huge loss for LibreSSL and OpenBSD because they can no longer take patches from openssl. Apache 2.0 is a permissive license; they could certainly take patches from OpenSSL and ship them under that license. They might choose not to, of course. But that's the choice of the downstream project.
- Canada 10y agoDidn't OpenBSD fork Apache 1.3 over this exact issue? http://apache.org/foundation/license-faq.html#PatentScope http://apache.org/foundation/license-faq.html#PatentScope
- Esau 10y agoMy understanding is that they did, which is why they had such an old version for such a long time.
- hedora 10y ago"Permissive" is a spectrum on many dimensions. This relicensing is less permissive than the old license in some ways (like patent requirements for developers) and more permissive in others (the advertising clause). If the relicensing was done with the requirements of the whole open source community in mind, they would have dual-licensed or just removed the advertising clauses (and whatever else is GPL incompatible). Why not turn the tables and relicense OpenSSL under the AGPL? Current users couldn't accept security patches unless they "chose" not to release a bunch of unrelated proprietary code under the AGPL, including things they don't have copyright to. The only real difference is that service provider's rights would be trampled instead of developer's rights.
- feld 10y agoThis is _illegal_