Slashdot Mirror


US Navy Under Fire In Mass Software Piracy Lawsuit (torrentfreak.com)

An anonymous reader quotes a report from TorrentFreak: In 2011 and 2012, the U.S. Navy began using BS Contact Geo, a 3D virtual reality application developed by German company Bitmanagement. The Navy reportedly agreed to purchase licenses for use on 38 computers, but things began to escalate. While Bitmanagement was hopeful that it could sell additional licenses to the Navy, the software vendor soon discovered the U.S. Government had already installed it on 100,000 computers without extra compensation. In a Federal Claims Court complaint filed by Bitmanagement two years ago, that figure later increased to hundreds of thousands of computers. Because of the alleged infringement, Bitmanagement demanded damages totaling hundreds of millions of dollars. In the months that followed both parties conducted discovery and a few days ago the software company filed a motion for partial summary judgment, asking the court to rule that the U.S. Government is liable for copyright infringement. According to the software company, it's clear that the U.S. Government crossed a line. In its defense, the U.S. Government had argued that it bought concurrent-use licenses, which permitted the software to be installed across the Navy network. However, Bitmanagement argues that it is impossible as the reseller that sold the software was only authorized to sell PC licenses. In addition, the software company points out that the word "concurrent" doesn't appear in the contracts, nor was there any mention of mass installations. The full motion brings up a wide range of other arguments as well which, according to Bitmanagement, make it clear that the U.S. Government is liable for copyright infringement.

