Slashdot Mirror


USDTV Subscribers Gouged For Linux USB Keys

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."

49 of 191 comments (clear)

  1. Possibility of GPL Validation by MrWGW · · Score: 5, Insightful

    Well, this would be a great opportunity for a lawsuit, instigated by the FSF or another stakeholder in the matter. The flipside of that, however, is that proponents of proprietary OSes would then immediately cite the case as an example of the "dangers" of using Linux.
    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).

    1. Re:Possibility of GPL Validation by Lockejaw · · Score: 2, Interesting

      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).
      Either that, or it becomes a really verbose BSD license. I personally prefer BSD, but I think this would be a Bad Thing.
      --
      (IANAL)
    2. Re:Possibility of GPL Validation by Qzukk · · Score: 5, Insightful

      would then immediately cite the case as an example of the "dangers" of using Linux.

      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.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    3. Re:Possibility of GPL Validation by Chandon+Seldon · · Score: 5, Informative

      Your question: "The GPL has never been tested in court, is it really legal?" is way over-hyped. It originated as FUD from the SCO case. Legally, the GPL is on really solid ground - even moreso than EULAs for commercial software. It's a copyright license. Either the user agrees to it and gets to take actions not normally allowed by copyright law in exchange for whatever terms are in the license, or they don't and are restricted by copyright law.

      But... even if the GPL needed a test case, this wouldn't be it. This case would be about whether $30 was a "reasonable" fee to distribute source code, and given that USB keys are like $15 the judge would probably rule that it's close enough to the cost of media to be OK. Even if the judge ruled that $30 was too much, the penalty would probably only consist of a requirement to charge $25 in the future and refund $5 to anyone who payed $30 and asks for the refund.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    4. Re:Possibility of GPL Validation by Anonymous Coward · · Score: 4, Insightful

      Why does everyone think the USB key contains the source code? It's just how you update the firmware on these boxes. You plug in a USB stick with the new firmware image, power on the receiver and wait a couple of minutes while the new firmware *binary* is written to the flash memory chip. That's just one more binary distribution that warrants a corresponding source offer, which is, in violation of the license, nowhere to be seen and neither is the source.

    5. Re:Possibility of GPL Validation by dch24 · · Score: 4, Informative

      USDTV has been doing a little of both: selling and leasing boxes to customers. But at this point, they are going into their second (or, depending on how you look at it, third) bankruptcy because the CEO and the president of the company have been ... well, doing some shady things.

      Most of the (former) employees of USDTV (full disclosure: I was) were doing what it took to get a decent alternative to cable off the ground. It seemed like a good idea: send digital video over the air on unused bandwidth, capitalize on the switch to ATSC broadcasting, and earn a little revenue with some extra offerings, like PVR, pay-per-view, and some of the most popular cable channels. It was a very limited channel selection (plus all the free HDTV channels), but there were almost no infrastructure costs.

      But the company had a serious problem with "too many chiefs, not enough indians" and after the second round of VC funding, the "chiefs" couldn't drum up any more loans. So now they're shutting down. There are lots of small startups in Utah that fail. It gives Utah a bad name in VC circles.

      Tim Rikers (who does bzFlag) has been in contact with the company for some time, trying to obtain GPL compliance in the form of source code that will run on the HiSense box. If any of you out there would like to sell me your HiSense box, we can probably work out a deal. They're very capable of doing something like MythTV. As far as I know, USDTV has stalled until they're closing the doors.

      And now, they're making you pay $30 to prevent your box from going into "Please Activate" mode, since none of the boxes will receive activations anymore. (Technically, they won't go into "please activate" until the first power outage.) In my opinion, they were in violation of the GPL for selling a GNU/Linux-based system to some of their customers, and now that they're giving the rest of the boxes to the customers (sort of by default), they are still in violation of the GPL. There are no GPL notices anywhere in the system, unless you connect by a serial console (I can give you pinouts, and maybe a password or two) -- then you'll get the login: prompt.

      I don't think a lawsuit is going to do a whole lot of good. But I think if anyone tried to acquire USDTV's IP and sue someone or a website doing hacking on the box, they'd make SCO look like a profitable venture. What is it with Utah businesses?!

    6. Re:Possibility of GPL Validation by sumdumass · · Score: 2, Informative

      Who are you going to suit? The company is closing it's doors. Being that it is a corporation, your not going to go back on the investors or owners or anything like that. You might be able to block the distribution of assets until the firmware source is released but if a hurry isn't put on it, that might even be too late.

    7. Re:Possibility of GPL Validation by init100 · · Score: 2, Funny

      There are lots of small startups in Utah that fail. It gives Utah a bad name in VC circles.

      I guess failing startups may not be the only thing giving Utah a bad reputation in VC circles. There is also a company called SCO...

    8. Re:Possibility of GPL Validation by Chandon+Seldon · · Score: 2, Insightful

      Caldera (and praised for having the best desktop Linux)

      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?"

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    9. Re:Possibility of GPL Validation by sumdumass · · Score: 2, Interesting

      That sounds about right except there might be a loop.

      If they are distributing a patch that isn't GPL and they are only adding it to the existing code soley as the IT staff of the owner of the box, they could claim the use doesn't have to make sure it is compatible because they are not distributing it.

      Nah, I think that would kick in the dirivited works clause of the GPL. I think your right, good call.

      Unless the patch is just a script that changes some settings though an interface built into it. Then I'm not sure if it would be automaticly covered or not. Still, good call.

  2. Ask them nicely, sue them if they don't comply by Anonymous Coward · · Score: 4, Insightful

    It's plain copyright infringement. They wouldn't get away with it if they infringed on Microsoft's copyright. There's no reason to let them get away with it if they infringe on the copyright of thousands of Linux contributors.

    1. Re:Ask them nicely, sue them if they don't comply by Chandon+Seldon · · Score: 2, 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.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
  3. Re:So..... by MrWGW · · Score: 3, Informative

    Specifically its an issue of a service provider exiting a business, after having distributed Linux to people, and the new service providers failing to provide the source code as required by the GPL.

  4. Gouged? by ClamIAm · · Score: 4, Informative

    Perhaps the submitter has never read the GPL, but the license does, in fact, allow you to charge money when people request copies of the code. In fact, for a while Stallman made a living selling copies of Emacs by mail-order; there are plenty of sites that sell CDs of Linux distributions as well.

    1. Re:Gouged? by UbuntuDupe · · Score: 3, Informative

      Yes, but:

      1) The code must be *somewhere* freely available. Profiting off people's ignorance of where to get it for free, is fine. For example, selling Firefox in a regular software box at Best Buy for $35 + sales tax would be within the GPL, as long as you can download it somewhere for free.

      2) If you're charging for the source code you have to provide, it has to be somewhere close to distribution costs.

    2. Re:Gouged? by RealSurreal · · Score: 4, Insightful

      Close but no cigar. 1) There's no requirement to make the source freely available anywhere. You can release software under the GPL and charge whatever you like for a copy. The requirement is that whoever buys a copy from you with a GPL license receives the rights to redistribute it under a GPL license - which means they can then give it away for free (as long as the recipient is bound by the GPL too) 2) Nope. http://www.gnu.org/licenses/gpl-faq.html#DoesTheGP LAllowDownloadFee Oh and Firefox is distributed under the Mozilla Public License not the GPL.

    3. Re:Gouged? by jrockway · · Score: 2, Insightful

      > Oh and Firefox is distributed under the Mozilla Public License not the GPL.

      That's incorrect. Firefox is tri-licensed -- LGPL, GPL, and MPL. You get to pick which one you want.

      --
      My other car is first.
    4. Re:Gouged? by drinkypoo · · Score: 3, Informative

      Apparently you didn't read the link you made, and neither did anyone else. Try actually reading the following:

      [...] "You can charge any fee you wish for distributing a copy of the program. If you distribute binaries by download, you must provide "equivalent access" to download the source--therefore, the fee to download source may not be greater than the fee to download the binary."

      IF you distribute binaries by download, which they did not, you may charge a fee as much as the fee to download the binary.

      Since the binaries were distributed physically, with the product, or physically again, when the people come to your house to do the upgrade, you may not charge more than a nominal amount to cover copying for the source code.

      Nice try, though.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Gouged? by Romancer · · Score: 2, Informative

      From the article: "Cable Communications is coming to subscribers' houses and updating the boxes, but not leaving a USB key" that's a problem right there as they are not getting any copies of the code.

      and second: "ProServ is selling USB keys." are they selling the key with the code on it, or are they selling just a USB drive that stores a key that has been created by the code. As in a compiled file? If it's just a standard USB key, then it only has a file on it that gets verified. not the code or utility to distribute keys.

      If they gave one person the code, then people would be able to generate keys from that code and copy them to USB devices at will and there would be no discussion about this issue. that's how most GPL code becomes: "free to download somewhere" in peoples minds. it's not stated in the actual GPL but it becomes that way since the people that get a copy of the code usually put it up somewhere for others to just download. Instead of buying a CD or other physical copy, that can be charged for.

      It's not really the price that is at issue here, it's about the lack of the code being distributed at all.

      --


      ) Human Kind Vs Human Creation
      ) It'd be interesting to see how many humans would survive to serve us.
  5. You can't be forced to open source your code. by Anonymous Coward · · Score: 2, Insightful

    The GPL is voluntary. You do not have to accept the license. However, if you don't or can't accept the license, you can't distribute the code. If you distribute the code even though you have not accepted the license or don't comply with its terms, you're committing copyright infringement, which is punishable by a bazillion dollars per illicit copy. Alternatively you can settle with the copyright owners who most likely want you to open the code and call it a day. But if you don't want to or can't open the source, you're free to accept a copyright infringement verdict.

  6. Re:W H A T ? by guspasho · · Score: 2, Insightful

    It doesn't. Unfortunately for your question, no one has suggested that it should.

  7. Re:What about other licenses? by AJWM · · Score: 5, Informative

    They couldn't release the code and they couldn't not release the code either.

    The solution to that is to stop distributing anything. If you end up with a warehouse full of settop boxes you can't legally (because of copyright) distribute/sell, that's your tough luck for not doing due diligence on your business plan.

    Same goes for any successors in interest to the defunct company.

    --
    -- Alastair
  8. Re:Who cares? by geekoid · · Score: 2, Insightful

    Many people pay over 100 bucks a month on TV. There are people that have satallite AND cable.

    Seemsd like a waste to me, but a lot of people do it.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  9. Re:It's too bad USDTV went under... by ReverendLoki · · Score: 3, Informative

    It's called an "ilo SDTV", the "sdtv" being some bastardization of HDTV that means "ATSC tuner with a plain old tube that displays 600 lines per second instead of 500"

    Actually, it means "Standard-Definition Television", which is just the plain-old 480i you've always been getting over the air. It's just given a shiny new acronym so the local electronics store can still sell them alongside all them fancy HDTVs and such.

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  10. The GPL is irrelevant to its usability for OTA by Edward+Kmett · · Score: 3, Interesting

    Ok. I'm as much of an open source advocate as anyone, but I'm not sure I see what all of the hubbub is about or believe the proposition that this upgrade should be free.

    Company makes a box that happens to run linux as the base OS. They should therefore redistribute any changes they make to the GPL'ed code they run. That I get.

    What I don't see is how the GPL being involved in some of the software on the firmware entitles the people who bought the hardware to anything involving software that they used for the TV tuner portion of the box.

    In one of the links they mention that they used the following bits of GPL'ed software:

          Linux kernel version 2.4.18
          glibc version 2.2.4
          libpthread version 0.9
          busybox version 0.60.0
          GNU tar 1.13.19
          gzip version 1.3

    None of those, with the possible exception of the kernel would they have needed to modify to do what they were doing.

    They went out of business, and they let people who were former subcontractors give away/sell the information needed to update the system so the end user can continue to use the hardware in some fashion.

    I just don't see the relevance of the fact that some of the software is GPL'ed to the discussion at hand. You could argue that they need to make available a disk with the code for the GPL'ed stuff that they ran, but they are out of business, so good luck with getting them to honor that.

    However, what is at stake is the ability to use their box to receive OTA signals. None of those packages deal with that. You can make a case that since they closed down they might want to try to give away their service to soften the blow, but the GPL issue is unrelated.

    If I ran a computer company and sold computers preloaded with Linux that happened to come with some fancy proprietary biometric thumb scanner and I went out of business, I wouldn't spontaneously owe every one the source for some user-space application that controlled the thumbscanner.

    If they modified the kernel, then sure the kernel mods are probably owed to the community. I'll bet that they aren't sufficient to perform all of the box's functions unaided however.

    Without the service provided by this third party you are in possession of your very own Linux box running on funny hardware. The joke is on you. Good luck getting your money back.

    --
    Sanity is a sandbox. I prefer the swings.
  11. Not sure, but.. by Jim+Hall · · Score: 4, Informative

    Looking at the links provided in TFA, it's hard to find the real violation here. For example, the link to HiSense quotes an email (March 2006) from the technical lead at USDTV, responding to a user request for copies of the source per the GNU GPL. He states that he would be happy to put up the files for download via a (web?) server, but they were moving offices and didn't have a box to use. Lame, but looks to be in good faith. Until they could put up a server, the technical lead listed the (unmodified?) software components covered by the GNU GPL:

    • Linux kernel version 2.4.18
    • glibc version 2.2.4
    • libpthread version 0.9
    • busybox version 0.60.0
    • GNU tar 1.13.19
    • gzip version 1.3

    There is then a mention on the site (not part of the email) that the company has since hit financial problems, possibly implying they are going out of business. In fact, USDTV did go under. Technically, a violation of the GNU GPL for not providing the source on demand, but would be hard to bring to court. Especially since USDTV is out of business now. :-P

    Under the GNU GPL, a developer who modifies or distributes code under the GNU GPL is required to redistribute the source code, "for a charge no more than your cost of physically performing source distribution". However, a program that is separate from the GNU GPL code (for example, a program that runs on top of the Linux kernel) is not bound by the GNU GPL. So they company isn't bound by anything to release code or binaries to their subscriber box software. And in any case, $30 could be a reasonable fee for physical distribution, since they are sending a field rep to your home - if they were distributing source code to the GNU GPL components (which doesn't appear to be the case.)

    Reading through the (long!) forum, the company appears to be distributing an updated kernel and their own subscriber box software updates - from a USB "key" (I assume a USB fob or somesuch.) Forum members report they haven't been able to read the USB key on a PC. I didn't go through all 19 web pages of comments, but I didn't see anyone complaining about trying to get the source code.

    So after much searching, it appears the submitted article is someone complaining they aren't getting upgraded TV software for free, and using the GNU GPL as leverage in their argument. Am I missing something???

    1. Re:Not sure, but.. by Andy+Dodd · · Score: 3, Interesting

      Also, while the above components may be GPL, there are two other issues:

      a) Nothing requires you to provide binaries on demand. Still, any time binaries ARE provided, source for those components must be provided, and there HAS been a violation here.

      b) Just because the kernel and glibc are GPL doesn't mean that there aren't any closed-source applications. HiSense could comply with the GPL and release source code for all GPL components and anyone wanting to update their system would likely still be SOL because the update is for a closed-source application that runs on the box.

      --
      retrorocket.o not found, launch anyway?
  12. flaunting-the-GPL dept.? by Simon80 · · Score: 2, Informative

    flouting the GPL! FLOUTING!

    1. Re:flaunting-the-GPL dept.? by 26199 · · Score: 3, Funny

      Hey, if you've got it, flout it.

  13. correct me if I'm wrong... by Secret+Rabbit · · Score: 2, Insightful

    ... but isn't the key NOT source code.

    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.

  14. I'm not sure this is the case. by raehl · · Score: 5, Insightful

    Where is the act of infringment?

    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?

    1. Re:I'm not sure this is the case. by dgatwood · · Score: 2, Interesting

      It's the same legal precedent that makes it illegal to hack your rented cable box. It's considered trespassing. If you rent a cable box, you do not have the right to open it up or modify it in any way. As the owner, they have the right to specify what can and cannot be done with their property. Therefore, they are under no legal obligation to aid and abet any action by their customers that would be in violation of their rights as the owners of the property. Indeed, by assisting you in doing so, they would be tacitly agreeing to allow the owners of their cable box to make modifications to those boxes, including those that could harm the box. As such, they cannot realistically be expected to do so.

      It would be the same as a person renting a house demanding that the landlord help him remove an exterior wall. The law says that by transferring a piece of property, you transfer all rights to modify the property as the new owner sees fit. However, when renting it, you retain the right to maintain the value of that property, up to and including preventing the unauthorized modification thereof. Modifying a cable box could decrease its value to the owner (if the person doing the upgrade screws something up), and thus, they are well within their rights to not allow you to do so.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    2. Re:I'm not sure this is the case. by squiggleslash · · Score: 2, Insightful

      My gut feeling says no, this wouldn't suffice. The receiver maker needs a license to put the software on the receivers, whether they intend to sell them or lease them, much as they'd need a license if they wanted to put a copy of The Matrix on every receiver and sell them or lease them. "Fair use", the usual out that allows us to talk about the GPL not applying to private modifications, does not apply in this case, fair use isn't as liberal as people here tend to think it is.

      The fact that the software has been distributed, whether leased or sold, means it needed agreement to a license. The user was given (whether on the basis of a lease or not) the physical software. They, therefore, under the terms of the GPL, should have been offered the source code. I would be enormously surprised if that isn't the case.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:I'm not sure this is the case. by MoralHazard · · Score: 2, Interesting

      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.

      You make a very tricky argument, here, about exactly what defines "distribution". I believe (correct me if I'm wrong) that you're just drawing a distinction between distribution on machines being loaned/leased to the end user, versus distribution on machines where the end user actually buys the hardware. It seems to me, on face, that both are literally examples of "distribution". But the GPL (and a court, obviously) may support your distinction--the literal meaning might not be the whole story. The text of the GPLv2 (which I just reviewed on the FSF site) doesn't go into detail on this point.

      However, I do believe that you are wrong, specifically because of the nature of how copyright law applies to the acts in question. I'm not sure if my position rests entirely on the literal definition of distribution, though. Let me see if I can construct an argument around this, and you can tell me whether it holds any water.

      1) Consider the hardware boxes to be just another piece of media. Sure, they're functional in their own right, but the have internal flash or memory that carries GPL-governed binary code. In this sense, it seems like the sames rules should apply that govern other forms of media carrying GPL code, such as Linux-based live CDs.

      2) Hypothetically, I could create a binary-only live CD (most of them are, anyway) and hand out copies of it to people. However, let's pretend that I stipulate to everybody receiving a CD that they don't actually own the CDs. I'm not giving them away, I'm just loaning or leasing those physical CDs. Maybe we write out a contract--you accept the CD as a loaner from me, but you're required to return it if I ask or at some designated future time.

      3) It would seem that the contents of the hypothetical loaner CDs are clearly still covered by the GPL, in full effect. Although I could demand the physical CD-ROM back from a user, I couldn't also try to forbid them from making a copy and saving it, or giving it away to other people. In fact, even if we wrote out a special contract to that effect, it would violate the GPL to impose such conditions on them, which would in turn terminate MY rights to re-distribute GPL code in the first place. I couldn't prevent my users from exercising their GPL-given rights without losing my own license over that code.

      4) The requirement that I pass on the right to copy and re-distribute GPL software is only one of the tenets of the license. Another tenet is that I must provide source code, upon request, when I distribute binaries. So in addition to #3, above, I would also be forced to provide the source code for my binary live CD when any of my users asked for it. And furthermore, I would be required to do so at a reasonable cost. If I refuse, or if I try to impose conditions on my users, I lose my own original right to give them the copies in the first place.

      5) Given that the hardware boxes the cable company is handing to its end-users contain binaries of GPL code, it would therefore seem that the users maintain their rights under the GPL to demand the source code from the cable company at a reasonable cost. Unless the cable company meets this requirement, they have no right to distribute the GPL code along with their hardware.

      So... Does that add up? I mean, I would contrast this against the case where the cable company installs edge routers in local neighborhoods that run Linux--those routers being sited in company offices and passing customer traffic as opposed to being given to customers to operate in their own homes. In that case, it would seem as if they were NOT distributing the software, since they maintain direct control over it, and therefore the customers w

    4. Re:I'm not sure this is the case. by Sancho · · Score: 2, Interesting

      Of course this company is held to the GPL. The question is whether or not leasing constitutes distribution. If it does, then this company would be required to release the source per the GPL. If leasing does not constitute distribution, then the company would still be required to comply with the GPL, however as they were not distributing the binaries, they would have no obligation to provide the source.

    5. Re:I'm not sure this is the case. by raehl · · Score: 2, Interesting

      I don't think that adds up.

      You kind of touched on the problem with your argument, but then went past it.

      The receiver is a self-contained unit that runs it's own software. The live CD does not run anything. In order to use the software on the live CD, you have to put it in some other device. And when you do that, you copy the software.

      So, if I 'lease' to you a CD with software on it, and then you run the software on the CD, one of two things is true:

      - My lease to you of my property with the copyrighted software on it either allows you to copy that software, or it does not. If it does, then I have infringed the copyright as I have no license which allows me to allow you to copy the software onto whatever machine you're going to ultimately run it on.
      - My lease to you of my property does not allow you to actually copy the software, ergo, you commit the infringement if you copy it to your machine to run.

      The difference with the receivers over the live CD is that unlike the live CD, where the program must be copied off the CD to run on your computer (even if it's only copied into memory for the purposes of running the program), the program in the receiver only runs on the receiver, which is still my property.

      Let's put this another way. Let's say I create a business where I lease computers. Let's further say that I lease computers with Linux installed. You pay me $100 and I loan you a computer for a month. Am I obligated to give you the source code?

      What if instead of giving you the computer, I have an internet cafe, and I instead charge you $20 to use my computer for an hour. Am I obligated to give you the source code then?

      I'd say no to both cases, and under the same reasoning, would not expect that distributing the source to GPLd software running on leased hardware is required.

      You bring up a good point with the Java applets though - I would argue that in that case, making the source code available is required.

    6. Re:I'm not sure this is the case. by MoralHazard · · Score: 2, Informative

      My lease to you of my property with the copyrighted software on it either allows you to copy that software, or it does not. If it does, then I have infringed the copyright as I have no license which allows me to allow you to copy the software onto whatever machine you're going to ultimately run it on.

      This may be a misunderstanding. My point was that the GPL forbids you from making a lease agreement in the fashion you describe. IF the act of handing over the CD qualifies as distribution, you're breaking the GPL if you refuse to provide source to the end user, contract or no. Remember, the when you accept the terms of the GPL (by copying or re-distributing the licensed work), you're making a promise UPSTREAM, to the guy who owns the copyright on the software. You can't void that promise by making a second agreement, a lease or what have you, with someone downstream to whom you're passing a copy of the software.

      We have to determine first whether there is distribution going on. If an act qualifies as distribution, then the copier has obligations to recipient of the distributed code under the terms of the GPL. That said, I think you have a neat argument here:

      The difference with the receivers over the live CD is that unlike the live CD, where the program must be copied off the CD to run on your computer (even if it's only copied into memory for the purposes of running the program), the program in the receiver only runs on the receiver, which is still my property.
      Let's put this another way. Let's say I create a business where I lease computers. Let's further say that I lease computers with Linux installed. You pay me $100 and I loan you a computer for a month. Am I obligated to give you the source code?
      What if instead of giving you the computer, I have an internet cafe, and I instead charge you $20 to use my computer for an hour. Am I obligated to give you the source code then?

      Your claim is an interesting one: the definition of distribution is tied to the nature of the act of copying--as long as ownership of the media is retained by the entity that made the copy, they aren't really distributing copies.

      But WHY should this be the case? As I pointed out earlier, the literal definition of distribution is to turn copies over to the control of other people, regardless of who owns the media. I doubt NetFlix claim that since they still own all the DVDs they're mailing to people that they're not "distributing" anything. This may not be legally accurate, but you don't provide any reason for why your definition of distribution is better than the literal one.

      I would suggest that the spirit of the GPL also comes into play, here: in order to get some benefit (i.e., using GPL software as a basis for your company), you should have to give something in return (i.e., provide the same opportunities to others). With leasing, you are actually creating a copy in order to install the software on each of the machines you lease out to your customers, and you are actually turning it over to them. Why should you be allowed to reap the benefits of copying/redistribution, which you would otherwise be forbidden from doing, without any price?

      And I don't know how legally valid this is, but version 3 of the GPL actually replaces the term "distribute" with words such as "propagate" and "convey". According to Eben Moglen, who wrote both versions 2 and 3, this change is intended to answer the type of question that we're debating here. In fact, most of the changes from version 2 to version 3 are intended to shore up potential loopholes in wording and practices that might allow an unethical person or company to cheat. That doesn't mean they ARE loopholes--nobody's admitting that the GPL version 2 doesn't include your leasing company, or even your internet cafe, in the definition of distribution. It's just that they're trying to make it MORE explicit in the future. Check out the

  15. Stop right there by westlake · · Score: 2, Insightful
    Salt Lake City-based USDTV discontinued their service. USDTV used the Hisense DB2010 as subscriber boxes, with Linux based firmware [CC]. 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 [CC] is coming to subscribers' houses and updating the boxes, but not leaving a USB key. ProServ [CC] 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.

    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?

  16. Dangerous to use Linux? by AP2k · · Score: 2, Informative

    I cant see what the problem is with using other's works and having to abide by the terms set forth by the author. "If you want my help, you are going to do it this way" is what it amounts to. Linux devs dont just throw their code out under GPL for shits and giggles.

    I dont see it as a danger, but rather a very stern warning that you abide by the author's license terms if you use their work. If you have something trade secret-related that you cant just hand out to anyone that wants it, you can code it yourself.

    1. Re:Dangerous to use Linux? by init100 · · Score: 2, Informative

      Using your logic, why don't Linux hippies stop reverse engineering closed software when they see the "Do not disassemble" clause?

      I don't think reverse engineering network protocols or file formats (which is mostly what the reverse engineering done by the "Linux hippies" is all about) can be counted as disassembling the software. Disassembling the software is just that, applying the reverse of the process of the assembler, to produce an assembly file from the binary. This is rarely, if ever, done to reverse engineer network protocols or file formats.

    2. Re:Dangerous to use Linux? by Dun+Malg · · Score: 2, Informative

      Using your logic, why don't Linux hippies stop reverse engineering closed software when they see the "Do not disassemble" clause?

      Or is it another case of double standards? "Do what we want, not what they want!". Because "do not disassemble" clauses are an unenforceable crock of shit. Doctrine of First Sale says that you can do whatever you like with a product you've purchased, including open it up and look inside. On the other hand, using GPL'd software in a product you're selling carries a definite contractual burden, as you need to comply with the license the author(s) provide the GPL'd code to you under. Venture capitalists are free to hire a bunch of programmers to reverse engineer all that GPL software and create their own proprietary version of it, just as "Linux hippies" do with proprietary stuff. You obviously don't understand how any of this works. Maybe you should talk less and read more.
      --
      If a job's not worth doing, it's not worth doing right.
    3. Re:Dangerous to use Linux? by neomunk · · Score: 2, Insightful

      Doctrine of First Sale says that you can do whatever you like with a product you've purchased, including open it up and look inside. On the other hand, using GPL'd software in a product you're selling carries a definite contractual burden, as you need to comply with the license the author(s) provide the GPL'd code to you under.

      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." No, the first case is a matter of a company trying to end-run around already existing laws that deal with the topic, at least as it applies to your analogy.
      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"
    4. Re:Dangerous to use Linux? by trianglman · · Score: 3, Informative

      Actually, no. (obligatory IANAL clause)

      Doctrine of First Sale (or at least the important part in this issue):

      In 1997 in Novell v. Network Trade Center 25 F. Supp. 2d 1218 (C.D. Utah 1997)[2] purchaser is an "owner" by way of sale and is entitled to the use and enjoyment of the software with the same rights as exist in the purchase of any other good.

      This would include taking it apart to see how it works.

      On the other hand, taking the whole piece of software, or a significant piece of it, and selling it as if it were your own is a copyright infringement the same as copying a page from a book and saying it is your own work, thus where the GPL comes in. GPL gives limited allowance to 'infringe' on the copyright, as long as you follow few rules, without contacting the original authors.

      --
      Clones are people two.
    5. Re:Dangerous to use Linux? by init100 · · 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 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.

  17. GPLv3 by SanityInAnarchy · · Score: 2, Informative

    Are the judges and lawyers who eventually decide and argue these matters going to be aware of these extremely fine technical distinctions?... Lots of uncertainty, here, as far as I see it.

    Believe it or not, GPLv3 is designed to resolve exactly this kind of issue. It's designed to be much clearer about what is and isn't allowed.

    Of course, a lot of people don't like this, because they can get away with certain things that the GPLv2 allows, that it wasn't intended to. Tivo-ization is the perfect example -- the GPLv2 was never meant to allow you to see source code, but not be able to produce a modified binary that works. If, when it was being drafted, they had considered this a real threat, it would have been written the way GPLv3 is today.

    Which, I believe, does require that GPL-derived web apps be distributed with their source code in full -- meaning if you visit such a website, there should be a download link somewhere.

    --
    Don't thank God, thank a doctor!
    1. Re:GPLv3 by kscguru · · Score: 3, Insightful
      the GPLv2 was never meant to allow you to see source code, but not be able to produce a modified binary that works. (emphasis mine)

      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...

      --

      A witty [sig] proves nothing. --Voltaire

  18. You're making up a 'fact'. by raehl · · Score: 2, Interesting

    The fact that the software has been distributed, whether leased or sold, means it needed agreement to a license.

    But no distribution (giving a copy to another party) has taken place. Only *COPYING* has taken place.

    And it is obvious that the GPL *MUST* allow copying without distribution. If it doesn't, we're all violating the GPL any time we copy the program from one computer to another without also copying the source.

    (It would seem that at least the GPL statement If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. permits copying without distribution - as if you start with a program and source code, whatever access allowed you to copy the executable would also necessarily allow you to copy the source code.)

    So, while you're correct that the act of copying means the receiver maker either has accepted a license OR is infringing the copyright, the GPL permits the copying.

    So yes, they've accepted the GPL, but no, copying the program didn't violate it.

    1. Re:You're making up a 'fact'. by raehl · · Score: 2, Interesting

      They distributed the boxes with software on them, and they distribute the software on USB-keys (when you pay for them).

      Again, copying the software onto their own hardware isn't distribution. It's copying. The receiver is a self-contained unit owned in its entirety by one party. Copying software onto your own hardware must be permitted, and giving other people access to the hardware, even if for a fee, does obligate you to give them source code, anymore than you visiting my website obligates me to give you a copy of the source to Apache.

    2. Re:You're making up a 'fact'. by Scarblac · · Score: 2, Informative

      Bullshit, go read the license (http://www.gnu.org/copyleft/gpl.html). It's not that long. It covers copying, distribution and modification.

      Without a license, you do not have the right to copy a work copyrighted by someone else. The GPL is the only thing that gives you the right to copy, modify or distribute Linux. Therefore, you need to abide by its terms, even if you only copy it.

      Saying that means you must also always copy the source is idiotic, since that's not what the license says. But since this is commercial copying and/or distribution of a binary, they must choose to adhere to either 3a or 3b - accompany with the source, or a written offer to give any third party the source for a fee no bigger than the cost of physically distributing it.

      Since that's for any commercial copying, and to any third party, it doesn't matter at all whether it's leased or bought.

      --
      I believe posters are recognized by their sig. So I made one.