Slashdot Mirror


Expert Says Cisco's iPhone violates GPL

Stony Stevenson writes "Even while Cisco Systems is suing Apple for violating its iPhone trademark, an open-source enthusiast is accusing Cisco itself of infringing copyright in the same product. From the article: "Cisco has not published the source code for some components of the WIP300 iPhone in accordance with its open-source licensing agreement, said Armijn Hemel, a consultant with Loohuis Consulting and half of the team running the GPL Violations Project, an organization that identifies and publicizes misuse of GPL licenses and takes some violators to court."

18 of 193 comments (clear)

  1. What an effing minefield by Kris_J · · Score: 5, Insightful

    Business and innovation are getting completely strangled by all this IP rights cr^H^H stuff. Is it actually possible to produce anything without setting yourself up to be sued by someone who better understands how the law "works" than you? It's gotten to the point where any business needs a lawyer first, and accountant second and a functional business model an optional third. Can anyone identify the date that making products ceased to be about how good your product was and became more like a poker game where you win if you can raise the stakes higher than the other players can afford?

    1. Re:What an effing minefield by wall0159 · · Score: 4, Insightful

      While I basically agree with your comment, I don't really think this is the time to make it.

      I haven't RTFA but, in general, if someone gives you something with conditions then it's reasonable to expect you to understand and honour those conditions - otherwise, don't take it in the first place!*

      In this case, Cicso has (according to the summary) used GPL code, and hasn't fulfilled it's share of the bargain. It doesn't sound like a business "getting completely strangled by ... IP rights" to me!

      *I think the GPL is different to an EULA... (my personal bias shining through)

    2. Re:What an effing minefield by robotninja · · Score: 3, Interesting

      The answer to this question depends on whether you choose the date the law was passed (October 19, 1976 ) or the date that it went into effect (January 1, 1978): US Copyright Act of 1976.

      Yes, I realize Cisco's suit is about trademark, and not copyright; however, Larry Lessig goes into great detail in most of his writings to explain why the complete redirection in copyright law in 1976 laid the groundwork for such backwards and insane laws as the Sonny Bono Copyright Term Extension Act and of course, the notorious DMCA, among others.

      Interestingly enough, as a law professor and lawyer, one of Lessig's proposed solutions is to "fire all the lawyers"...

    3. Re:What an effing minefield by rnapier · · Score: 5, Insightful

      Note all the parts of the article, however:

      * The article misrepresents the GPL by stating: "The GPL license requires the company to publish the code that it develops for the phone." This is not true; GPL requires that modifications to GPL code be released, not that code developed for a GPL platform be released. Such confusions are exactly why it is a minefield out there. Even if you're in compliance, you get accused of not being so.

      * Hemel has not actually identified any code that is in violation (according to the article, though it also says he's identified the MTD as being in violation). As he says, "I'm not going to do their work for them." But without some clear identification, this becomes a fishing expedition. He says "you're not in compliance" and /. expects the company to prove the negative. Minefield #2.

      * Cisco, as noted by the article, was "very open to his report, [Hemel] said. The company subsequently fixed omissions on a few products that Hemel identified." Every indication is given in the article that Cisco has worked with Hemel in good faith to ensure GPL compliance. This is very different from Apple's announcement of an apparently violating trademark while literally in the middle of negotiations over whether they could use it. Regardless of the merits of either, comparing the two is absurd. They have nothing in common except a vague "IP violation" umbrella.

      * As Hemel notes in the way of a hunch, large companies often acquire code from partners, acquisitions, and contractors. Ensuring that none of these sub-parties has violated GPL is a significant burden, and in most cases impossible to do 100%. Minefield #3. Companies should be judged for their good faith in these situations and particularly how they react when problems are discovered. Nothing in this article indicates that Cisco has behaved except in good faith.

      The original poster was quite correct that the GPL is a minefield. The fact that you often know when you're entering it (unlike software patents) does not remove the minefield. The only way to avoid the minefield is to completely avoid GPL platforms and code, or to GPL absolutely everything you produce. If you wish to work somewhere between those two poles (which Linux seems to encourage), then there are going to be some legal issues to watch out for, and legal issues that don't have really clear answers because the GPL is unlike any other "license agreement" that came before.

      The good news is that the GPL creates exactly the kinds of problems for propriety-software companies that RMS wanted it to cause. The bad news is the the GPL can be a bit of a minefield for proprietary-software companies.

    4. Re:What an effing minefield by simm1701 · · Score: 3, Informative

      Just an adendum to your points... its not just modified GPL code that you need to release. Its also the code of derivative works.

      Its defining derivative (which differs between the LGPL and the GPL and also how you link to libraries) which is the other mine field.

      In general if you dynamically link LGPL libraries or system call to binaries of either type you are safe from having to release your own code as GPL/LGPL

      One of the other compliance issues that is uner the GPL that is trrival to meet but many companies fail to do so is that when you do use GPL code in such a way that you dont have to release your own code, you still have to aknowlege the use of such GPL code and either provide a copy of the source code in machine readable form or provide instructions to where it can be found (a few links to sourceforge is usually sufficient) since this is trivial to do it understanably annoys FOSS advocates when companies fail to do so.

      --
      $_="Slashdotter";$syn="OTT";s;..;;;sub _{print shift||$_};s!ash!Perl !;s=$syn=ack=i;tr+LLEd+BLAH+;_"Just Another ";_
  2. no suprise by Lumpy · · Score: 4, Interesting

    It was like pulling teeth to get the wifi accesspoint/routers GPL code released a few years ago, this is standard operating proceedure by Cisco. I remember the foaming at the mouth all over slashdot about that.

    Anyways the WIP300 sucks bad.

    --
    Do not look at laser with remaining good eye.
  3. Single page version of the article by Anonymous Coward · · Score: 5, Informative

    Can be found here. No ads, pleasant to read, all on one page! (Posting AC to avoid karma whore accusations).

    1. Re:Single page version of the article by debilo · · Score: 5, Funny
      (Posting AC to avoid karma whore accusations).

      Oh, get out, you're such a sympathy whore.
  4. Re:Richard Stallman... by PunkOfLinux · · Score: 5, Insightful

    Ok, to clarify things - the only thing they HAVE to give people is any modifications to programs licensed under the GPL. If they modified the Linux kernel running on this (which they most likely did) then, yes, they need to release that. If they wrote a custom app for this purpose, that does not need to be released.

  5. Re:Oh Slashdot by Ungrounded+Lightning · · Score: 3, Insightful

    When Cisco sued Apple, there was no way Apple was guilty...
    When an open-source "expert" announces that Cisco "might" have violated the GPL...


    Please note that Slashdot posters are not a homogeneous mass. Different claims are typically posted by different people with different opinions.

    Also please note that there are different types of "IP" involved in the differing infringements:
      - In the Apple-Cisco dispute it is a trademark issue. (Last news I saw makes it look like Cisco had let the trademark lapse - which leaves it open to the next claimant.)
      - In the Cisco-GPL dispute it is a matter of whether Cisco failed to abide by copyright licensing terms, along with an attempt by a party to whom those terms grant rights to require performance.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  6. Re:Big Company by Whiney+Mac+Fanboy · · Score: 4, Interesting

    The iPhone trademark is what is at issue between Cisco and Apple. That has nothing to do with IP or Copyright,

    Meh, Large companies would have you believe that Trademark, Trade Secrets, Copyright & Patents (along with other intangible or government granted monoopolies) all fall into the 'Intellectual Property' basket.

    Oh, and I could have been referring to either Cisco or Apple with my comment. Apple's complained about people violating it's copyright/look'n'feel/whatever countless times. But seems to have absolutely no problem violating some small guy's copyright

    --
    There are shills on slashdot. Apparently, I'm one of them.
  7. Re:Anyone who owns one of these phones ask? by Ungrounded+Lightning · · Score: 4, Informative

    Did anyone who purchased one of these phones ask for the source? They don't have to put the source out there for the general public.

    Actually, according to the GPL, if they don't provide the source with every phone then they DO have to give it to anyone in the general public upon request - until they've sold or otherwise "distributed" the last one and for a period of time thereafter.

    (You never know who ends up with the black box containing the object code, after all, and writing the GPL so it would require successive box owners to maintain a paper trail of ownership in order to obtain the source code would have subverted its purpose.)

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  8. Re:Of course by gnasher719 · · Score: 3, Interesting

    '' At the end of the day, the only way in which different cases of infringement are fungible is if opposed parties agree to trade suit cancellations. They could hammer Cisco as hard as they want and Cisco's position vis-a-vis Apple would (probably) not be affected at all. ''

    The copyright holders could sell lets say 50 percent of their copyrights to Apple, which might be happy to pay a generous amount of money for them to have some ammunition against Cisco. The original copyright holders get a nice amount of money, they can still sue Cisco for copyright infringement, and Apple can do the same. The GPL status of the software wouldn't be affected. (If they sold _all_ copyrights to Apple, the software would be just as free, but only Apple could sue any GPL abusers, and of course Apple could build a non-free version itself).

  9. Re:Richard Stallman... by Constantine+Evans · · Score: 3, Informative

    In my interpretation, that doesn't mean any third party in general, it means any third party that the party with the written offer chooses. An arbitrary third party wouldn't have the written offer, and so wouldn't be eligible.

    The idea behind that section is that someone who has a binary under the GPL but hasn't requested the source shouldn't be required to acquire the source before distributing the binary. With that section, they can distribute the binary and rely on the original provider to provide the source directly.

    Nevertheless, this has come up a few times before on Slashdot. For example, see
    http://slashdot.org/comments.pl?sid=212978&cid=173 29266 - as can be seen, the interpretation of that particular point is quite difficult. I am considering asking the FSF directly about the section.

  10. Maybe true, but irrelevant by tkrotchko · · Score: 3, Insightful

    The article implies a linkage that isn't there.

    iPhone is a trademark dispute between Apple and Cisco.

    The other appears to be a vague accusation the Cisco didn't abide by a usage restriction (not related to apple in the least) on source code....

    I mean, perhaps this could be considered ironic, but irony is not a legal challenge and in any case, even if the GPL has been violated, it has no bearing at all on the case between Apple and Cisco.

    I'm not a big fan of the way either of these companies use their legal teams, but you don't have to be a lawyer to realize that Apple is wrong here. They gave away their entire negotiating position when they announced iPhone before securing the rights to the name. They either pony up what Cisco wants, or choose a new name. It's not that difficult.

    --
    You were mistaken. Which is odd, since memory shouldn't be a problem for you
  11. Re:Anyone who owns one of these phones ask? by hp48 · · Score: 5, Informative

    Did anyone who purchased one of these phones ask for the source? They don't have to put the source out there for the general public.

    Actually, according to the GPL, if they don't provide the source with every phone then they DO have to give it to anyone in the general public upon request - until they've sold or otherwise "distributed" the last one and for a period of time thereafter.


    Actually, according the the GPL, they don't. They just have to give it to anyone who uses the binary. However, most of the time anyone in the general public could be a user, but that's not assured.

    http://www.fsf.org/licensing/licenses/gpl-faq.html #GPLRequireSourcePostedPublic>
    and
    http://www.fsf.org/licensing/licenses/gpl-faq.html #WhatDoesWrittenOfferValid>

  12. GPL is NOT an agreement by SLi · · Score: 4, Informative

    Argh. When will people learn this? The GNU GPL is not a "licensing agreement", it's a license. It's a one-sided declaration that gives to the licensee rights they would not otherwise under the copyright law have (ie. the right to redistribute the software under some conditions, spelled out by the GPL). It doesn't demand anything at all in exchange, and the licensee does not need to "agree" to it or "accept" it for it to have effect (and not accepting it wouldn't make much sense, since it only gives additional rights).

  13. Sorry, wrong: by Ungrounded+Lightning · · Score: 4, Insightful

    ... the only thing they HAVE to give people is any modifications to programs licensed under the GPL. If they modified the Linux kernel running on this (which they most likely did) then, yes, they need to release that. If they wrote a custom app for this purpose, that does not need to be released.

    Sorry, not true.

    If they have a stand-alone part that is unchanged they still have to distribute the source of it.

    If they have stand-alone part they modified they have to license their modifications under the GPL and distribute the whole part's source (not just the deltas).

    The only thing they can avoid *GPLing and distributing source for is a stand-alone part that they wrote from scratch - and then (since it's a single software load rather than a distribution containing clearly separable components) only if the underlying code was licensed under the LGPL rather than the full-blown GPL.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way