USDTV Subscribers Gouged For Linux USB Keys 191
Former USDTV Subscriber writes "A few weeks ago, Salt Lake City-based USDTV discontinued their service. USDTV used the Hisense DB2010 as subscriber boxes, with Linux based firmware. USDTV should have released the source and binaries as required by the GPL, in order for customers to create a USB key to convert their DB2010s to FTA HDTV boxes. Instead, they chose to hand the keys to former USDTV subcontractors. Cable Communications is coming to subscribers' houses and updating the boxes, but not leaving a USB key. ProServ is selling USB keys. But 'Due to copyright laws you are only allowed to purchase one of these keys if you have proof of being a current or previous subscriber to USDTV.' USDTV customers are being charged $30 for a service and/or files that should be freely available to anyone who has a DB2010 in their possession. There is a thread on the AVS Forum detailing the whole debacle."
Possibility of GPL Validation (Score:5, Insightful)
Tough call; I'm in favor of an attempt to enforce the GPL (and potentially get validation from a US court that it is, in fact, a legally enforceable license).
Ask them nicely, sue them if they don't comply (Score:4, Insightful)
Re:Possibility of GPL Validation (Score:1, Insightful)
Re:Possibility of GPL Validation (Score:5, Insightful)
To which you respond by asking what they would think if the company had installed windows on all of these boxes without paying for a single license.
Same thing either way. You either pay with the code, or you pay with your cash. Or use BSD.
You can't be forced to open source your code. (Score:2, Insightful)
Re:W H A T ? (Score:2, Insightful)
Re:Gouged? (Score:5, Insightful)
Re:Gouged? (Score:3, Insightful)
That's incorrect. Firefox is tri-licensed -- LGPL, GPL, and MPL. You get to pick which one you want.
Re:Who cares? (Score:3, Insightful)
Seemsd like a waste to me, but a lot of people do it.
correct me if I'm wrong... (Score:3, Insightful)
I mean sure, if the firmware is GPL'd then according to the GPL we have to have access to it. But, if a key is required (as in a crypto type key) then that would NOT exactly be covered under the GPL. Thus NO violation.
I'm not sure this is the case. (Score:5, Insightful)
The GPL requires that IF you distribute code, you also have to distribute source code, and the person you give that code to can then also redistribute it under the same terms.
But, if I give you code, and you change it, and then you don't give it to anyone, guess what, you don't have to give the source code out at all.
So, in this case, who owns the receivers? If the cable company owned the receivers, and were just leasing them to the customers, I don't see that there's any infringement taking place. They're not distributing the software (it's on their hardware), so they're not obligated to distribute the source either.
Now, if they SOLD the boxes to the end consumer, then they'd be obligated to distribute the source, but is that the case here? Or did people just end up with abandoned receivers when the cable company went out of business?
Stop right there (Score:3, Insightful)
First question that comes to mind:
How many subscribers would be able to flash the firmware without bricking their box even if they had the source code and binaries?
[it happens, sometimes, even to the geek who is sure he knows what he is doing]
Second question:
Where in the contract does it say that these set top boxes are user-serviceable? If they are not, then the code becomes of intellectual interest only.
Third question:
What makes paying for a USB key differet from paying for a CableCard to access and unlock subscription content and services?
Re:Ask them nicely, sue them if they don't comply (Score:3, Insightful)
This isn't accurate. I'm not a lawyer, but I have actually read the GPL and payed attention to legal discussions related to the GPL.
First, only the copyright holder can sue for copyright infringement. Unless that's you, you have no standing for a copyright infringement claim. There are some other marginal ins you might have, but they don't really apply to this case.
Second, they aren't obviously violating the GPL. The GPL says they need to offer source code to anyone with binaries for the cost of distribution. A USB key + shipping + handling is $30. You could argue about what a reasonable "handling" charge is, but they're not obviously in the wrong.
In the end, this isn't an argument over software freedom or the GPL. It's an argument over $20. And, frankly, $20 doesn't matter that much.
Re:Possibility of GPL Validation (Score:4, Insightful)
Comment removed (Score:3, Insightful)
Re:Possibility of GPL Validation (Score:3, Insightful)
I was there, and I'm pretty sure that never happened.
You're right that the "is the GPL enforcible" question did come up occasionally before the SCO trial started, and the counterargument you give is exactly what many people responded with. I stand by my claim that the question only really showed up with any frequency after it was popularized by SCO.
More importantly, I stand by my comments on the relevance of the question. Very simple, no-one wants the GPL to be invalid because it's the only thing giving them a right to modify and redistribute GPL-covered programs. The question isn't "is the GPL enforceable", the question is "if you're unwilling to comply with the GPL, what gives you the right distribute that copyrighted software?"
Re:Dangerous to use Linux? (Score:2, Insightful)
In the first case, the author has a license which restricts what you may do with a given piece of software (you may not disassemble it). In the second, the author has a license which restricts what you may do with a given piece of software (you may not sell it without releasing the source code).
This is called "having your cake and eating it, too."
The second case is a matter of an author expressly permitting you, with conditions, to have addition rights with their work that normal copyright would not allow.
And as for a more proper cake analogy: The first case is saying "here's a cake, and don't you pay no nevermind to what's in it, don't be doin none of them dang 'tests' on it either, we know what you want. that'll be $249.99"
The second case is like saying "here's a cake recipe, but if you make cakes with it, you have to give out the recipe too. that's the rules for getting this recipe for free"
Re:GPLv3 (Score:4, Insightful)
GPLv2 guarantees you the right to produce a modified binary that works on some system.
GPLv3, with the TIVO-ization clauses, guarantees you the right to produce a modifed binary that works on the original system.
The difference between those is huge! TIVO complies with GPLv2 (you could build your own TIVO box and install your modified source on it). USDTV seemed to comply with neither of these.
And this new GPLv3 doesn't clear up the GP's points about what is "distribution" (the 2nd GPLv3 draft only adds confusion, defining "distribution" as "conveying" without defining "conveying") - so that definition will still have to evolve via case law in the courts. Sorry FSF, y'all got too focused on fixing TIVO-ization and didn't actually clear up the ambiguities...
Re:Dangerous to use Linux? (Score:3, Insightful)
In the first case, the author has a license which restricts what you may do with a given piece of software (you may not disassemble it). In the second, the author has a license which restricts what you may do with a given piece of software (you may not sell it without releasing the source code).
This is called "having your cake and eating it, too."
The difference is that in the first case, further restrictions than those imposed by copyroight law are added in the license. In the second case, some of those restrictions imposed by copyright law are removed if you agree with the license.
Also, the GPL requirements on the distributor are orthogonal to the question whether the First Sale Doctrine trumps the EULA. The GPL imposes certain obligations on the distributor, while the First Sale Doctrine gives certain rights to the receiver of the good. IANAL, but I'd say that there is no contradiction between demanding that the distributor comply with the GPL at the same time as you ignore a restriction in the EULA that may be unenforceable and trumped by the law.