20 of 121 comments (clear)

  1. Oh, no! by hey! · · Score: 5, Funny

    Hundreds of millions of dollars? Where will the DoD get that kind of money?

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    1. Re:Oh, no! by umghhh · · Score: 2

      Yes that is a real worry. But they can claim that the German SW was flawed on purpose to hide CO2 footprint. That would fix it.

    2. Re:Oh, no! by Anonymous Coward · · Score: 5, Funny

      Wait - the copyright lobby have yet to peer-review the maths involved. This will be complex because the plaintiff is German and not American, but I believe the formula they apply is something like:

      sue_for_losses = (actual_losses + made_up_losses) * 1000

      Then, because it's a German company:

      america_first_weighting = 0.0001
      sue_for_losses = sue_for_losses * america_first_weighting

      Next up comes the political stuff:

      sue_for_losses = apply_secret_sauce_no_one_understands(sue_for_losses)

      By the time all that gets done, the German state will end up bailing out Bitmanagement so it can be pay the US government for misuse of their equipment.

    3. Re:Oh, no! by AmiMoJo · · Score: 2

      They could try piracy. Sail the seven seas drinking, murdering and looking for booty, then selling it on the black market.

      Better than the most heinous crime of software piracy.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    4. Re:Oh, no! by retchdog · · Score: 2

      yes, this is the us military, you're right about that, and they'll throw whomever they need to under the bus, and if they complain about being thrown under the bus, they'll get a courts-martial instead of a warm and fuzzy civil trial. roflmao

      --
      "They were pure niggers." – Noam Chomsky
    5. Re:Oh, no! by henni16 · · Score: 4, Insightful

      Maybe they can get the RIAA to do the math:
      150k of statutory damages per willful infringement multiplied by 100k infringements makes 15 billion in statutory damages.

      Which leads to the question of who do you call to repo a carrier group.

  2. How does it taste? by Anonymous Coward · · Score: 4, Funny

    As an American I hope this will teach the Us government to stop being douchebags about copywrite infringement. And about most everything else too.

  3. Been there, done that by Anonymous Coward · · Score: 2, Interesting

    Heh. I can remember, many moons ago, when Siebel sold very expensive licenses for MRI software on SGI hardware. They were quite miffed to discover that I had ported VNC to SGI IRIX, in order to allow clinicians to access the box remotely and use the software rather than buying each their own SGI Indigo box each with their own license. That was in.... dear lord, that was back in 2000. They were *miffed*, but I couldn't find anywhere in the licensing that forbade remote access.

    Now, I would *not* want to permit that on Navy computers, because remote X sessions with the fairly poor non-"/bin/login" password handling of VNC is.... well it's dangerous, and can leave idle non-managed sessions lying around for crackers to abuse. But it can be really useful, especially for clients that don't have a built-in X server. And yes, X servers and clients have the names backwards.

    1. Re:Been there, done that by rickb928 · · Score: 4, Interesting

      Many more moons before that, when you were limited to dialup connections, we set up tunnels for authorized clients, RADIUS and all. The stated purpose was to enable radiologists about 100 miles away to access the Solaris machines and read radiology images for diagnosis.

      Imagine our surprise when we saw connections (logging ANI for auditing) originating from India.

      Imagine further surprise when Sun tried to shut this down, claiming they were constrained from delivering the software offshore due to encryption and munitions regulations.

      Several lawyers later they went away, very disappointed in missing out on not only the licensing for few hundred thousand new end-users, but also for the licensing they missed out on when we figured out how other hospitals could share imaging and use our teleradiology services for the cost of a long-distance call. Which got cheaper when we partnered with a nascent DSL provider (NOT the ILEC, mind you), and they got AOL on the side.

      Good times. that odd adapter with the 02DEADBEEF20 MAC address drove me crazy for a few hours, though. And the infiltration of Ethernet into my pristine Token-Ring network, with all the joy that brought.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
  4. Remember Harvard Graphics? by Anonymous Coward · · Score: 3, Informative

    The Army bankrupted this company due to rampant piracy of their software.

    That's the origin of the US GOV'T RESTRICTED RIGTS in the (c) messages.

  5. Why GFS is misleading. by Anonymous Coward · · Score: 5, Interesting

    Delightfully missing in TFS is that a library, not linked to any executable software, was on a common desktop image. Not an executable, much less a runnable installation.

    1. Re:Why GFS is misleading. by DCFusor · · Score: 2

      It's sad that it's a legal issue - not one that involves fairness, honesty, justice or any other thing the legal system wants us to believe.

      --
      Why guess when you can know? Measure!
  6. why no, I didn't RTFA, why do you ask? by Thud457 · · Score: 3, Funny

    Piracy?
    In the Navy?

    That's a serious problem.
    YAAAARRRRR!

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

  7. Obligatory Russian Reversal? by Clueless+Nick · · Score: 3, Funny

    In Soviet America, the Navy are the Pirates?

    --
    Chat with other atheists http://secularchat.org
  8. Re:Two points... by Gilgaron · · Score: 3

    Its probably just some lame program for training that got stuffed into the standard system image. Mission critical stuff probably only resides on individually validated systems.

  9. Re:phone-home software in the navy by Anonymous Coward · · Score: 3, Informative

    I assume that is how they know the navy had 100,000 installs of their software.

    During the lawsuit the Navy stated they believed they had a license that would allow them to include this software in their standard PC deployment image and that the only restrictions were how many copies were running or in use at the same time.

    During the court case, the Navy admitted it has deployed that particular standard system image hundreds of thousands of times since the software inclusion.

  10. Re:phone-home software in the navy by afidel · · Score: 4, Informative

    Incorrect. They learned the scope of the problem through discovery and adjusted their claims to account for the much more massive copying (the original scope was just the single site where the trial happened). The DoD very much does not allow call home.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  11. Estimates by bestweasel · · Score: 5, Insightful

    "We need to scope out this Bitmanagement deployment, Lieutenant. How many PCs will need it?"
    "Several hundred thousand Sir".
    "That's a lot of licenses, is there any way we can get by with fewer?"
    "Well Sir, we could switch to a concurrent licensing model."
    "How many would we need then?"
    Scribble, scribble.
    "I make it 38 Sir."
    "That sounds better, we'll do that."

  12. Re:Reinterpreting license agreements by Immerman · · Score: 3, Interesting

    I'm curious, how do you get from "bought software for use on 38 machines" to installing it on 100,000 while "the number of active licenses doesn't exceed the ones it bought"

    --
    --- Most topics have many sides worth arguing, allow me to take one opposite you.
  13. Re:Now vee... by Calydor · · Score: 2

    Over there, on the other side of the Atlantic.

    --
    -=This sig has nothing to do with my comment. Move along now=-