14 ms·
> the GPLv2 does not require that the modified code must be able to be installed back on the original hardware by the person doing the modification Does not ex
by mindslight 11y ago
> the GPLv2 does not require that the modified code must be able to be installed back on the original hardware by the person doing the modification
Does not explicitly. From GPL2:
> Accompany it [executable code] with the complete corresponding machine-readable source code ... The source code for a work means the preferred form of the work for making modifications to it
So, you're telling me that the preferred form for making modifications to the source code of a router does not include the scripts which install onto the router to test those modifications?
> Not by any legal definition of "bad faith"
The GPL2 and the FSF are very explicit on what the GPL2 is supposed to engender. Accepting the license and trying to circumvent it on a possible technicality (assertion that a signed blob isn't a derivative work, when the only reason anyone is interested in the source code is to run it) looks pretty bad-faith to me.
IANAMOAG (I am not a member of a guild, and you probably aren't either). Even if we were, we could still disagree until it was actually litigated. I see no reason to prematurely capitulate Linux devices being non-Free.
- eli 11y ago> So, you're telling me that the preferred form for making modifications to the source code of a router does not include the scripts which install onto the router to test those modifications? In short: yes. Being able to access and modify and redistribute source code isn't the same as having the ability to deploy it to a particular piece of hardware. Likewise, if I open source a .NET project that doesn't mean it has to include Visual Studio even though VS is the preferred way to build it.
- mindslight 11y ago> Being able to access and modify and redistribute source code isn't the same as having the ability to deploy it to a particular piece of hardware But the preferred form for modification includes being able to test your changes. Source without installation scripts is most likely not the preferred form - ie what do engineers at the company use? > if I open source a .NET project that doesn't mean it has to include Visual Studio, which is the preferred way to build it Yes, because having been designed in the era of expensive compilers, GPL2 explicitly covers this: > However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable
- mynameisvlad 11y agoVisual Studio is not a "major [component] ... of the operating system on which the executable runs". It's not any component, in fact; it's a completely separate application from the OS, and in no way bundled together.
- AnthonyMouse 11y agoYou're arguing that a compiler is not a major operating system component when the license explicitly enumerates it as a major operating system component. Nobody says you have to get all your operating system components from the same disc.
- mynameisvlad 11y agoThe compiler is part of VS though, not part of the Windows. You don't get VS if you have Windows, and you don't get Windows if you have VS. They're completely separate products. So if it isn't actually included with the OS, and you need to acquire (either through a free or paid license) a completely different product to get it, then I don't see how it could be considered a major component of the OS, regardless of what the license text says. It's not a matter of it being on another disk, it's a matter of it being a completely different product in the Microsoft world.
- AnthonyMouse 11y agoIt doesn't say anything about products. It doesn't say that major components can't be optional components. It does say that a compiler is a major component of the operating system. You're trying to draw a box around "Windows" and define operating system as everything in that box. But minesweeper is not an operating system component, it's just something that comes with Windows. A hypervisor is an operating system component, even though not all versions of Windows have one. So is a compiler. I imagine there exist developer-oriented PC OEMs that offer PCs with Windows and Visual Studio already installed. So then it is included with the OS by the OEM. The fact that that would change the outcome in your interpretation implies that there is something wrong with it.
- dfox 11y agoIIRC FSF's position on this is that the original author has to include inlude explicit GPL exemption for things like MFC, VCL or even OpenSSL, if the program depends on them, in order for anyone to be legally able to distribute binaries. I would assume that something similar comes into play when building the program requires proprietary compiler that is not "component of the operating system" (although in that case it might very well be implied). That in practice nobody except FSF and Debian cares is another thing.
- uxp 11y ago> So, you're telling me that the preferred form for making modifications to the source code of a router does not include the scripts which install onto the router to test those modifications? No. Not really. GPLv2 requires that the modifier of source code release the tools to build/compile that source code into an executable. Whether or not the source code can be run directly (ex. Ruby, Python) or requires a compile/assemble/link process (ex. C, Java) is irrelevant. The GPLv2 also does not entitle or give anyone rights to any method to execute that recontributed and rebuilt code, for example if the code was ported to a proprietary hardware or some closed sourced ISA. However, IANAL and could very well be wrong because the GPL is such an unwieldy beast of unknowns.
- dtparr 11y agoI'm not sure how this is premature. The reason the practice is called tivoization is because we went through all this years ago when Tivo did it. The FSF acknowledges that releasing the source but locking you out from installing your self-built version of it does comply with the GPL2, which is why there's a GPL3. See https://www.gnu.org/licenses/gpl-faq.html#Tivoization https://www.gnu.org/licenses/gpl-faq.html#Tivoization
- mindslight 11y agoIMHO, poor wording in a FAQ by the FSF. The company considers themselves complying with the GPL2 by releasing a scrubbed tree. The FSF looks the other way, having limited resources. I'm having a hard time digging it up, but I swore I have seen a video where RMS lays out the exact same theory I'm saying here. It's not a terribly outlandish theory. I'm just getting a lot of flak for bucking the status quo from people who grew up with DRM kool aid and see Free software in terms of the corporations that lock it down.
- dtparr 11y agoSo, I don't think people have 'drunk the DRM kool aid' so much as everyone has generally agreed for the last decade or so that GPLv2 doesn't prevent tivoization and GPLv3 does. That everyone includes RMS, by the way. Here's a transcript[0] from 2006 where he's talking about it and says: >For instance, the Tivo itself is the prototype of tivoisation. The Tivo contains a small GNU/Linux operating system, thus, several programs under the GNU GPL. And, as far as I know, the Tivo company does obey GPL version 2. They provide the users with source code and the users can then modify it and compile it and then install it in the Tivo. That's where the trouble begins because the Tivo will not run modified versions, the Tivo contains hardware designed to detect that the software has been changed and shuts down. So, regardless of the details of your modification, your modified version will not run in your Tivo. So while you may be correct that it's never been litigated, it would seem that if the strongest software freedom advocates like RMS and the FSF thought that it did violate GPLv2, surely rather than telling people they should upgrade to V3 because it blocks tivoization [1], they would have just litigated against tivo and set the precedent. [0] http://fsfe.org/campaigns/gplv3/tokyo-rms-transcript#tivoisation http://fsfe.org/campaigns/gplv3/tokyo-rms-transcript#tivoisa... [1] https://www.gnu.org/licenses/rms-why-gplv3.html https://www.gnu.org/licenses/rms-why-gplv3.html
- devit 11y agoIf you consider signed blobs derivative works (which means hashing and producing a signature creates a derivative work), then any signed statement referring to an hash of the source code (or including the source itself) is also a derivative work. This means that someone sending a PGP signed e-mail saying "I audited that the source code of GNU Foo with hash 0xdeadbeef... is free of backdoors" is violating GNU Foo's copyrights unless he releases his private keys. This is obviously a very undesirable outcome, and so it's resonable to hope that hashing does not create derivative works, and thus signing doesn't either. Including the scripts to install in the "preferred form" also seems very problematic because then you might also be forced to include a full copy of the hard drive of your development machine since that's an even more "preferred form" under that theory. This is also a very undesirable outcome, so it's again reasonable to hope that "preferred form" does not necessarily include things that were absent in the original work and that aren't essential for reproducing the binary derived work itself.
- mindslight 11y agoIt's not the hashing of the object code that makes the signature a derivative work. It's the appending the signature and object code that creates one whole work.
- tzs 11y agoYet in GPLv3, where they could have explicitly made it so that the modified code must be able to be installed back on the original hardware, they declined to do so in the general case. The anti-tivoization clause instead was written narrowly to only apply when the object code was conveyed "as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized)". Note that this means that I could sell a device that only runs signed code and could separately sell signed apps for that device that the user can buy and install later, and as long as the code that ships with the device is not GPLv3, I could use GPLv3 code in the signed apps and would NOT be required to release signing keys under GPLv3. (The Apple App store incompatibility with GPLv3 has nothing to do with the app signing requirements. It is due to the terms of service that users are required to agree to in order to access the store. These impose what the GPL considers to be additional, incompatible conditions). It seems odd, if they felt the way you think they do, that they would have written this so narrowly.
- DannyBee 11y ago"So, you're telling me that the preferred form for making modifications to the source code of a router does not include the scripts which install onto the router to test those modifications? " Yes. 100% yes. It is very explicit in what must be included and you are explicitly ignoring what it says about scripts: " For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. " Scripts used to control compilation and installation != signing keys. It means scripts used to control compilation and installation. You may want it to include something more, but it doesn't. That's why GPLv3 was written.
- AnthonyMouse 11y ago> Scripts used to control compilation and installation != signing keys. You're referring to "scripts used to control compilation", but how are signing keys not part of the source code? GPLv2 uses a specific definition of source code, "the preferred form of the work for making modifications to it." Don't you have to be arguing that a form not allowing modifications to be used or tested is the "preferred form of the work for making modifications"?
- DannyBee 11y ago"" Don't you have to be arguing that a form not allowing modifications to be used or tested is the "preferred form of the work for making modifications"?" You are trying to take parts out and remove context from them. I don't have to argue at all about the preferred form, because it very explicitly says what that is: "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable." The first two sentences go together. It defines, explicitly, what the preferred form of complete source code for an executable work includes. So that isn't going to include signing keys unless you want to argue that one of the explicitly enumerated parts includes signing keys. For years, people have argued back and forth about whether the scripts include data files. The general consensus is "no", because otherwise, it has no differentiable meaning from the other parts.