FSF Rattles Tivo Saber At Apple
Ohreally_factor takes us back to Friday when both the iPhone and the GPLv3 were released. "This article at Tectonic suggests that Apple's iPhone might run afoul of the GPL. Peter Brown, executive director of the FSF is quoted as saying: 'Today, Steve Jobs and Apple release a product crippled with proprietary software and digital restrictions: crippled, because a device that isn't under the control of its owner works against the interests of its owner. We know that Apple has built its operating system, OS X, and its web browser Safari, using GPL-covered work — it will be interesting to see to what extent the iPhone uses GPLed software.' Might there really be GPLed code in the iPhone? It's well known that OS X built on BSD, which of course uses the BSD license. Webkit is based on KHTML which uses the LGPL."
If there isn't any evidence of GPL violation, why make the accusation?
This is despicable sensationalism, and not what I'd expect from the FSF.
Apple's work on the Mach kernel for ARM isn't under the GPL, it's under the BSD license. The graphics libraries are their own, and KHTML is available under it's own license. The FSF is trying to pull a Greenpeace-style publicity-grab here.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
This is a base attempt to get attention, to get some of the bigger press outlets to look at them. I suspect that they are in reality simply resenting that the iPhone buried almost all awareness of the GPL3 release, and are now desperate for attention.
BSD zealot strikes again?
As often said, (L)GPL is about protecting the freedom of the *USERS*.
GPL serves to basically grant to USERS freedom to do whatever they want with code, as long as they pass along the same freedom, shall they decide to distribute the code (ie.: they have to transmit the code and the same freedom to the next in line).
Yes, it does restrict professional developpers', manufacturers' and other corporates' freedom. But the GPL was always centered around the user.
The problem that the FSF is trying to bring attention to is that with iPhone those users' freedoms aren't preserved. There is code covered by GPL or LGPL version 2 or previous inside the iPhone. One well known exemple is WebKit/KHTML.
You bought the iPhone, and you own it, it's yours. You got the software running on the iPhone, and you can get the source code for (L)GPLed elements from the web.
BUT you can't do whatever you want to do with it : you can't recompile it and put a new version.
Let's say that KHTML gets some upgrade making it better support newer standarts (strong standart support has always been KHTML/Webkit's selling argument). Or let's say GCC or some other compiler project (be it closed or open source) release a newer compiler version which compiles much faster code, and produce faster software.
The "do-whatever-you-want" freedom to tinker should allow you to rebuild the webkit component in the iPhone (and having either a better or a faster one, according to the previous scenarios).
*BUT* you can't actually upload the newly produced firmware, because the iPhone is DRMed to the bone with Trusted Computing chips, and as such does only run signed and crypted code. The DRM architecture in the iPhone takes away your freedom as an end user to play around with FLOSS inside the firmware.
The only hope for you is to wait and hope that Apple will release a newer firmware with an upgraded WebKit and/or recompiled faster. And hope that Apple won't act like other phone manufacturer ("Sorry this new feature [which btw is only a matter of software support] is only supported in our newer Phone model. Buy it now and enjoy support for newer web-stantard or whatever else").
Once again tivoization occurs.
The speculation of the article ask an open question about what is the long term impact of GPLv3 on this kind of behaviour.
This is an interesting thing to ask oneself. It brings lot of questions about the future :
- Will companies start to think of strategies to let the user tinker the GPL parts (special signing keys for the GPL modules can be ordered from the manufacturer that allow to use modified GPL code in the firmware, while everything else is still restricted) ?
- Will manufacturer start forking project (Apple's forks staying GPLv2, while opensource projects slowly make transition toward GPLv3) ? And which manufacturer will be able to sustain their own fork, or will most of that forking will lead to poorly maintained projects ?
- Or will manufacturer simply stop using GPL code at all and slowly switch to more corporate-friendly instead of user-friendly license like BSD ?
- And will Apple try to bribe the FSF by offer free iPhone, please ?
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Apple already have their own KHTML fork, it's called Webkit. The two pieces of code have separated quite a way now, although there appear to have been attempts recently from both sides to pull them a little closer together again. Apple is more than capable of keeping webkit going on their own.
Combination - fun iPhone puzzling
> The DRM architecture in the iPhone takes away your freedom as an end user to
> play around with FLOSS inside the firmware.
Whoa there! FSF makes an accusation and you swallow it without question? There is no proof that there is any GPL software in the iPhone and until such proof becomes available, how are you any better than RIAA or SCO in assuming otherwise?
> Or will manufacturer simply stop using GPL code at all and slowly switch to more
> corporate-friendly instead of user-friendly license like BSD ?
More likely they will simply continue making and using proprietary code. That's what I would do. Aside from really large projects like the Linux kernel, it is not that much more difficult to rewrite than it is to reuse. That's what salaried programmers are for and lots and lots of unpaid overtime. If they bark, we can always outsource to India.