6 ms·
OpenSSL Licensing Update
- JoshTriplett 10y agoThis 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_
- jasonkostempski 10y agoWhat happens if not everyone responds to the emails?
- shaggyfrog 10y agoThe OpenBSD team is asking that very same question: https://marc.info/?l=openbsd-tech&m=149028593819547&w=2 https://marc.info/?l=openbsd-tech&m=149028593819547&w=2
- amenghra 10y agoNow I can respond on his behalf...
- notaplumber 10y agoTake a look at the code they've attributed to him. I don't think he's overly concerned, not about that anyway. The overreaching attempt at re-licencing others work on the other hand...
- jwilk 10y agoWhy is https://github.com/openssl/openssl/commit/24956ca00f014a917fb181a8abc39b349f3f316f https://github.com/openssl/openssl/commit/24956ca00f014a917f... on the list of Theo de Raadt's contributions?
- okket 10y ago
- tyingq 10y agoI didn't understand the issue with the original license well, but found Wikipedia's overview: https://en.m.wikipedia.org/wiki/OpenSSL#Licensing https://en.m.wikipedia.org/wiki/OpenSSL#Licensing
- hedora 10y agoWow. Apache 2 has a patent license section that BSD style licenses are missing. At first glance, this looks like this change is being done in bad faith. Concretely: Contributing to apache 2 software potentially grants universal licenses for relevant patents you hold to anyone that uses the apache 2 software. Courts have not decided how viral this is. (What if I start with apache 2 code, make substantial changes, and apply it in areas the patent holder objects to, for example?) I'm not a fan of software patents, but sloppy retroactive relicensing like this will create all sorts of legal ambiguity for users and contributors. (Also, as the openbsd thread points out, apache 2 is license incompatible with existing openssl forks and other downstream software)
- obstinate 10y ago> Contributing to apache 2 software potentially grants universal licenses for relevant patents ... Not potentially. > (What if I start with apache 2 code, make substantial changes, and apply it in areas the patent holder objects to, for example?) The plain reading of the license is that it only grants licenses to patents which are necessarily infringed by the contributions of the patent holder. As for what would happen if you heavily modify it, I suppose the court would have to decide whether it is still the same work. But that's strictly more protection than you have under BSD, so I don't really see why you would view it as a negative.
- hedora 10y agoIf I'm the developer, I accidentally lose my patent, or (accidentally) misrepresent my employers intention not to license the patent, so I get hauled into court. If I am the user, and use Apache 2 software Yahoo (for example) contributed to before they sold their relevant patent to a troll, I'm fine. If that software is "Apache 2" OpenSSL, I'm totally screwed, even though the OpenSSL team's license.txt told me it's all OK while I was paying my lawyer to do due patent diligence.
- deleted 10y ago[deleted]
- 10y ago
- kstoneman 10y agoSeems like OpenSSL should focus on fixing their code instead of risking the alienation of past contributors. I wonder if this is to satisfy some of the big donors who want to fix OpenSSL but won't until the license is changed. I know I'd be pissed if I had contributed and then got an email saying no response implies agreement.
- eriknstr 10y agoI think with any larger scale open source project looking to change license they basically have to assert that no response implies agreement because of the amount of people that have contributed over time and things that this leads to, such as the probability that at least one of them might have died or otherwise have become unreachable since when they contributed. However they might have instead used some of the donor money to hire someone to do a clean-room re-implementation of the functionality for which they couldn't get the original author's blessing to change the license of. This might have been the more respectful thing to do perhaps.
- kstoneman 10y agoIf they don't do it, and just take the code someone else contributed to the project under a different copyright notice and put it under Apache 2.0, does that mean I can fork, say, Firefox or gcc and slap an MIT copyright on the source code if not all of the contributors reply to my email asking them if they agree to it? If no, then what percentage of contributors need to agree? Or do I need to rewrite all of the code that I get noes for?
- kibwen 10y agoAnyone with a potential copyright claim on the source can take legal action if they believe that their rights have been violated. If you object to OpenSSL relicensing and have contributed to it, you can sue them if they go through with it. Likewise, if you violate the license of any other software project, that project can sue you. OpenSSL is betting that the vast majority of contributors will agree, and that the rest will either not care or won't sue, and if someone does sue they're hoping that person's contributions are minimal enough that they can be removed from the codebase.
- deleted 10y ago[deleted]
- starseeker 10y agoAlthough I personally think matching the OpenBSD libressl license would have been better, I still have to regard the move towards using one of the mainstream, modern standard open source licenses for such a widely used and critical software component a Good Thing. I do, however, also agree with those voicing skepticism about the "silence gives consent" bit - this is important enough to be worth doing without adding a (very) questionable practice like that to the mix. I'd suggest instead setting up some sort of "relicensing coverage" report, and use the yay/nay/no-answer status of various diffs to figure out a price tag for re-writing the bits that can't be relicensed. I don't suppose the libressl folks could end up creating a 2-clause BSD implementation of the SSL/TLS stack that could divorce itself completely from its openssl origins? (Yes I know that's almost certainly impractical for such a large, complex and thorny code base and problem set, but it's a nice dream... maybe some cryptography researchers/companies/etc. looking to make a name the the industry could target and re-implement specific pieces/algorithms/etc...)
- Animats 10y agoThe Rust replacement for OpenSSL is coming along well.[1] It's available under Apache License version 2.0.. the MIT license, or the ISC license. That should be the future direction. [1] https://github.com/ctz/rustls https://github.com/ctz/rustls
- nopcode 10y agoIs rustls actually a replacement though? I can compile existing applications with rustls in stead of OpenSSL without altering the code of those applications?
- kazagistar 10y agoHopefully not, as one of the major problems with OpenSSL is its convoluted surface API which is easy to misconfigure.
- paulddraper 10y agoYeah...OpenSSL's difficulties cannot be _really_ fixed unless the the API is allowed to change. It's a hard slog either way.
- DannyBee 10y agoSo, the major question getting asked (and theo is trolling about elsewhere) is what happens if you don't respond to the emails. Having helped out with many relicensing exercises at this point, i'm not sure why people are so worried. The usual tact taken is: If you cannot affirmatively get consent, you remove the code and, if still needed, have someone not involved rewrite it. I have yet to see anywhere in all of this that actually says they plan on doing anything different (IE theo's trolling seems to be based not on reality). I looked at the press releases, details, and mailing lists. What am i missing?
- 4a6f656c 10y agoThe email being sent out clearly states: "If we do not hear from you, we will assume that you have no objection."
- ckastner 10y agoThe email can state all it wants, but from a legal point of view, assuming consent merely by absence of dissent is nonsense -- at least in the jurisdictions I'm familiar with. There are exceptions to this, but this is not one of those cases. Just assuming that the email has been read is already a far stretch.
- jwilk 10y agoThe process raises my eyebrows, too, but apparently that's how it was done for other projects: * https://mailman.videolan.org/pipermail/vlc-commits/2011-November/010353.html https://mailman.videolan.org/pipermail/vlc-commits/2011-Nove... (grep for "It is possible") * https://dolphin-emu.org/blog/2015/05/25/relicensing-dolphin/#a-legal-gray-area https://dolphin-emu.org/blog/2015/05/25/relicensing-dolphin/... * https://blogs.fsfe.org/ciaran/?p=58 https://blogs.fsfe.org/ciaran/?p=58 (grep for "it is not necessary")
- ckastner 10y agoAh. In those cases, it appears that the overwhelming majority (>= 95%) of developers explicitly agreed to the relicensing, with the remaining minority at least not objecting. That is still not assent by the remaining 5%, but was apparently sufficient for relicensing of the whole work in the relevant jurisdictions. In that context, the quote from the OpenSSL email appears to be well-phrased, as it really only assumes the absence of objections.
- Daviey 10y agoFinally! This should mean Debian & Ubuntu can enable SSL in Squid! EDIT: Dammit, Squid is GPLv2.. It might make the situation worse due to the Patent clause. So, potentially now.. GPLv2 programmes can't use OpenSSL. Nice.