9 ms·
“Tivoization” and Your Right to Install Under Copyleft
- AceJohnny2 5y agoApple has explicitly chosen to stay away from anything GPLv3. It's the reason Bash and other tools bundled with macOS are so old (they're the last version that were still GPLv2), and why they chose to switch to Zsh as a default.
- bumblebritches5 5y agoGoogle too, hence Fuscia.
- cma 5y agoAside from that stuff it is hard to use Mac seriously as a unix anymore after they started wiping out /etc/ changes every update (with insecure ssh defaults like password authentication).
- deleted 5y ago[deleted]
- IntelMiner 5y agoThat's shot them in the foot many times over the years. Especially when they tried to replace Samba with their own SMB implementation in I believe 10.7 Lion?
- whoknowswhat11 5y agoI think you underestimate how much traction Samba lost with GPLv3. You used to have a system that was just wonderful across Linux / Mac / Windows. Seriously, you'd run Samba on server and Mac would work great with it because under the hood the Mac was running Samba. Windows would work fine too for what most folks cared about. That was lost when Samba went v3. One thing - the hosting loophole is still there I think with GPLv3, so you can offer HOSTED services with Samba. I think some folks have done things there maybe.
- smoldesu 5y agoSamba still works like a charm on my network, but only because I'm sharing between Linux/Android/Windows devices.
- josephcsible 5y agoThere's no clause in the GPLv3 that says "Apple may not use this software". Apple could use the new Samba if they wanted to, but they choose not to because they like being able to do the bad things that the GPLv3 prohibits doing.
- ribit 5y agoWhat „bad things“?
- ajklsdhfniuwehf 5y agosliping in divergencies in the protocol so that you can only connect to Apple-Active-directories or something. Microsoft wrote the book in the 90s about this. https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
- ribit 5y agoRight. And implementing their own SMB server (smbd) allowed them to do these "bad things"? What is the evidence that they did anything like that? Anyway, how about a much simpler explanation: Apple doesn't want to get stuck with a viral license that might open them to lawsuits and force them to open up their proprietary code they want to keep closed source? GPL doesn't work for everyone and there is nothing wrong about that. To suggest that anyone who rejects GPL plans something "bad" is naive and immature.
- ajklsdhfniuwehf 5y ago> What is the evidence that they did anything like that? LOL. you are joking right? Apple uses the textbook from microsoft the second they can. When they stuck gold on IOS the first thing they did was draw up a monopoly on music and ibooks licensing scheme. And those are just the ones they were found guild on courts with public records. The last one, also on courts public records, is about how they prevent their messaging applications to work on non-apple because it would "allow families to buy android devices to their children" Oh, you trolls. I keep falling for your low efforts...
- bb88 5y agoYeah, I find it weird that considering that homebrew is what makes macs acceptable for software development, you'd think apple would want to support things like bash as first class citizens on their os.
- varajelle 5y agoThe "tivoization" was not the only change in GPLv3. It also has patents related changes, which I think is what scared apple.
- swiley 5y agoApple has convinced me of the need for FOSS more than RMS ever could have.
- bb88 5y agoThe original Tivo land-line modem would die, making it impossible to dial out to get guide data. Interesting though there was a card edge connector on the mother board. Some enterprising person made an adapter that allowed an ISA ethernet card to be plugged in, and then the Tivo would use the network instead of the modem. Further Tivo not only allowed this, but tacitly encouraged it by including the network driver needed to make this happen on tivo firmware upgrades. https://www.samba.org/~tridge/tivo-ethernet/ https://www.samba.org/~tridge/tivo-ethernet/
- bkallus 5y agoI'm surprised to see that installation is a requirement of the GPLv2. Does this mean that Android phones with bootloaders that can't be unlocked violate the GPL?
- kmeisthax 5y agoYes, but given that most of the copyright owners of Linux do not believe GPLv2 to have such a requirement (and explicitly abhor the idea that v3 adds one, even though it didn't add it) I doubt anyone with standing is interested in enforcing said requirement.
- whoknowswhat11 5y agoSeriously, the idea that after losing this fight clearly with GPLv3 that they are going to force this down folks with a re-write of history / language / intent and practice is appalling. Hopefully someone like Linus can make absolutely clear this is total garbage.
- bkallus 5y agoWhat I think is total garbage is the fact that I have a drawer full of potentially useful computers (EDIT: by computers I mean mostly phones, routers, e-readers, etc) stuck running insecure OSes. Can you give me an argument for why installation should not be required? It seems pretty clear to me that if release of "the scripts used to control compilation and installation of the executable" is required by the GPLv2, then those scripts should have to be functional.
- whoknowswhat11 5y agoThey are functional on hardware you build. The source code is released. No one disagrees there. Buy unlocked hardware if you care about this. Most PC's can disable secure boot paths through BIOS settings unless you are in a corp environment and they lock that out.
- whoknowswhat11 5y agoGod - the GPLv3 folks basically totally lost the debate on tivoisation - and now are trying to retrofit this war into GPLv2. Are they serious?? Many OSS developers always want to get a copy of the software and mods back, but are OK if others USE that software in diverse ways, including making locked down hardware that is rented, radios that are power limited and more. In this way the GPL preserves everyone's freedom to do what they want with the software. The GPLv2 has served a wide range of needs, from Linus and Linux to plenty of industry efforts. Linus was asked about this in a talk and he said he a)gets value in terms of forcing vendors to release code even from players like Tivo and b) is not interested in setting lots of additional restrictions on how folks use the code. The FSF / Conservancy keep on re-assuring folks that encryption keys don't have to be released. Ubuntu went through an analysis and basic result was that this is a lie, lots of things may force secure boot key disclosures, so they avoided that by avoiding GPLv3. Can we just leave GPLv2 as it has been. If the FSF or whomever wants another bite at the GPLv3 apple create a GPLv4 and let folks adopt it if they want.
- josephcsible 5y ago> In this way the GPL preserves everyone's freedom to do what they want with the software. Except the freedom of the people who bought a TiVo and want to modify Linux on it. > Ubuntu went through an analysis and basic result was that this is a lie, lots of things may force secure boot key disclosures, so they avoided that by avoiding GPLv3. Can you link to a source for this?
- whoknowswhat11 5y agoExcept the DEVELOPERS of linux - who are the ones that get to set license terms not users - have been clear - they want users / companies etc to have freedom to use software how they want to. This might be locked down devices -> yes, and Linux is used in plenty (medical equipment, vehicles etc). Plenty of folks ONLY use it in these cases because they can control a root of trust. This is an old fight. The GPLv3 came out to allow developers who wanted anti-tivosation to get it. Practically it's really dead. Sure on Ubuntu Ubuntu Can't Trust FSF's Secure Boot Solution https://linux.slashdot.org/story/12/07/06/1525240/ubuntu-cant-trust-fsfs-secure-boot-solution https://linux.slashdot.org/story/12/07/06/1525240/ubuntu-can... I followed this reasonably closely, and it was a total lie on FSF's part - Ubuntu looked at it and agreed. Sadly for those of us running Linux they had to adopt MICROSOFT's UEFI secure boot. Ugh.
- ohazi 5y agoMy biggest problem with the GPL (any variant) is that I don't believe that any organization that exists today (including the SF Conservancy and the Linux Foundation) is capable of enforcing it to the degree desired by the software freedom die-hards. I say this as a software freedom die-hard myself. In theory, you can cook up any license terms you want, but in practice, you need money and resources and the will fight in court if you actually want to enforce it. If you can't or won't enforce it, your silly terms may as well not exist. Unfortunately, the nature of how proprietary software is distributed makes discovery of a violation inordinately difficult, and even when you do discover a violation, challenges are rare, and victories in court even moreso. I don't see the point of debating the minutia of what you think the GPLv2 requires in one very specific instance, when there are probably 2-5 orders of magnitude more violators than anybody's best estimate. Who cares what you think the letter of the license requires when it takes you ten years to get one company to make a passive-aggressive change to a now obsolete product, when thousands of violators don't even follow the spirit of the license? This feels like such a wasted effort. Get your priorities in order.
- pabs3 5y agoConservancy recently got a grant for compliance work, and are working on an enforcement action in the IoT space: https://sfconservancy.org/copyleft-compliance/firmware-liberation.html https://sfconservancy.org/copyleft-compliance/firmware-liber... The bigger problem is that outside of the FSF and Conservancy, large amounts of the Linux developer community and several ostensibly Free Software companies/organisations do not want the GPL to be enforced at all.
- whoknowswhat11 5y agoThere has been relatively high levels of support for normal / standard GPLv2 enforcement. That said, the FSF and Conservancy like to pick more edge cases and go to absolute war on them. That doesn't generate as much support it is true and a lot of parts of the GPLv3 push also rubbed folks the wrong way. "Linus says says GPL v3 violates everything that GPLv2 stood for" https://www.youtube.com/watch?v=PaKIZ7gJlRU https://www.youtube.com/watch?v=PaKIZ7gJlRU is but one of many many examples here.
- whoknowswhat11 5y agoFor those not interested in reading this long arguement the actual license simply says you must release the source code to your application "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." This is relatively routine. The major new claim here is that releasing source code requires folks to unlock secure boot / root of trust / DRM type implementation on HARDWARE they sell. So release a complete work no longer (as plain language would read) means releasing the source code - but now ALSO requires that developers add various features to HARDWARE to bypass root of trust security measures which may include things around power limits or management on equipment or for things like phones sold on installment plans with a vendor lock would let folks pick up the phone on plan, root it to avoid vendor lock and then stop paying on phone.
- deleted 5y ago[deleted]
- josephcsible 5y ago> phones sold on installment plans with a vendor lock would let folks pick up the phone on plan, root it to avoid vendor lock and then stop paying on phone. You realize that bootloader unlocking and carrier unlocking are totally separate, orthogonal things, right?
- whoknowswhat11 5y agoDo you understand the GPLv3? It made clear that any of this locking on hardware was prohibited. Vendors of products that had these locks have to provide the security / encryption keys to bypass them if they use GPLv3. As a result, they do not.
- josephcsible 5y agoThere's two separate sets of keys. One controls what OS the phone's CPU will boot, and the other controls what SIM cards the phone's baseband will use. Nothing would require releasing the second set of keys.
- reflexe 5y agoBash and readline are both gpl-3. In theory, in some cases, you can force the company to give you the option to replace them with your version. Cleaning up gpl-3 is not fun.
- jsbdk 5y agoJust by reading the first paragraph I can see how unbiased this article will be. The gplv3 has been an utter failure. Trying to rewrite history so the gplv2 works like the gplv3 is pathetic and will be the last nail in the coffin of the GPL.
- selfhoster11 5y agoI doubt it. There is no way I'm releasing valuable FOSS software as anything less restrictive than GPL. No feeding the corporate behemoths.
- pabs3 5y agoThe article makes it clear that this is always how GPLv2 has worked and been enforced in entire history of its existence.
- FounderBurr 5y ago“Free” software is never free. It’s extraction of payment by other and often endless means.
- JetSpiegel 5y agoThis is another interesting take: > As I was completing drafting on this article, the Linux Foundation sent me a rejection letter for my talk about this issue at their annual Open Source Summit (taking place this September 2021), and simultaneously announced McCoy will speak on this matter instead. I invite McCoy to not take the easy way out of presenting his work unquestioned to a friendly audience. I would be glad to come to the Open Source Summit in September and debate McCoy publicly on this issue during this session. I believe the audience would benefit from hearing more than just the anti-software-repair view of this issue.