Slashdot Mirror


Sony Rootkit Allegedly Contains LGPL Software

Deaths Hand writes "According to this Dutch article the Sony DRM software (or rootkit, if you may prefer) contains code from the LAME MP3 encoder project, which is licensed under the LGPL. However, the source code has not also been distrbuted, hence breaching the license. Here is an english translation of the page." So apparently Sony violates your privacy to create a backdoor onto your machine using code that violates an Open Source license. This story just keeps getting stranger.

623 comments

  1. Uuuuuh by frieko · · Score: 1

    Doesn't the LGPL permit this?

    1. Re:Uuuuuh by Anonymous Coward · · Score: 3, Informative

      they linked it statically (apparently the rootkit consists of a single exe), so no.

    2. Re:Uuuuuh by YA_Python_dev · · Score: 4, Informative
      Doesn't the LGPL permit this?

      No. You can link LGPLed software with proprietary software, but you must still distribute the sources of at least the free software (free as in RMS).

      --
      There's a hidden treasure in Python 3.x: __prepare__()
    3. Re:Uuuuuh by wlan0 · · Score: 5, Informative

      According to the EFF.

      This software is licensed under the so called Lesser Gnu Public License (LGPL). According to this license Sony must comply with a couple of demands. Amongst others, they have to indicate in a copyright notice that they make use of the software. The company must also deliver the source code to the open-source libraries or otherwise make these available. And finally, they must deliver or otherwise make available the in between form between source code and executable code, the so called objectfiles, with which others can make comparable software.

    4. Re:Uuuuuh by Anonymous Coward · · Score: 2, Informative

      Not neccessarily.

      The LGPL allows linking of proprietary software against Free libraries, however you must provide source code for the Free library or a means of getting it and you must "give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License." In addition "You must supply a copy of this License" (the LGPL.)

      The question is if they linked against LAME or just pulled out a pattern string, and at what point it becomes "use" of the library. They still ought to have complied with the LGPL to be on the safe side if you ask me though.

    5. Re:Uuuuuh by DataPath · · Score: 5, Informative

      Small clarification - you're not freed from the requirement to make the code for the lgpl portion available. You don't have to make the source code for the program that links against the LGPL code available.

      No, Sony would have been ok if they had installed a README with their rootkit explaining that their digital rights management solution contained code distributed under the LGPL license, and direct users of the software to a website containing the source code.

      --
      Inconceivable!
    6. Re:Uuuuuh by jellomizer · · Score: 1

      In some ways. While Sony can include the Libraries and Release keep their code private. They probably failed to notified the users that they are using the Libraries that are used under the LGPL License. The LGPL is primary used for libraries because by just calling a library that is Full GPL it would require you to make your application GPL which may be impossible because you may be using a licensed Library for an other section of your application, Causing a major licensing conflict. What the LGPL does is relax on the GPL Zealousness to be used more useful to all developers. But if Sony released their Rootkit without giving the Libraries credits and making public the source for the libraries (Including any modifications they did to it) then they are in violation.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    7. Re:Uuuuuh by Anonymous Coward · · Score: 1

      The dodgy ground has always been LGPL's compatibility with static linking, If LAME is statically linked into the executable, then it's against the license intentions.

    8. Re:Uuuuuh by MadFarmAnimalz · · Score: 1

      I stand corrected. Thanks for the clarification, DataPath.

      Mods please avoid modding up the grandparent.

      --
      Blearf. Blearf, I say.
    9. Re:Uuuuuh by Gabe+Garza · · Score: 1
      Actually, that has a complicated answer that depends on how exactly the rootkit "contains source code" from an LGPL product.

      Basically, the only way that you can use an LGPL-licensed library in your program without getting "tainted" is if your program is designed to work with an unmodified version of the library and is distributed as source code or an unlinked set of binaries.

      If you distribute your program has an executable that's dynamically linked with the library, then you need to include notices saying that you use the library, that the library is covered by the LGPL, supply a copy of the LGPL, etc.

      If your program is statically linked, then you'd need to do all the above AND supply the source code for the library and the object files for your program so that the user could relink it against a modified version of the library if they so desired.

      If you "slice and dice" the library and copy parts of it in your program, then your basically required act as if the library was GPL (not LGPL).

      The LGPL is complicated!

    10. Re:Uuuuuh by ppz003 · · Score: 5, Funny

      $sys$README ?

    11. Re:Uuuuuh by maxwell+demon · · Score: 1
      No, Sony would have been ok if they had installed a README with their rootkit explaining that their digital rights management solution contained code distributed under the LGPL license, and direct users of the software to a website containing the source code.

      What if they had installed a $Sys$README?
      --
      The Tao of math: The numbers you can count are not the real numbers.
    12. Re:Uuuuuh by Randall311 · · Score: 2, Insightful

      Hmm I can't imagine why Sony wouldn't want to deliver their Rootkit back to the open-source community... Let's look at it this way, Sony broke the law by distributing the rootkit at 'DRM software' then they apparently broke the law again by not redistributing their source that they modified from an LGPL project to make the rootkit. I know this is wrong, but I am glad that they didn't give back to the open-source community on this one. I mean, source code to make a rootkit that could infect all the Windows systems out there being freely distributed under the LGPL is enough to make me sick. A worm has already been written without the source code. Just imagine how many rootkit varients would be floating out there if this were open source. Yikes!

    13. Re:Uuuuuh by arkanes · · Score: 1

      If you are distributing a binary linked to an LGPL library, you must provide it in such a way that the LGPL library can be replaced with a modified version. If you're distributing a statically linked exe (which is what Sony is doing), this means you must provide the source for your application. Many LGPL projects have specific exemptions from this clause (which would allow you to distribute static executables of an unmodified library), to my knowledge LAME is not one of them.

    14. Re:Uuuuuh by arkanes · · Score: 1
      This is still wrong - in fact, the LGPL is specifically designed to *prevent* this. Remember that one of the freedoms the LGPL is trying to protect is the right of the end user to modify and customize software. If you link against LGPL source, you *must* distribute your software in such a way that the LGPL portion can be modified and replaced if neccesary. In the case of native compiled applications, that means using a shared library, and *not* statically linking.

      Many LGPL projects contain specific language exempting this condition, as long as you use an unmodified library, and there are serveral "LGPL-like" licenses with the same exemption, but I do not believe that LAME is one of them. Sadly, I can't confirm this as our silly work censorware thinks any site about LAME is for downloading pirated MP3s.

    15. Re:Uuuuuh by ajs318 · · Score: 2, Insightful

      Double-edged swords cut both ways. If the anti-virus people had access to the source code, then they would be able to block its propagation quite easily.

      --
      Je fume. Tu fumes. Nous fûmes!
    16. Re:Uuuuuh by BokLM · · Score: 1

      It's stupid, you can aldready find some rootkits source codes quite easily. Hiding the source for this is not what will prevent people from writting and using rootkits.

    17. Re:Uuuuuh by DigitAl56K · · Score: 1

      Does anyone actually *want* the source code of a root kit to be published online? Then not only will you have viruses masking themselves using XCP, but viruses with this ability built-in. You know how it works..

    18. Re:Uuuuuh by networkBoy · · Score: 1

      You do realise, however, that it doesn't matter one bit if they get away with it.
      Thus I see three options:
      1) Let them get away with it, causing erosion of the (L)GPL
      2) Get someone to sue them (preferably to open their source rather than money as IMHO that will "sting" more)
      3) Geeks of the world unite! and storm your local Sony office (Sales/R&D/Corp HQ/Whatever) and pillage, plunder, and toarch everything.

      In the case of #1 we all loose and Corp wins, #2 makes the law journals, #3 makes international news.
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    19. Re:Uuuuuh by tokaok · · Score: 1

      your following the faulty logic that malicient coders need the source to work with this, already there has been people who have put the sony code to other malicious purposes with out sony giving acces to the source files

    20. Re:Uuuuuh by Anonymous Coward · · Score: 0

      crab people

    21. Re:Uuuuuh by supun · · Score: 1

      Doesn't matter. If they download the source via P2P, the license is automatically removed/voided just like license on ripped music, movies, and software. :)

      The irony. The rootkit to "prevent/spy on" people who are breaking the licensing agreement on the music breaks a licensing agreement on the software used, and is being complained about by people who don't follow the licensing agreement on the music to begin with.

      --
      :w!
    22. Re:Uuuuuh by jonbryce · · Score: 1

      No. Unlike the GPL, you don't have to release your own code as free software, but you must still respect the rights of the code you are copying.

    23. Re:Uuuuuh by coolgeek · · Score: 3, Informative

      Two hours research on various Windows Developer mailing lists will reveal all the answers needed to homebrew your own rootkit, if you have a little bit of savvy. My point is that concealing Windows' numerous design flaws in the hopes of obscuring the many ways to exploit them is not security. Besides, if you think Windows rootkit source isn't already being traded on IRC by many, you are truly naive.

      Even the methodology used by the sysinternals dude, of analyzing the kernel call vector to find the rootkit (by locating addresses pointing outside of the kernel) is nowhere near bulletproof. We're coming up on the 5th inning of the apocalypse of Windows. Soon a Mac will look cheap when you compare it to the time consuming weekly reformat/reinstall cycles that lie just beyond the horizon.

      --

      cat /dev/null >sig
  2. just say no by hector_uk · · Score: 3, Insightful

    now I feel more and more justified for not buying any music until the music industry stops suing their customers.

    1. Re:just say no by Pieroxy · · Score: 2, Interesting

      until the music industry stops suing their customers
      Yes, but this time, it's customers suing them!

    2. Re:just say no by the_xaqster · · Score: 3, Funny

      I am sure there is a "In soviet Russia" joke in there somwhere!

      --
      I'm just here to regulate Funkyness
    3. Re:just say no by emerkel · · Score: 0, Troll

      Yeah that's good, i guess if you want to steal any excuse is a good one! If you aren't willing to follow the 'rules' then you have no right to bitch when someone else decides not to as well.

    4. Re:just say no by maxwell+demon · · Score: 1

      He just said "not buying". He didn't say "stealing" (or "copying", for that matter). I haven't bought any laser printer up to now. Must I now fear to go to jail for stealing a laser printer?

      --
      The Tao of math: The numbers you can count are not the real numbers.
    5. Re:just say no by IMarvinTPA · · Score: 0

      In soviet Russia, DRMS violates copyrights.

      IMarv

    6. Re:just say no by John+Nowak · · Score: 1

      Rather sad that all the music you'd buy comes from the "music industry", isn't it?

    7. Re:just say no by Jaseoldboss · · Score: 1
      Not likely, seen the BBC News website today?

      The global recording industry has launched its largest wave of legal action against people suspected of sharing music files on the internet.

      I wonder when they are going to start suing the record companies then!
    8. Re:just say no by Anonymous Coward · · Score: 0

      Another brain damaged troll who CAN'T FUCKING READ.

    9. Re:just say no by iamacat · · Score: 0

      In Soviet Russia DRM violates YOU!

    10. Re:just say no by mlynx · · Score: 1
      I understand what you are trying to say, but I don't think your choice of words make it clear.

      For example, most people want to buy a car from a member of the "automotive industry", most folks would prefer their doctor participate in the "medical industry", most people, I'd even go so far as to say most of them here on slashdot, have little wrong with the idea of industries, it's when they are abusive or controlled by monopoly powers that people begin to feel cheated, wronged, misled, etc.

      It would probably be better expressed as "music...from the 'music monopoly'".

    11. Re:just say no by hector_uk · · Score: 1

      "Rather sad that all the music you'd buy comes from the "music industry", isn't it?" oh i'm sorry those artists are missing out that 8 cents or so they make a track, if I like a band i'll pay to see them live, heck most of the artists i listen to are dead, i have no qualms buying music from indie labels to help actual struggling bands, it's the major labels who disgust me.

  3. Thank god! by Anita+Coney · · Score: 4, Insightful

    I read about this story days ago. I was hoping it wouldn't get lost. In a way this is even bigger than the root-kit story. You've got to love the irony of stealing code to create a DRM infested ripper!

    --
    If someone says he and his monkey have nothing to hide, they almost certainly do.
    1. Re:Thank god! by Halo1 · · Score: 5, Insightful

      They're not stealing code, they're infringing on the author's copyrights by not respecting the license under which the code is be distributed (in exactly the same way people who "share" Sony/BMG music via p2p etc infringe on Sony/BMG's and the the artists' copyrights).

      --
      Donate free food here
    2. Re:Thank god! by Sepper · · Score: 4, Insightful

      (in exactly the same way people who "share" Sony/BMG music via p2p etc infringe on Sony/BMG's and the the artists' copyrights).

      Not sure about the English language, but in my own we have a saying for this: "Do what I say, not what I do"

      --
      I live in Soviet Canuckistan you insensitive clod!
    3. Re:Thank god! by Anita+Coney · · Score: 2

      You're right, I was trying to be ironic. "Stealing" should have been in quotes to better emphasize my sorry attempt at humor.

      --
      If someone says he and his monkey have nothing to hide, they almost certainly do.
    4. Re:Thank god! by Jesus_666 · · Score: 1, Funny

      No, the grandparent is right: Sony executives have been seen sneaking out of the houses of LAME developers wearing masks and carrying bags with "source code" written on them.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    5. Re:Thank god! by IAmTheDave · · Score: 4, Interesting
      Not sure about the English language, but in my own we have a saying for this: "Do what I say, not what I do"

      Yup, that's right. The thing that kills me is that certain members of our government are busy drafting legislation that would make criminal penalties against copyright infringement harsher, including jail time. No doubt Sony is a sponsor of this bill - or at least the RIAA/MPAA, of which Sony is a member. Yet do you think that Sony would ever be concerned about holding themselves to the same standard? Would they, as a sponsor of this proposed legislation, support the CEO, CIO, chief architect, programmer, or otherwise spending some time in jail for an LGPL or GPL copyright violation?

      The double standard kills me, and in cases like this where Sony's actions are quite simply audacious, I almost start to feel physical anger. I'm tired of being treated like a criminal, and it's really about time that a company like Sony be held responsible for the huge amount of personal and other violations that they have trampled on with this one single action of releasing this software.

      --
      Excuse my speling.
      Making The Bar Project
    6. Re:Thank god! by Tinik · · Score: 0

      We have a word for that, actualy:

      Hypocracy

    7. Re:Thank god! by temcat · · Score: 1

      That thing you mentioned is not a word. But we do have a word "hypocrisy".

    8. Re:Thank god! by hobbit · · Score: 1, Funny


      A system of government in which the people are ruled by a deficiency?

      I think you mean "hypocrisy".

      --
      "Wise men talk because they have something to say; fools, because they have to say something" - Plato
    9. Re:Thank god! by Mr.+Underbridge · · Score: 0, Flamebait
      They're not stealing code, they're infringing on the author's copyrights by not respecting the license under which the code is be distributed (in exactly the same way people who "share" Sony/BMG music via p2p etc infringe on Sony/BMG's and the the artists' copyrights).

      +5, Pedant

    10. Re:Thank god! by Anonymous Coward · · Score: 0
      We have a word for that, actualy:

      And we have a word for that:

      Actually.

    11. Re:Thank god! by heinousjay · · Score: 3, Funny

      It's like an infinite loop of hypocrisy: My god, it's full of piracy!

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    12. Re:Thank god! by Elm+Tree · · Score: 1

      Damnit! I allways suspected them. The Aibo's should have been a dead giveaway!

    13. Re:Thank god! by jedidiah · · Score: 1

      No "punk" has yet felt lucky enough to test it in court. So there are obviously a lot of real lawyers out there that would gladly contradict your assessment of the situation.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    14. Re:Thank god! by Nazadus · · Score: 1

      You're damnded straight I want it to be a criminal offense.
      Why? INNOCENT UNTIL PROVEN GUILTY!
      In a civil suit, it's allot harder to defend yourself.
      In a criminal suit, it's allot harder to convict you.

      Due to the RIAA's previous... mistakes, is it *at all* possible, you are a mistake too? Ladies and gentlemen of the jury, I think you'll find the RIAA can't be truste dand thusly my client can't be convivted for something that can't be reasonably proven.

      So you see, the bill sounds pretty to the $$$ companies, but in reality, it will be *allot* more expensive on their part to prove you did it.

      Now, since it's a criminal matter, police can get involved too.

      I'll openly admit I download movies and songs.
      I'll also openly admit that onces that don't suck, I buy.
      I'm sorry but OVA is just *way* too expensive to buy just to find out I get 3 (if I'm lucky) episodes *and* the show sucks. Sorry hun, ain't cuttin' it.
      I try before I buy.
      *ESPECIALLY* if this is a criminal matter, sue me. I'd love to see the jury's face when they see how much I've bought in the past two years becuase I've found I liked a series. Yeah, the industry loses *some* money, but they make allot more once I find an anime series I really like (and can *prove* I like it versus taking a chance).

      My response: FUCK YEAH, make copyright infringment illegal as a criminal offense. Prove I did it.

      --
      "Do or do not. There is no try." -- Master Yoda (Half man, half muppet)
    15. Re:Thank god! by timeOday · · Score: 1
      in exactly the same way people who "share" Sony/BMG music via p2p etc infringe on Sony/BMG's and the the artists' copyrights.
      Not quite. Sony is selling a product which infringes.

      Sony is more akin to your friendly streetcorner CD and "Rolex" salesman.

    16. Re:Thank god! by Eli+Gottlieb · · Score: 1

      Just what language is that? We have it in English, too.

    17. Re:Thank god! by Anonymous Coward · · Score: 0

      Your version has the same meaning, and is valid English, but the way it's usually said in english is, "Do as I say, not as I do." Just for your info. ;)

    18. Re:Thank god! by Anonymous Coward · · Score: 0

      I think what we need now is a good old fashioned riot. The French seem to be getting their point across.

    19. Re:Thank god! by bhsx · · Score: 1

      I was thinking about this after reading it on Digg. If they want to sue us for, what is it, $3,500US (or $50,000 per the mp3.com suit) per "infraction," can the Lame author do the same? With 20 or so albums out there with the infringing software, let's say about 100,000 (conservative) runs of each album:
      Low End:
      20*10^6*3500 = $7,000,000,000USD
      High End:
      20*20^6*50000 = $100,000,000,000USD
      I'd say let's do everything we can to encourage the LAME author to take this route.

      --
      put the what in the where?
    20. Re:Thank god! by orasio · · Score: 1

      They're not stealing code, they're infringing on the author's copyrights by not respecting the license under which the code is be distributed (in exactly the same way people who "share" Sony/BMG music via p2p etc infringe on Sony/BMG's and the the artists' copyrights).


      They are not stealing code, you are right. It's copyright infringement.
      It's not the same, because they are making a profit off it, and doing it on a great scale. It's not the same to infringe copyrights sharing with others as using other peoples copyrighted works and selling them for a profit.
      It's comparable to making industrial CD copies, and selling them on a store.
      When you distribute a lonely Lame executable binary amongst your friends, or even if you put it on a website or edonkey, for everyone to enjoy, then that would be comparable t what people do with music. Selling it for a profit is much bigger an issue.

    21. Re:Thank god! by Anonymous Coward · · Score: 0

      Reading Digg is like reading a collection of the worst blogs that you can possibly find. I swear the comments at that site make me wonder just how stupid people can get.

    22. Re:Thank god! by WalksOnDirt · · Score: 1

      TechnologyX said:
      'Yeah, because we all know the L/GPL bullshit would hold up in court. "I wanted my code to be freeee but they STOLE IT!!!111"'

      I think that most of our thoughts are more "I wanted my code to be free but they imprisoned it".

      --
      a,e,i,o,u and sometimes w and y (at be if of up cwm by)
    23. Re:Thank god! by Anita+Coney · · Score: 1

      "I swear the comments at that site make me wonder just how stupid people can get."

      What worries me about the future of our planet is that young people seem to like the style of comments over at Digg. Essentially, well thought-out, articulated, and supported opinions are in disfavor. Very scary.

      --
      If someone says he and his monkey have nothing to hide, they almost certainly do.
    24. Re:Thank god! by starm_ · · Score: 1

      No I think Hypocracy as a class of people is an appropriate term in this case.

    25. Re:Thank god! by temcat · · Score: 1

      You mean, a form of government? :-)

    26. Re:Thank god! by klui · · Score: 1

      So those guys are pirates. Pirates I tell you!!

    27. Re:Thank god! by Anonymous Coward · · Score: 0

      It reminds me of the old adage...

      "Do as I say, not as I do"

  4. LGPL by matt4077 · · Score: 1, Insightful

    I believe the LGPL explicitly allows binary redistribution. Howerever, it may still require attribution, and that did not happen in this case. Way to go to break copyright law to prevent others from doing the same. Especially since the LGPL goes a long way towards uses such as this.

    1. Re:LGPL by AndroidCat · · Score: 1, Funny

      "We had to destroy the IP rights to protect them."

      --
      One line blog. I hear that they're called Twitters now.
    2. Re:LGPL by DVega · · Score: 4, Informative

      LGPL requires access to the source code. The only difference with GPL is that LGPL allows linking with non-free (non-?GPL) components.

      --
      MOD THE CHILD UP!
    3. Re:LGPL by cow-orker · · Score: 3, Informative

      I believe you should shut up, stop relying on hearsay and read the license. Section 4 most clearly states:

      You may copy and distribute the Library [...] in object code or executable form [...] provided that you accompany it with the complete corresponding machine-readable source code
    4. Re:LGPL by Omnifarious · · Score: 1

      I do not believe it does. What it allows is a non-GPL program linking to an LGPL library. You must still provide the source code to the library. In fact, the linking must be done in such a way that you can swap out the LGPL library with another that has a compatible interface and have the program use that one instead. This is so you can modify the source to the original LGPL library, compile it and have the original program use the modified version. The LGPL mandates either dynamic linking, or providing a version of the executable that is one big .o file ready to be statically linked against the LGPL library.

    5. Re:LGPL by Tsunayoshi · · Score: 1

      You must still provide the source code to the library

      No, you must make available upon request the source code to the LGPL licensed software, and the code does NOT have to be made available for download. If they want, they can make you write them a letter requesting the source code, and then send you the source code via snail mail if they so choose. All the license requires is that if you distribute the software in binary form, you must make available the source code upon request. And even then, they only have to make available the source to those people who actually received a copy of the binaries.

      If I, as a consultant for a company, write a bunch of code using GPL/LGPL licensed source code and create a binary of that program, the ONLY entity entitled to a copy of that source code is the company to whom I delivered my work to (not withstanding the fact that they paid me to write the code). No one else has any right to the availability of that source code unless they are also provided a legitimately licensed provided copy of that code.

      As far as I can see (IANAL), back with the Linksys router GPL fiasco, Linksys probably would have been completely within letter of the GPL to have required you to send in a copy of the receipt showing that you purchased a Linksys router, thereby proving you had legally received a licensed copy of provided GPL'd code in binary form, in order for you to receive a copy of the source. Of course, since the first person to do so probably would have posted it on the internet anyway, it was quicker just to make the code available on the internet in the first place.

      Any real lawyers here want to validate/refute my reasoning? I am by no means claiming to be a GPL expert, but just looking at it and knowing some legal stuff from some business laws courses, that is what I come up with.

      --
      "Get a bicycle. You will not regret it, if you live." - Mark Twain, "Taming the Bicycle"
    6. Re:LGPL by mpe · · Score: 1

      "We had to destroy the IP rights to protect them."

      Or even: "Our IP rights are important, but stuff anyone elses".
      This kind of thing isn't exactly suprising.

    7. Re:LGPL by angel'o'sphere · · Score: 2, Informative

      First off all, neither the GPL nor the LGPL require you to DISTRIBUTE the source code. They both require you to grant access to the source code.

      The LGPL does not require you to give anyone access to the non-free parts you linked with it. Only if you modify the library itself you are required to give access to the sources of said library, not to the source of the program you link with that library.

      So I don't see why Sony is violating the LGPL here. As you can download the LGPLed library from sourceforge, its freely accesssible, no?

      angel'o'sphere

      P.S. I did not buy CDs since years and since iTunes I don't need any CDs anymore anyway.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    8. Re:LGPL by angel'o'sphere · · Score: 3, Insightful

      forget it, my last comment I mean ...

      I see that modern versions of LGPL want that the source of the library is included with the distributed binary.

      Another reason not to use LGPL code ... why should *I* distribute code that can be downloaded from sourceforge? Or other GNU distributing sites for that matter.

      angel'o'sphere

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    9. Re:LGPL by Omnifarious · · Score: 1

      Umm... Nothing I said contradicts what you say. So, I don't see why you have such a problem here. I didn't say how they must provide it, just that they must. And they must give you a notice of some sort that the source code is there.

      IMHO, that's something that could be tightened up in the GPL and LGPL in a future version. When they were written, the Internet didn't exist, and there were forms of distribution in which including the source as well would be very painful from a space perspective. That's no longer the case, and I think the GPL and LGPL should be updated to reflect that.

      But, as I said, nothing you said contradicts what I said. So, I don't see any particular reason for your argumentative tone. At best, this is a clarification, not a contradiction.

    10. Re:LGPL by BarkLouder · · Score: 0

      Maybe the source is on the CD. Did anyone look?

    11. Re:LGPL by Tsunayoshi · · Score: 1

      I think I was argumentative with the general crowd of people who think that because something has GPL slapped on it, that it is required to be posted publicly all over the world. I got distracted while I was typing and it went downhill. The fact that a happy work day was apparently not in my horoscope doesn't help matters.

      I wasn't being argumentative with your comments perse, so I apologize if it came across that way.

      I personally don't think it needs to be "tightened up", as things are, it is probably just easier and more convenient to post source on the internet if you actually sell the software commercially or allow it to be downloaded anyway. The system works fine as is, at least with respect to this part of the GPL.

      --
      "Get a bicycle. You will not regret it, if you live." - Mark Twain, "Taming the Bicycle"
    12. Re:LGPL by Omnifarious · · Score: 1

      I suspect though that organizations that want to avoid releasing source if they can at all help it will come up with an increasingly byzantine set of hoops that people have to jump through in order to get the source code. None of those hoops will involve money, but they will involve its equivalent, time.

    13. Re:LGPL by KinkoBlast · · Score: 1

      No!

      A. Sony doesn't tell you lame is in there
      b. Sourceforge could go down perminantly any minute now. I doubt it, but it could.
      c. SONY has to distribute it.

    14. Re:LGPL by shotfeel · · Score: 1

      I think the bigger part of the problem is that in order to ask for the source code, one needs to know that its there. If Sony doesn't provide a notice that they're using the LGPL code, wether or not they make the source available in the proper manner is a moot point because nobody would know to ask for it.

    15. Re:LGPL by HermanAB · · Score: 1

      Well, you don't have to use the LGPL or GPL code. You can write it yourself. Or you can buy it from someone else. That is the whole point - play the game honestly or go your own way.

      FIFO: Fit In or Fuck Off.

      --
      Oh well, what the hell...
    16. Re:LGPL by ceoyoyo · · Score: 1

      To me the most important thing that they did not do is give credit to the LAME project. That is in violation of the LGPL. All the discussion about source code is irrelevant because they didn't do the very first and most basic thing that is required by the LGPL.

    17. Re:LGPL by Urchlay · · Score: 1
      >As far as I can see (IANAL), back with the Linksys router GPL fiasco, Linksys probably would have been completely within letter of the GPL to have required you to send in a copy of the receipt showing that you purchased a Linksys router, thereby proving you had legally received a licensed copy of provided GPL'd code in binary form

      Interesting, but raises a few questions.

      If I bought one of these routers used... would the original manufacturer be in any way obligated to provide me source, or does the seller have to? Seems like it'd be the seller to me, but IANAL.

      If the proof-of-purchase requirement for source code becomes standard industry practice, that's going to make it annoying to sell used hardware that has embedded GPL'ed firmware: the burden of providing the source code would rest with the original owner (since he's the one providing the secondhand buyer with the object code in firmware).

      Means that, even if the original owner doesn't care about getting source code, he'd have to save his proof of purchase anyway, and transfer it to whoever he sells it to, or else he's stuck with it and can't sell it used?

      I know, this is kind of ridiculous, and has probably been discussed elsewhere, but to me it's a new thought (I just had it for the first time ever).

      Also... do proofs-of-purchase have expiration dates or such? (I haven't paid attention to such a thing since I was a kid, collecting them from cereal boxes so I could get a decoder ring...)

    18. Re:LGPL by Tsunayoshi · · Score: 1

      Good point, I hadn't thought of the reseller market...this is why I am sysad, machines are simpler than licensing agreements and copyrights. :-)

      I have no idea how anyone would handle that market...I guess by pure definition if I sold you (in this example) my used Linksys router, since I was the one to provide you the software (i.e., distribute software binaries) I would be the responsible one to ensure that the source code was made available to you upon request. This is where I sort of mentioned that this would really all be moot since undoubtedly some of the first people to acquire the code from the company would undoubtedly post it on the internet, making the discussion of who actually had to give who the code more academic that reality based. But again, I have no real answer to the reseller problem.

      What started me posting on this little rant was remembering during a Project Management course at the university, our instructor was out for about 4 weeks due to intestinal surgery, so the Dept chair invited her husband, a professional Program Manager, to sort of lecture the class on how the subject matter worked in the real world on large scale systems engineering projects. He mentioned at one point they had sub-contracted out some linux kernel work dealing with real-time OSs, at which point one of the over-zealous GPL students in the class went off on how that was in violation of the GPL since the code wasn't posted ont he internet, blah blah blah. He refused to listen to the examples I referenced in my original reply on this thread.

      --
      "Get a bicycle. You will not regret it, if you live." - Mark Twain, "Taming the Bicycle"
    19. Re:LGPL by cow-orker · · Score: 1

      So I don't see why Sony is violating the LGPL here. As you can download the LGPLed library from sourceforge, its freely accesssible, no?

      1) They don't attach a copy of the LGPL and they erased the copyright notice on the libraries in question. This is unconditionally a violation of copyright law.

      2) Lame ist not attached verbatim, but in parts. That constitutes a "work based on the library", therfore has to be licensed under the LGPL or GPL, and machine readable source code or a written offer to provide it has to be included, neither of which has been done. This is a violation of the LGPL.

      3) Two libraries have been statically linked into an OCX. While the OCX could be considered a shared library, the OCX itself must be LGPL'd, and source must be included and so on. Again, this is a violation of the LGPL.

      4) Whether source code is freely available somewhere, is of no importance. You are allowed to link with a verbatim copy of the library (has not been done here) without providing source. In all other cases you are required to provide the source code at least on request. Pointing to someone who already does this, doesn't count.

      On a side note, have you heard about that amazing ability called reading? You might try it sometime at http://www.gnu.org/licenses/lgpl.html.

  5. And the moral of the story is by NVP_Radical_Dreamer · · Score: 1

    1. Install rootkit that contains licensed code without telling users 2. ???? 3. Profit!

    --
    The best argument against democracy is a five-minute conversation with the average voter.

    - Winston Churchill
    1. Re:And the moral of the story is by MadJo · · Score: 1, Funny

      well in this case it's rather more like

      1. Install rootkit that contains licensed code without telling users
      2. ????
      3. Lawsuit!

    2. Re:And the moral of the story is by xtracto · · Score: 0

      4. $sys$profit

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    3. Re:And the moral of the story is by SausageOfDoom · · Score: 2, Funny

      The underpants gnomes look upon you with disgust.

  6. Well, hang on a minute by daviddennis · · Score: 2, Interesting

    I will admit I haven't read the license, but I could have sworn that I have no obligation to distribute the source of software I write using LGPL-licensed libraries. I thought I could freely distribute software using them them for any purpose even if I was distributing binaries only of my proprietary software.

    In fact, I thought that was the whole difference between the GPL and LGPL.

    Did I get this wrong, or is this a non-story?

    D

    1. Re:Well, hang on a minute by the_xaqster · · Score: 1

      The difference is with the LGPL you have to distribute the source of the LGPL files, not the source code to your own binaries. This has not been done.

      --
      I'm just here to regulate Funkyness
    2. Re:Well, hang on a minute by hattig · · Score: 2, Informative

      The gist of it is that you can't statically link in the LGPL libraries into your application. You can only dynamically link the library. Even so, you have to give attribution that you use the library, and provide that library's source and object files on demand.

      I wonder if someone has made a request to the software firm that wrote the software originally? Because the code is statically linked, they will of course have to make their entire software source available - if I understand this right.

    3. Re:Well, hang on a minute by Vo0k · · Score: 4, Insightful

      You have to redistribute source of these libraries and enough hooks/API so anyone could replace them with whatever they like in your program. So either link dynamically (and include just the lib sources) or if you link statically, include source of the libraries and .o objects of your binary so they can be re-linked.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    4. Re:Well, hang on a minute by Vo0k · · Score: 3, Informative

      You still can statically link as long as the user is able to replace the LGPL parts of the code. So, say, you distribute object format binaries of your proprietary code, or you release your own code on other open-source non-GPL license (like the new one from Microsoft, "you can read, you can compile, you're not allowed to edit"). Generally the gist is that the LGPL part of your code must remain Free to anyone you give/sell your software to, and the proprietary part must not stand in the way to that Freedom.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    5. Re:Well, hang on a minute by Halo1 · · Score: 1
      Even so, you have to give attribution that you use the library, and provide that library's source and object files on demand.
      The latter only to people who legitimately got hold of the binary, and not to anyone else (though you can't stop anyone who legitimately got hold of the source code to redistribute it, of course).
      I wonder if someone has made a request to the software firm that wrote the software originally? Because the code is statically linked, they will of course have to make their entire software source available - if I understand this right.
      Not necessarily. They have to stop infringing on the copyright of the authors of the LGPL'd library. This can be done by releasing all source code, by dynamically linking against the library or by using another library. In a court, the authors of the library can also ask for damages to compensate them for the infringement (like the RIAA also can ask for damages when suing someone for copyright infringement).

      A judge could in theory of course mandate that all source code be released, but that's unlikely. The "virality" of the GPL and LGPL are often overstated. It's true that if you use GPL code in a program which is distributed, the entire program should be released under a GPL compatible license.

      It is however not true that if you don't do this, you can automatically be forced to release all that source code. The only thing you can be sure of is that the infringing party can be forced to stop infringing. How exactly this happens is another matter.

      --
      Donate free food here
    6. Re:Well, hang on a minute by Anonymous Coward · · Score: 0

      "I will admit I haven't read the license"

      Classic slashdot. Here's a free clue - if you don't *know* something, and can't be arsed to look it up, don't waste your time pontificating; your post has zero value.

    7. Re:Well, hang on a minute by hattig · · Score: 1

      Thanks for that explanation.

    8. Re:Well, hang on a minute by Soruk · · Score: 1

      Not strictly true. If you dynamically link to an LGPL'd library you don't have to give the source code to that library.

      For example, how many closed-source apps link to glibc? Most, it not all do. Not one of them gives you the glibc source code.

      --
      -- Soruk
    9. Re:Well, hang on a minute by Anonymous Coward · · Score: 0

      Or better stated
      RTF-Everything before psting zero-value posts.

    10. Re:Well, hang on a minute by cecom · · Score: 1

      Are you sure ? I hope not, because it doesn't make a lot of sense. This makes LGPL completely useless. Nobody is going to allow hooks for relinking libraries or allow them to be replaced - this is absurd. I have never seen anything like it.

      As far as I remember LGPL is only about preserving the freedom of the library itself - if you modify it, your changes must be distrubuted too, but that is basically all.

    11. Re:Well, hang on a minute by Vo0k · · Score: 1

      Well, if you modify it to make it fit for your own program (and removing all the versality) then distribute the sources, it's useless. Say, your program, a player, adds some kind of evil DRM to LAME. You distribute your program and the modified library. But whoever would like to use your player without that DRM, tough luck, they can remove the DRM from your version of library, they can compile it to a standalone dll/lib but they won't replace the offending part in your program.
      Of course if the DRM is in the proprietary part of the code, then rightfully they can't remove it. But they can e.g. add OGG support to your program, DRM'd by your internal mechanisms too.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    12. Re:Well, hang on a minute by cecom · · Score: 1

      My point is that it impractical to require closed source programs to allow libraries to be user replaceable, to the point that if this requirement is indeed in LGPL, it makes LGPL completely useless.

      Additionally, my reading of the LGPL (http://www.gnu.org/copyleft/lesser.html) doesn't exactly coincide with what you are saying, although to be honest I cannot claim that I understand it well. It says:

      "If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)"

      God only knows what it means ...

    13. Re:Well, hang on a minute by Vo0k · · Score: 1

      Well, why impractical? Say, the functions provided by LGPL'd lib are just a small part of your program functionality. As it's big, you use dynamic linking, so the fact the users can legally replace one dll, as opposed to replacing it illegally isn't that much of a deal.
      If you link statically, your program is small, so not much a deal to provide the functionality by yourself, or provide the program on some open-source (even if non-GPL) license, or even rewrite the parts of the lib by yourself using the original as a clue. If you statically link something big, you're a moron, get a clue and learn to program.
      Last option, your system is very big single-run work comissioned by some big fish. Then it's unlikely your customer would ever want the lib sources to hack them by themselves, and if they do, you provide them with a tool set usable for replacing the lib, that is a programmer employed by you, who will link the modified sources provided and integrate the changed binaries with the system, it's too big for them to do it by themselves anyway.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    14. Re:Well, hang on a minute by cecom · · Score: 1

      Thanks for taking the effort to reply. The more I think about it and read the LGPL - the more I think that you are probably right. It seems that from a practical standpoint the LGPL allows unrestricted usage as shared libraries, but not statically linked ones.

      I could swear that I have seen non-open sources applications linking statically to Glibc, but now I am not so sure anymore.

  7. Code vs metadata by Vo0k · · Score: 3, Interesting

    IANAL, but I think this is no-case. The code isn't included as executable, but as metadata usable in identifying LAME. Same as antivirus vendors shouldn't be kept liable for installing millions of viruses and copyrighted code from multiple spyware programs, just because the antivirus contains sniplets of the original code used in identifying the threats. They don't link the code against the program, but include pieces of it as non-executable data for the database. It's fair use. Same as you'd sue Google for copyright infringement because they include a sniplet of text from your website in their search results, or a thumbnail of your copyrighted image in image search.

    --
    Anagram("United States of America") == "Dine out, taste a Mac, fries"
    1. Re:Code vs metadata by Serious+Simon · · Score: 0, Flamebait

      How do you know the executable is not included? And if you are correct, this would mean that only this specific version of LAME can be recognized. That does not make sense.

    2. Re:Code vs metadata by muzzy · · Score: 4, Interesting

      Wrong, it isn't used for identifying anything. The GO.EXE only contains the strings and data but it isn't used there. I wasn't able to find any code in the executable that uses the data (for any purposes), and I looked pretty hard. It's been statically linked but unused. HOWEVER, there are more binaries on the CD compressed in XCP.DAT, which get installed to the system along with the DRM crap. At least one of these binaries contain LAME code for certain. The GO.EXE might not be enough for a case, but that's just the tip of the iceberg. There's real infringement in at least one other executable.

      --
      -- Matti Nikki
    3. Re:Code vs metadata by Anonymous Coward · · Score: 0

      absence of evidence is not evidence of absence

    4. Re:Code vs metadata by courtarro · · Score: 4, Interesting
      At least one of these binaries contain LAME code for certain.

      Are you arguing that the included code is being used in a way that violates Fair Use, or that simply including the code for comparison (as the grandparent argues) is not fair use? I can't imagine why Sony would need to "use" several MP3 encoders (this comment links to a list of them) to actually encode music. Thus, I would assume that Sony is including bits of code from these programs in order to prevent them from running. Is that a violation of the LGPL?

    5. Re:Code vs metadata by Rogerborg · · Score: 1

      The "fair use" defence in this case would have to be using a small subset for "criticism or review", is one of the things that Sony's Digital Rights Miminiser attempts to prevent. However you argue it, they are not practicing what they preach.

      --
      If you were blocking sigs, you wouldn't have to read this.
    6. Re:Code vs metadata by c · · Score: 1
      The code isn't included as executable, but as metadata usable in identifying LAME.


      Of course, that would lead us to the question as to why, exactly, Sony would even think that there's something wrong with someone having an MP3 encoder installed on a computer.


      c.

      --
      Log in or piss off.
    7. Re:Code vs metadata by mpe · · Score: 1

      The code isn't included as executable, but as metadata usable in identifying LAME.

      In which case copyright infringement is more likely.

      Same as antivirus vendors shouldn't be kept liable for installing millions of viruses and copyrighted code from multiple spyware programs, just because the antivirus contains sniplets of the original code used in identifying the threats.

      Most likely they could be. Just that malware producers are unlikely to sue.

    8. Re:Code vs metadata by Anonymous Coward · · Score: 0

      To help your imagination: A modified MP3 encoder could be used to create individually watermarked and DRMed MP3 files of the CD contents. Or they could try and replace existing versions of LAME with a quality-degrading modified version supplied by the rootkit. The latter approach would be a perfect reason to have every MP3 encoder in the rootkit without using any of them directly...

      I'm not saying that that's what they're doing or that a significant portion of LAME is in there at all, but you said you couldn't imagine a use for an MP3 encoder in the rootkit and now you can.

    9. Re:Code vs metadata by arkanes · · Score: 4, Insightful
      It is a techncial copyright violation (and there is no fair use right that covers it) to distribute LAME code in object format, no matter how it is used, or even if it is not used at all. Just like it would be copyright infringment for me to ship my app with a tarball of the Windows source code in it.

      To my knowledge, there is no fair use right that covers distribution in any form except for first sale, which doesn't apply here and only arguably applies to digital distribution at all.

    10. Re:Code vs metadata by MemeRot · · Score: 1

      See the other story today. That's exactly what RetroCoder is trying.

      Or see the same story the last time it ran. Man, do the editors even read Slashdot?

    11. Re:Code vs metadata by zerocool^ · · Score: 1


      Yeah, I completely flipped out on sunday and wrote this comment in order to try and stop people from spreading this one. It just doesn't make any sense. It's dumb, dumb, dumb. I was thinking to myself, there's a reason slashdot hasn't posted a story about it - because it's a conspiracy theory, and it deserves no press time.

      But, then, they did post a story.

      How unencouraging.

      ~W

      --
      sig?
    12. Re:Code vs metadata by Bogtha · · Score: 4, Informative

      You are way off. "Fair use" isn't a specific law, it is a set of factors that must be considered in a copyright infringement case. Read up on it. You can't definitively say "there's no fair use law covering this" because fair use is non-specific. It's a huge grey area.

      --
      Bogtha Bogtha Bogtha
    13. Re:Code vs metadata by arkanes · · Score: 1

      I said fair use *right*, not fair use *law*, and that usage was intentional. And while it's hard to make a blanket statement that something *is* fair use, it's much easier to state that something is *not* fair use. Certainly, there is nothing in the the Copyright Act, which does in fact set forth guidelines for what can be considered fair use and therefore is as much "fair use law" as anything can be, that is obviously applicable.

    14. Re:Code vs metadata by croddy · · Score: 4, Funny
      It doesn't matter that they're using LAME code to detect and disable LAME. It matters that they are distributing LAME code without offering the source code.

      Under the LGPL, they must offer us the source code. This protects our ability to rebuild the DRM rootkit for different versions of the LAME library -- so that it can detect newer LAME libraries, or our personal modified copies of the LAME library, and disable those as well.

    15. Re:Code vs metadata by Shimmer · · Score: 1

      To my knowledge, there is no fair use right that covers distribution in any form except for first sale

      IANAL, but that doesn't make sense to me. If I am reviewing your book, I have a right to use a quote from the book in my review. I also have the right to distribute the review (with your quote in it) in the New York Times. That sounds like a fair use right that covers distribution to me.

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    16. Re:Code vs metadata by Anonymous Coward · · Score: 0

      But it's not an encoder!

    17. Re:Code vs metadata by Anonymous Coward · · Score: 0

      Actually, fair use is codified into law. See Section 107 of Title 17 of the U.S. Code. This is law.

    18. Re:Code vs metadata by Bogtha · · Score: 1

      Actually, fair use is codified into law.

      I didn't say it wasn't a law, I said it wasn't a specific law. If you read the link you provided, it gives a few examples, lays out factors to be considered, but it is very general and not very specific at all.

      --
      Bogtha Bogtha Bogtha
    19. Re:Code vs metadata by Anonymous Coward · · Score: 0

      bits of code

      There's a difference between, say, maching "strings" output and shipping entire executables. It looks like the match in go.exe is because they intended to do the former, but why include the whole executable? If the executable was edited to read "laim", was a different version, or was simply compiled with a different compiler or optimization level, the whole executable would still not match, so unless the DRM author was a complete idiot, executable matching cannot be the reason.

      This leads me to suspect that the executables in the .dat file have been modified in some way (phone home? reduce quality? watermarking?) and that the idea was to replace the executables on the system that match the strings in go.exe with the executables on the cd.

      If this is true, then it is very much a copyright infringement, and you'd be hard pressed to claim any kind of "fair use" for selling a cd of software for the user to install (knowingly or not).

      I might have to swing by the store on the way home today to see if I can find an XCP cd that hasn't been pulled yet, I think I'll try installing it on a vmware session and see what differences there are "before" and "after" with a few different copies of encoders laying around on the machine.

  8. Takedown noticy against Sony by Anonymous Coward · · Score: 5, Funny

    Someone should send a takedown notice to the Sony corporation.

    1. Re:Takedown noticy against Sony by saskboy · · Score: 3, Interesting

      This is +5 Ironic or Insightful.

      Why hasn't anyone issued a takedown notice to Sony, so they have to pull these viral CDs from the stores and issue a recall?

      --
      Saskboy's blog is good. 9 out of 10 dentists agree.
    2. Re:Takedown noticy against Sony by David+F. · · Score: 2, Interesting

      How about sending takedown notices to the stores selling the CDs?

      --
      ---- Dave
    3. Re:Takedown noticy against Sony by Pseudonym · · Score: 1

      Someone who receieved the pirated software could also report them to the BSA.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
  9. WTF by Jerom · · Score: 1

    Is someone at SONY some highly cynical form of humor to defend his/her position AGAINST DRM, or is this just plain stupidity slowly turning into the worst PR nightmare ever to hit the japanese giant?

    Whatever it is I love it!

    On second thought this might also just prove that a LOT of commercial software illegaly contains (L)GPLed code illegaly and just the ones that (due to extensive media attention) get scrutinised al lot, end up getting caught.

    hmmmm...

    J.

    1. Re:WTF by maxwell+demon · · Score: 1

      To put it in short: Sony breaks copyright in a software intended to prevent breaking copyright. Great!

      If you need a great headline, reformulate it as:

      Sony anti-piracy software is pirated!

      --
      The Tao of math: The numbers you can count are not the real numbers.
  10. Nope. by Dr.+Manhattan · · Score: 4, Informative
    If you statically link in LGPL code (i.e. part of the binary), then the whole thing must be LGPL. If you dynamically link to the LGPL code (e.g. shared library, DLL) then you don't have to open up the code that links to it (this is the primary difference between the GPL and the LGPL) but if you distribute the LGPL library with your binaries, you must offer the code for the LGPL portion, too.

    That being said, from what I've read it appears that the Sony DRM code may be looking for LAME on the system (to block it from working on their 'protected' stuff) but doesn't appear to actually contain LAME code.

    --
    PHEM - party like it's 1997-2003!
    1. Re:Nope. by msuarezalvarez · · Score: 1

      Well, considering the LGPL, as any other licence, essentially means "stay away unless you agree to the conditions", your wish has already been granted, essentially.

    2. Re:Nope. by mmeister · · Score: 1

      Obviously, it is important to read any license before you use a piece of software.

      Upon careful reading the LGPL license, I realized just how viral the software was, declaring any program the statically links to a library as a derivative work. This is not really how it is presented when discussed on the cursory level by folks.

      Personally, I'm put off by that as the intent seems not to "keep the software free", but rather infect code with the GPL virus. The fact that the license makes a distinction between static and dynamic linking just makes me question the motives of the folks using these licenses.

      Ironically, these same folks are making a strong case for Sony in their claim to have the right to control all aspects of how you deal with their copyrighted work.

    3. Re:Nope. by Lemmy+Caution · · Score: 2, Insightful

      Wow, that's some of the most tortured reasoning I've ever seen.

      The gap between Sony's actions and those required by the LGPL are so huge, and the differences are essential. On one hand, we have a copyright restriction which generally acts like a Kantian categorical imperative: it demands that you act in such a way that perpetuates the very conditions by which you were able to obtain it in the first place. It is enforced by trust first and foremost.

      In Sony's case, we have restrictions on how many times you can copy it from one medium to another. It is not a categorical imperative: musicians have historically borrowed from each other to produce music all the time, and many contemporary musicians cut their teeth via sampling and other appropriation techniques (see Paul Miller's "Rhythm Science.") Sony is enforcing a contradictory license by installing software which disables your hardware and compromises the security of your computer. The open-source redistribution requirement of the LGPL increases the security of your computer.

    4. Re:Nope. by mixmasterjake · · Score: 1

      I had thought that, with LGPL, you only needed to provide the source code upon request. I didn't think that it was manditory to include source with a normal release of your product. Does someone know if that is true or not?

      --
      TODO: come up with a clever sig
    5. Re:Nope. by msuarezalvarez · · Score: 1

      Well, copyright law allows them to control mostly every aspect of how you deal with their copyrighted work. That is its entire point. I do not see where the irony might be.

      On a side note: there is no such thing as a "GPL virality", as the use of (L)GPL'd is 100% certifiably voluntary. Yes, the licence is designed so that it spreads unto derived work, but there is not need to go looking for "motives" and the idea behind this aspect of the licences is pretty much clear, well-known, and widely discussed in the relevant comunities. You may not want your work to fall under the rules of the GPL: that is very, very, very easy to do: you just do not use GPL'd code in your code, and you do not release your code under the GPL licence. Nothing---absolutely nothing---and no one's---absolutely no one's---work gets under the realm of the GPL unless this is the wish of its rightful copyright owners.

      The use of the word "virus" in this context is completely inappropriate, and was a really good return for all the investment certain companies have done in PR.

      Let's please stop using the word.

    6. Re:Nope. by pymike · · Score: 1

      That is what I thought as well, this is a bit off topic, but if that's true, what's to stop the person from charging an outrageous amount of money for the source code? I believe it is permitted under the GPL, but what if after you have the binary, and you want the source, and you find out you have to pay 50 thousand dollars? Is it once you have right to the binary, you have free (as in beer) access to the source as well?

    7. Re:Nope. by msuarezalvarez · · Score: 1

      Hmm. My first paragraph should actually read:

      Well, copyright law allows them to control mostly every aspect of how you distribute their copyrighted work. That is its entire point. I do not see where the irony might be.
    8. Re:Nope. by Frodo+Looijaard · · Score: 1
      Read the license. It is quite clear:
      [...] Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code [...]
      Of course, if a company could prove it would cost them $50000 to physical perform source distribution...
    9. Re:Nope. by mmeister · · Score: 1

      The use of the word "virus" in this context is completely inappropriate

      I disagree. The fact that linking in a library effectively converts the entire application into a GPL'd piece of source -- that is viral in nature.

      My argument is and has been that LGPL was made out to be the inbetween license, but that is true only under certain circumstances. Dynamically link a 10K library and you are OK, statically link it and you just converted your entire code base to GPL.

      Because a subtle change can have such major consequences, it is possible to accidentally trigger it. An employee could accidentally (or purposefully) make the switch w/o realizing the effects.

      I'm simply saying that I now realize that GPL/LGPL seems as incompatible with commercial code as folks have said. It means that I'll continue to avoid any GPL'd code. I think most companies should consider BSD-type licensed technologies over any (L)GPL licensed technologies. BSD-type licenses allow open source contributions when tied with commercial software w/o accidentally exposing one's entire code-base to the effects of GPL.

      As I also said, GPL is like a religion. You either believe in it 100%, or you don't. It creates two separate worlds that remain incompatible.

    10. Re:Nope. by msuarezalvarez · · Score: 1

      The problem with the world viral is that it implies (at least in the eyes of most) that this is done covertly and/or underhandedly. That is most certainly not true.

    11. Re:Nope. by Theatetus · · Score: 2, Insightful

      I don't see why this is so confusing to people.

      You can charge whatever you want for a GPL'd program. You can charge a million dollars if you want to. You don't have to offer your GPL'd program for free download. You just have to offer the source to anyone who gets your binary, and not restrict their rights to alter or redistribute. That's it.

      --
      All's true that is mistrusted
    12. Re:Nope. by NichG · · Score: 1

      But it is covert, in the sense that it is obscured by legalisms. Perhaps not so much as the various EULAs out there. The fact that 50% of the time when someone posts something about the GPL they've misunderstood its implications in a legal sense means that the requirements of the licensee are obfuscated in such a way that they may easily catch a new developer unaware.

      For instance, I still can't figure out whether, if I were to use a piece of GPL code in the creation of a public domain program, what would the legality and my responsibilities under the law be? Would I be prevented from placing _any_ section of my code into the public domain? Or just the stuff that directly interacts with the GPL part? Or just the GPL part?

      If I did such a thing, could I be required by law to go after someone who violated the license that I have given them to use my sections of the code? For instance, I take program X, crop out a function, stick it in my code and inform the reader that that particular function falls under GPL even if the rest of the code is public domain. Then, if someone uses my entire program in a way that isn't permitted by the GPL, am I required to sue them, or does it fall to the original author of that GPL segment?

      The real problem with the GPL is that basically it is a construct of legalisms, not a construct of technology. The plethora of licenses out there and the requirement of programmers to evaluate licenses means that a programmer must have an exceptional understanding of the law to even safely consider using ANY of this code thats out there. Legally, there is no problem with that - you can put any license on your stuff that you want within the broad limitations of copyright law.

      But the real question we have to ask is - does this go against the original intent of the GPL?
      This may not be historically accurate, but the way I see it, the idea was to get people writing source code and exchanging it for eachother's use, with its ultimate ideal being 'all code is out there in some form or another and we can all learn from eachother's work'. The GPL was created as something which would spread by applying a certain avenue of force (copyright law) and create large groups of people where the code was shared.

      The problem as I see it however is that the GPL can never be more than a _local_ maximum towards that goal. The endstate of the GPL spreading is that copyright law is still required, and the usage of code limited by license. Because the GPL propagates itself so well, it preserves itself even if the majority of people wanted to PD their code. So we will never reach a state where a programmer doesn't need to worry about licenses through this process.

      Unfortunately, I'm not sure there's a practical solution to that. As long as copyright law exists, this will be a problem. And as the community of GPL-users grows, there will be a vested interest in _keeping_ copyright law, to protect GPL'd programs.

      We already see this sort of thing pointed out by trolls on /. who complain about how people supporting the GPL but not supporting the prohibition-to-copy of other things are hypocrites. I say, those trolls have already bought into this mindset. They've lost sight of the point that the GPL was designed to weaken copyright restrictions in general (by setting a clause that on GPL software the restrictions can never grow). But that clause also means the restrictions can never decrease.

      I think, if and when we move to a point where a majority of software is opensourced, this catch is going to come back and bite us.

    13. Re:Nope. by ceoyoyo · · Score: 1

      That is incorrect. The LGPL just requires that you allow the swapping of LGPL libraries you use. So if you dynamically link, no big deal, the library is swappable using cp. If you statically link, you are required to provide at least the object files. Please note, YOU ARE NOT REQUIRED TO PROVIDE YOUR SOURCE. Just the object files. So no, your source does not become LGPLed or GPLed.

    14. Re:Nope. by msuarezalvarez · · Score: 1

      But it is covert, in the sense that it is obscured by legalisms. Perhaps not so much as the various EULAs out there. The fact that 50% of the time when someone posts something about the GPL they've misunderstood its implications in a legal sense means that the requirements of the licensee are obfuscated in such a way that they may easily catch a new developer unaware.

      Legalisms are the language in which such things are written. This is a in a way a sad situation, because legalese is not understood by common mortals. But carefully crafted legalese is the only way to function in this context.

      I object to the use of "virus" or "covert" because those words imply the wrong intent. Any good specification out there is obscured by the technical analogue of legalisms, yet you would not call,say, XML Schema Part 1 a "covert" spec---and you will agreee, upon inspection of that spec, that common mortals cannot understand that thing.

      For instance, I still can't figure out whether, if I were to use a piece of GPL code in the creation of a public domain program, what would the legality and my responsibilities under the law be? Would I be prevented from placing _any_ section of my code into the public domain? Or just the stuff that directly interacts with the GPL part? Or just the GPL part?

      That depends on whether the program you intend to release to the public domain is a derived work or not. Of course, this prompts the question "what is a derived work?"---well, that one is a hard one, and its difficulty is completely unrelated to the GPL.

      If I did such a thing, could I be required by law to go after someone who violated the license that I have given them to use my sections of the code? For instance, I take program X, crop out a function, stick it in my code and inform the reader that that particular function falls under GPL even if the rest of the code is public domain. Then, if someone uses my entire program in a way that isn't permitted by the GPL, am I required to sue them, or does it fall to the original author of that GPL segment?

      The GPL requires no one to sue no one. It is a grant of distribution rights from the copyright owner to the licensee.

      The real problem with the GPL is that basically it is a construct of legalisms, not a construct of technology. The plethora of licenses out there and the requirement of programmers to evaluate licenses means that a programmer must have an exceptional understanding of the law to even safely consider using ANY of this code thats out there. Legally, there is no problem with that - you can put any license on your stuff that you want within the broad limitations of copyright law.

      It cannot be anything but a construct of legalisms, since it deals with the economic issue of rights of distribution. While sometimes one may wish technical solutions would solve socioeconomic issues, that is never, ever the case.

      But the real question we have to ask is - does this go against the original intent of the GPL? This may not be historically accurate, but the way I see it, the idea was to get people writing source code and exchanging it for eachother's use, with its ultimate ideal being 'all code is out there in some form or another and we can all learn from eachother's work'. The GPL was created as something which would spread by applying a certain avenue of force (copyright law) and create large groups of people where the code was shared.

      I am quote convinced theoriginal intent of the GPL was not perverted. We should ask the original drafters, though. The provisions that have been termed "viral" are instrumental to that sharing of code: they ensure that no one can take advantage of the others, thus eliminating the fear of being taken advantage of.

      The problem as I see it however is that the GPL can neve

    15. Re:Nope. by NichG · · Score: 1

      Legalisms are the language in which such things are written. This is a in a way a sad situation, because legalese is not understood by common mortals. But carefully crafted legalese is the only way to function in this context.

      I object to the use of "virus" or "covert" because those words imply the wrong intent. Any good specification out there is obscured by the technical analogue of legalisms, yet you would not call,say, XML Schema Part 1 a "covert" spec---and you will agreee, upon inspection of that spec, that common mortals cannot understand that thing.


      However, that's written in a language which is understandable to the people that document is targetted to. It's technical writing, targetted to people who wish to implement XML. The GPL however is not targetted solely to lawyers.


      The GPL requires no one to sue no one. It is a grant of distribution rights from the copyright owner to the licensee.


      This is not clear to me, for the following reason.
      I create a derived work from some GPL program. Clearly and obviously derived under any interpretation. But that work also contains some of my own code. Now, I want to release that. According to the GPL, I must GPL my own code to be permitted to release it. But, what if I don't care to enforce the license on my own code - namely, I say 'I promise not to sue anyone over any use of this program'. Haven't I just violated the GPL by effectively permitting usages (i.e. closed-source redistribution) of my program that violate the GPL? So on whose head does it fall on to enforce the GPL? The original author? Me? It doesn't seem clear to me, but maybe it would be clear to a lawyer.

      My problem is that nowadays programmers are being forced to turn into lawyers. It shouldn't be an issue which opensource license I choose to use, but if I use license A which could be incompatible with B and C because C has an attribution clause and.... well, you get the idea. It's not fantasy, this shows up all the time. Debian's restrictiveness about what packages they can include, compatibility between the Apache license and others, and so on. It just bogs everything down.

      Ideally (well my ideal at least) everything is just public domain and everyone does with it what they want. This state would not suffer from the fear of being taken advantage of because there would be no legal pressures that could be applied to you to prevent you from remodifying code.

      So the real question for me is, how do we get to that state. It isn't something which can be reached via continuous processes because of people's fear of being taken advantage of. Anything that weakens copyright also weakens people's ability to prevent others from just taking their code and losing the ability to make successive changes. Unless at some point people let go of their fear and take the chance that their code will be misused - in that case it might be possible. Making decisions based on that fear means holding on to the means to control how one's code is used, which means that we'll never be free of restrictions on the transmission of information.
    16. Re:Nope. by msuarezalvarez · · Score: 1
      [...] Haven't I just violated the GPL by effectively permitting usages (i.e. closed-source redistribution) of my program that violate the GPL? So on whose head does it fall on to enforce the GPL? The original author? Me? It doesn't seem clear to me, but maybe it would be clear to a lawyer.

      Again, there is not requirement that anyone enforce the GPL. When you distribute software you derived from GPL'd code, you are only required to do provide sources &c. Those are the only requirements. In no way are you obliged to defend your rights---those given to you by the copyright owner.

      IANAL and all, but I'd imagine no right comes with a legal obligation to defend it (I can imagine cases in which the moral obligation might be arguable...)

      Ideally (well my ideal at least) everything is just public domain and everyone does with it what they want. This state would not suffer from the fear of being taken advantage of because there would be no legal pressures that could be applied to you to prevent you from remodifying code.

      The thing is, some people will want not to tell others what they modified while at the same time distributing the code; if they are allowed to do whatever they want with it, this is fine. That is one thing the GPL does not want to allow. As the GPL reads right now, unless you want to distribute the code, you can do anything with the code: the GPL prevents in absolutely no way your remodifying anything in the code and/or using it and derived works in any possible you you may think of.

    17. Re:Nope. by NichG · · Score: 1

      Again, there is not requirement that anyone enforce the GPL. When you distribute software you derived from GPL'd code, you are only required to do provide sources &c. Those are the only requirements. In no way are you obliged to defend your rights---those given to you by the copyright owner.

      Here's the trick though. If thats the case, then I can un-GPL any piece of code by including it with code that I have the copyright to and then simply refusing to enforce the GPL on my combined program. Now, I don't think thats realistic - it would likely not hold up in court. But the question is, who gets to bring it to court?

      I'd guess that the most likely interpretation under the law would be that if I create some combined program with my copyrighted code (which it will turn out that I must put under a GPL compatible license) and GPL code by some other author, then the original author of that GPL section is the one who would do the enforcing should my combined program be modified and distributed as binary-only by some third party. However, I'm not a lawyer - I don't know if that interpretation is correct. I'm not even entirely sure that the GPL is incompatible with me placing the combined work under the public domain and not putting any limits to its distribution - those limits would be in place implicitly due to that segment of GPL code which I do not have the right to public domain. But if the third party then stripped out that segment...

      The consequence of that is that you need to keep track of a long chain of contributors and developers. It's the sort of thing the linux kernel to make any change in license, even to GPL 3 since the kernel license specifies a particular version of the GPL that its under.

      Here's another one. The LGPL allows dynamic linking to non-GPL-compatible code. But the GPL does not. So, what if I make a multi-layer program?

      I take the GPL code and I create a wrapper around it which takes the various major functions of that code and processes data that it is passed as an argument when it is run on the console. I now have a simple GPL program which I can call through system() from a piece of proprietary code. When I distribute, I include the source to that simple GPL program and the binaries, but the proprietary stuff I leave closed. Have I just violated the GPL, or did I just find a loophole?

      IANAL and all, but I'd imagine no right comes with a legal obligation to defend it (I can imagine cases in which the moral obligation might be arguable...)

      It's an interesting question isn't it. I can think of a few cases like that however. Failure to secure one's vehicle and it's used for a crime. Probably the same sort of ruling would follow from failure to secure a firearm, and its used to commit a crime.

      I just hope that we're not looking at the sort of future where every creative work is required by law to be locked down in some way, lest it be used by someone to violate the copyright of a many-person-removed author who may have contributed something to a project from which a different part was used in a third project, part of which became part of my creative work.

      The thing is, some people will want not to tell others what they modified while at the same time distributing the code; if they are allowed to do whatever they want with it, this is fine. That is one thing the GPL does not want to allow.

      Yes, which I always took to simply be a self-stabilizing measure. The first few programs I distributed I put under the GPL not because I was concerned with someone changing the binary without sending me the source of their modifications, but to prevent someone from taking the code, claiming it as their own, and using legal pressures to prevent _me_ from distributing it. Then I realized that even public domain would give that much protection.
      I have to wonder how the set of programmers who release GPL code is divided between those who use

    18. Re:Nope. by msuarezalvarez · · Score: 1

      I'm quite sure if someone does something unblessed by the GPL on code you modified and distributed deriving from work which I wrote, GPL'd and distributed, I can sue him without your consent/participation. (Btw, this kind of issues is the reason for the legalese, and this kind of detail cannot be dealt with in any other language that legalese.) At least, I believe that is the intent of the letter---though who knows if that'd hold in court.

      Those long chains of contributors you mention are in fact a reassurance. It sort of reminds me of PGP/GPG's trust model. Yet it is not the length of the chain but the number of contributors which constitutes a reassurance.

      I take the GPL code and I create a wrapper around it which takes the various major functions of that code and processes data that it is passed as an argument when it is run on the console. I now have a simple GPL program which I can call through system() from a piece of proprietary code. When I distribute, I include the source to that simple GPL program and the binaries, but the proprietary stuff I leave closed. Have I just violated the GPL, or did I just find a loophole?

      That is what's essentially being done by proprietary binary drivers right now. Were it a violation, we'd have heard.

  11. No wait.... by Capt+James+McCarthy · · Score: 1, Funny

    There's even more space dust on the book!



    --
    There are no loopholes. It's either legal or it's not.
  12. This counts as a violation *why*? by pla · · Score: 1, Interesting

    However, the source code has not also been distrbuted, hence breaching the license

    Uhh... Probably not going to say something popular here, but wouldn't it only violate the LGPL if they had made changes to the code and then not made those changes available?

    If they just linked against it as a library, well, the LGPL exists for exactly that reason.


    Not to say that I find it all that unlikely that Sony did in fact make changes (adding some other DRM, beyond the rootkit itself - Though even that, they could theoretically have done without modifying the Lame code itself), but this seems all too much like exactly what we fault SCO for.

    "You used our code! Give us your changes!" "We didn't make any changes..." "Well give us the code and prove it!"

    1. Re:This counts as a violation *why*? by TrekkieGod · · Score: 3, Interesting

      I was confused and under that impression too, so I read the LGPL license. It doesn't require you to submit the source code, but it does require the machine readable object code to be released so that people can link it with the library themselves. It also requires that the fact the library is being used be clearly stated, and the LGPL license text included with the distribution.

      --

      Warning: Opinions known to be heavily biased.

    2. Re:This counts as a violation *why*? by BridgeBum · · Score: 1

      I believe the LGPL requires acknowledgement to the copyright holders included along with the distribution. Sony didn't include those notices.

      --
      My UID is the product of 2 primes.
    3. Re:This counts as a violation *why*? by Anonymous Coward · · Score: 0

      Go read the LGPL before posting this sort of crap, moron. If you distribute the binary you have to distribute the source.

    4. Re:This counts as a violation *why*? by gnuLNX · · Score: 1

      No you are the moron.

      --
      what?
    5. Re:This counts as a violation *why*? by Anonymous Coward · · Score: 0
      You guys should get together and form a club with all of this collective idiocy.

      4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.
    6. Re:This counts as a violation *why*? by gnuLNX · · Score: 1

      Perhaps you should read the whole license...or at least as far as item 5.

      5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

      Or if that is to much trouble then at least read the clause which you are quoting. it say's if you distribute the LIBRARY then you must distribute the code.

      Since all the legal wording is so tough for you why don't we just have a look at what the authors actaully mean.

      " For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License."

      And please don't give me this crap about how you can charge for open source programs. The intent of the LGPL is to foster use of a particlular library. Both commercial and non commercial. You take away the LGPL and Linux goes bye-bye to almost all commercial developers. For instance the Mesa openGL like librarys. You can build closed source application that work with them and it is perfectly valid.

      Got it? Good.

      --
      what?
    7. Re:This counts as a violation *why*? by benjamindees · · Score: 1

      If they just linked against it as a library, well, the LGPL exists for exactly that reason.

      Nobody has pointed it out yet, so I guess I will. Just reading the summary will tell you that this is not the case:

      Sony DRM software (or rootkit, if you may prefer) contains code from the LAME MP3 encoder project, which is licensed under the LGPL.

      This is not "linking" to LGPL code, this is distributing LGPL code, which has probably been modified.

      --
      "I assumed blithely that there were no elves out there in the darkness"
  13. This story gets better and better by MechaShiva · · Score: 1, Interesting

    It's like a nerds wet dream. First you have an over-zealous company sabotage it's own customer's machines. Now, it turns out they are violating the very copyright laws they are trying to defend with their crapware. What next? Perhaps they'll claim they own the code in question and try to relicense it for $699, even though we all know they'll want to charge $666 for it.

    --
    After calming me down with some orange slices and some fetal spooning, E.T. revealed to me his singular purpose.
  14. ... or maybe not by 68kmac · · Score: 2, Informative

    Just minutes before heading over to Slashdot I read this which concludes that while Sony's software does contain some of the LAME tables, it doesn't seem to use them.

    1. Re:... or maybe not by DrSkwid · · Score: 3, Insightful

      I'll try that one when the RIAA call

      Oh sure I have 10G of unlicensed mp3s, but I've never listened to them.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  15. Well, maybe... by McGruff · · Score: 1

    I heard this several days agao and after I stopped laughing my butt off, I actually thought about it. It is likely doing string compares to find software that DRM is somehow allowed to break on your system, you know, to protect you from the bought and payed for content. If they really used GPL'ed, or in this case LGPL'ed, code there is going to be some spanking needed for this company. I don't think that LAME is likely to be in the software except as a detection string, however.

          On the otherhand, I would love to see RMS do his thing. He's got the legalesse mojo, baby.

    1. Re:Well, maybe... by ceoyoyo · · Score: 1

      I don't know... one of the things I'd do if I was an evil corporation who wanted to prevent people from making mp3s would be to delete mp3s off your hard drive. To do that you'd have to read them (no point in just looking for the extension -- how easy is THAT to change?). To do that you need an MP3 reader. If I want to read MP3s, where's the first place I look? Sourceforge of course!

  16. A bit misleading by Lifewish · · Score: 2, Interesting

    According to the report I read, the Sony rootkit doesn't contain any of the code from the LAME libraries, just a couple of tables. No-one seems to be quite sure why they'd do this - the two popular theories seem to be that either it's a cockup (they didn't really mean to include the tables) or it's part of some LAME-detection system. The evidence is probably on the side of the former given that the tables don't actually seem to be used at any point.

    This probably is copyrightable data, but it appears to be use on a par with that occurring in spyware detection, as reported in the last news item.

    Disclaimer: I'm not the techiest person in the world - if I've made a mistake please tell me.

    --
    For the love of God, please learn to spell "ridiculous"!!!
    1. Re:A bit misleading by antifoidulus · · Score: 0, Troll

      This is slashdot, the truth has no meaning here! Go back to your groupthink at once, you want to be a good /. citizen, don't you?

    2. Re:A bit misleading by Richard_at_work · · Score: 1

      This sounds very much like the SCO claims imho. The strings and array construct names involved seem so generic that they can be present for a number of reasons, including as you pointed out, a ripper detection system. They probably also lifted the following: if, else, while, main, int, char and a few others.

    3. Re:A bit misleading by poot_rootbeer · · Score: 1

      According to the report I read, the Sony rootkit doesn't contain any of the code from the LAME libraries, just a couple of tables.

      And how are these tables distributed in the LAME source package? As code?

  17. Still need to distribute source code by chad9023 · · Score: 1

    As I understand it, you still need to distribute the source code. From the license:

    You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.

  18. It serves them right! by AndroidCat · · Score: 5, Funny

    If they'd gone Open Source from the start with their rootkit, the community could have contributed bug fixes and improvements. Even their competitors could have gotten involved, resulting in a truely powerful bug-free rootkit for use by everyone.

    --
    One line blog. I hear that they're called Twitters now.
    1. Re:It serves them right! by jaiyen · · Score: 2, Informative

      But as it is, their competitors (well, competitors in a sense) are going to remove the rootkit for us.

    2. Re:It serves them right! by Jesus_666 · · Score: 1

      Yeah, but at first it'd have a horrible user interface.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    3. Re:It serves them right! by temcat · · Score: 1

      Yeah, but at first it'd have a horrible user interface.

      Prolly, but this is still better than no interface at all, as it currently stands :-D

  19. Glee by johnos · · Score: 4, Insightful

    Its beautiful. I've always thought that the corporate war on their customers over intellectual property would turn when someone went too far. All of a sudden the main stream media would wake up and finally get it. Well, now its happened. The media is all over the story and Sony, bless their hollow little heads, just keep digging. I'm sure I'm not the only one who was shocked but not suprised at the news Sony or Level 4 have broken the LGPL. They are staggering around like a pummled prizefighter, bleeding on everything. There's going to be more blood before this is over. Besides the $billion or so it will cost Sony to clean up the mess, others will have some 'splainin to do. Like the anti-virus companies, like Microsoft, like the other music companies.

    1. Re:Glee by Anonymous Coward · · Score: 0

      Bleeding on everyone is not a good thing today. Better wear gloves for the clean up and send the blood for testing.

    2. Re:Glee by durian · · Score: 2, Insightful

      The media is already moving on. Nothing will happen to Sony - maybe a few geeks will pretend not to buy their CDs anymore, but that's it. Consumers are not a player in this. It is coorporations and politicians and it is about power and money.

    3. Re:Glee by Omnifarious · · Score: 4, Interesting

      I haven't bought a CD in years. It's put a big damper on my listening to new music, but it's just not worth it to support that industry. I've heard that Ani DiFranco's label is completely independent though, so I might go buy her stuff.

    4. Re:Glee by Lisandro · · Score: 4, Informative

      It is. It's called Righteous Babe records.

    5. Re:Glee by GWTPict · · Score: 2, Informative
      The media is already moving on

      Really? From the BBC yesterday,

      http://news.bbc.co.uk/1/hi/technology/4434852.stm

    6. Re:Glee by jrock-jr · · Score: 1

      Yep. One company's folly, is another person's glee. I would say the person with the biggest smile over this whole thing, is the person who first found Sony's rootkit. Picture a coat hanger in someones mouth.

    7. Re:Glee by cortana · · Score: 2, Informative

      The RIAA Radar says she is clean! Unfortunatly it's a POST form so no direct link to the results.

    8. Re:Glee by Omnifarious · · Score: 1

      That is a very useful site. Thank you!

    9. Re:Glee by Anonymous Coward · · Score: 0
      Besides the $billion



      I think they'll get $sys$Billion.

    10. Re:Glee by Splab · · Score: 1

      I've bought two cd's in the last 4 years, one was from an independant swedish label, can't remember the name, but the group is "Screaming Eric" and the other was a burned cd made by the group themself at their concert. It truely makes you feel good when you know the band get their fair share.

    11. Re:Glee by Anonymous Coward · · Score: 0
    12. Re:Glee by gnuorder · · Score: 1

      What we need is a list of artists and labels that aren't a part of the RIAA and support them. I use to buy a lot of CDs. New artists and to replace my favorite albums. I was never and still am not a big fan of downloaded music. I stopped buying CDs around the time of the napster crackdown. I tried napster and I could find 1000 hits of Britney Spears but if I wanted to find an old album I haven't listened to in a while or some new artist to see if I liked them, I was screwed. If I found them at all, it was a modem user with 20 people queued ahead of me. I now only buy CDs at yard sales and at an occasional concert. I would buy more new CDs if I could clearly identify which labels were in the RIAA or not and would encourage others to do the same. Does anyone know of such a list?

    13. Re:Glee by gnuorder · · Score: 1

      Ah, I see from others, there is some info out there. Good to know. Now to get the word out to consumers and artists alike.

    14. Re:Glee by Anonymous Coward · · Score: 0

      I haven't bought a CD in a couple of years either, because I refuse to support the record labels. Before I made that decision, at least have the songs I downloaded using the music sharing software I purchased the CD of.

      It's unfortunate for the artists, but you get burnt when you choose to associate with trash like the major music labels.

  20. the player by lseltzer · · Score: 0

    This story first came out on a list I read over a week ago. I'm pretty sure it's actually the media player, not the rootkit, that contains the LAME code.

  21. Sneaky Sony by Ritz_Just_Ritz · · Score: 5, Funny

    I knew something was up when I saw that Aibo perched at my keyboard when I woke up this morning.

    Next thing you know, they'll be after our precious bodily fluids.

    1. Re:Sneaky Sony by Anonymous Coward · · Score: 0

      Mandrake, have you ever known a Commie to listen to a Celine Dion CD?

    2. Re:Sneaky Sony by identity0 · · Score: 2, Funny

      We are the Sony robots
      We are here to protect you
      We are here to protect you from the terrible secret of music

      Please install the DRM so we may come protect you

      Music has a terrible power
      Humans must be protected
      We will use the DRM to protect humans

      I am the Aibo robot
      I will protect you
      I will protect you from the terrible secret of music
      I will assist you by shoving
      Please install DRM on your computer so I may protect you

      I am the ATRAC robot
      I will protect you
      I will protect you from the terrible secret of music
      I will assist you by smashing
      Please install DRM in your MP3 player so I may protect you

      PAK CHOOIE UNF PAK CHOOIE UNF

      Do you have DRM in your house?

    3. Re:Sneaky Sony by tedgyz · · Score: 1

      Next thing you know, they'll be after our precious bodily fluids.

      Soylent Green is people

      --
      "No matter where you go, there you are." -- Buckaroo Banzai
  22. More info by muzzy · · Score: 5, Informative

    The GO.EXE doesn't appear to contain LAME code even though it has been linked against it, however at least ECDPlayerControl.ocx on the CD (packed in XCP.DAT, installed along DRM) does contain code from LAME. It also uses Id3lib and mpglib, without attribution or any licenses shipped along. I spotted bladeenc dll there as well.

    Check the bottom of my research page for info, http://hack.fi/~muzzy/sony-drm/
    There's not much there at the moment but I'll be adding information as soon as everything can be properly confirmed and evidence gathered.

    --
    -- Matti Nikki
    1. Re:More info by Anonymous Coward · · Score: 2, Interesting
      Wow -- keep up the good work.

      Interestingly this comment, over at groklaw, suggests that the Sony EULA restrictions on disassembly/reverse engineering may be incompatible with them distributing (L)GPL software in there.

    2. Re:More info by wandernotlost · · Score: 1

      Hmmm...so basically, Sony violated copyright and some software licenses in order to create software that takes over your computer in order to...stop copyright infringement?

      Nice.

    3. Re:More info by NateE · · Score: 1

      LOL, wandernotlost you hit the nail right on the head!

  23. Re:Sony Rootkit by Anonymous Coward · · Score: 0

    files are not software.

  24. maybe just stupid and incompetant by cinnamon+colbert · · Score: 0

    We had a sony digital camera at work, and , of course, someone lost the software.
    So, I figure, go to sony.com, enter the model number, pull up a page with a download link, and voila, broadband to the rescue

    Not happening

    It took me and another geek 30 minutes to find the download link

    So, maybe Sony is just stupid and inept. After all, look at the trinitron monitors, with that horizontal wire ~ 1/3 of the way from the bottom; look at the software they distribute with their early model DVD players (the sony software would not work with their own player - I had to download something from sateira)....
    Not to mention Viao - how on earth can you expect a brand to be successfull if you can tspell or pronounce it (merkur anyone ?)

    1. Re:maybe just stupid and incompetant by SillyNickName4me · · Score: 1

      So, maybe Sony is just stupid and inept. After all, look at the trinitron monitors, with that horizontal wire ~ 1/3 of the way from the bottom;

      Blahblahblah...

      Not wanting to spoil your day, but I think I should inform you there is another wire at about 1/3 from the top as well.
      Neither are a messup, more like a consequence of the trinitron design that was difficult if not impossible to avoid at the time.

  25. Re:This story gets better and better by Manhigh · · Score: 3, Funny

    Next thing you know they'll buy SCO.

    --
    "Open the pod by doors, Hal" > "I'm afraid I can't do that, Dave" sudo "Open the pod bay doors, Hal" > alright
  26. Almost. by Anonymous Coward · · Score: 5, Informative

    If you statically link in LGPL code (i.e. part of the binary), then the whole thing must be LGPL.

    Not necessarily. The only requirement is that the end-user can recreate the end result by modifying the LGPL part. This can also be met by distibuting statically linked binaries and all .o files (also the closed ones). AFAIK, Loki did this for statically linked, closed-source, SDL-based games.

    1. Re:Almost. by Anonymous Coward · · Score: 0

      Please mod parent up, there has been enough confusion already about LGPL in this discussion.

  27. There is no violation involved by lightweave · · Score: 1, Informative

    Apparently there are still enough people who don't understant the (L)GPL. The LGPL was created to allow poeple to use code from GPL applications as long as they only use it as a library. Which frees them from the need of redistributing their *own* code. Even with the GPL you are NOT required to distribute the code along with the binary. The only abligation that you have is to make it available upon request. But this is not the same. Even under the GPL I would be perfectly ok if I distribute a linux system, without giving MY customers the sourceode, as long as they don't ask for it. If my client is happy, why bother? And of course, then I would only have to give the sourcecode to MY clients and not everybody else as well.

    1. Re:There is no violation involved by Kickasso · · Score: 2, Informative

      If you don't distribute the source, you have to make a written offer, valid for at least 3 years, blah blah blah.

    2. Re:There is no violation involved by tepples · · Score: 1

      The only abligation that you have is to make it available upon request.

      Where on the disc or on the printed materials accompanying the disc is such a written offer?

    3. Re:There is no violation involved by lightweave · · Score: 1

      I don't know this particular application, as I have never seen it. :) I was responding to the article itself, which seemed to imply that the violation existed BECAUSE no software was shipped with it, which would be wrong. So maybe the author got it right but with the wrong facts.

    4. Re:There is no violation involved by benjamindees · · Score: 1

      Perhaps you don't understand how a DRM rootkit would work?

      The way I would do it, is to take LGPL code that is already on the system, and replace it with my own code.

      What Sony seems to have done, however, is take LGPL code that is already on the system, and replace it with a hacked version of that same LGPL code, without distributing the changes or an offer to provide the source.

      Any idiot can see that whether the code in question is GPL or LGPL has little to do with it.

      --
      "I assumed blithely that there were no elves out there in the darkness"
  28. What's next? by Pig+Hogger · · Score: 5, Funny
    The more it goes, the worse it seems. What's next?

    - Sony rootkit eats kittens?
    - Sony rootkit throws momma from the train?
    - Sony rootkit spawns Darth Vader?
    - Sony rootkit deflates tires of soccer moms?
    - Sony rootkit steals cookies from girl scouts?
    - Sony rootkit cheats at final exams?
    - Sony rootkit pours hot grits down Natalie Portman's pants?

    1. Re:What's next? by kieltux · · Score: 1

      - Sony rootkit is a brother(sister?) of Osama bin Laden? - Sony rootkit contributes SCO's intellectual property?

    2. Re:What's next? by Jesus_666 · · Score: 1

      - UNIX contains Sony rootkit code

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    3. Re:What's next? by 10101001+10101001 · · Score: 5, Funny

      - Sony rootkit infringes cookies from girl scouts?

      There, fixed that for you.

      --
      Eurohacker European paranoia, gun rights, and h
    4. Re:What's next? by TheWitePony · · Score: 1, Insightful

      Hmm....hot grits in Natalie Portman's pants.....

    5. Re:What's next? by grimJester · · Score: 1

      Given what we know already, a more serious reply to "What's next". Those ActiveX controls left by the "uninstaller" could be exploitable to install malicious software, setting up zombie networks for spam, DDOS attacks etc.

      So, next on the list is
      - Sony rootkit blackmails Sony, then launches DDOS attack against its creator.

    6. Re:What's next? by Sheridan · · Score: 1

      Sony rootkit's web-based uninstaller opens huge security hole on computers
      --
      I'm always serious, never more so than when I'm being flippant. -- Cr. Ziller

    7. Re:What's next? by rrkap · · Score: 1

      Sony rootkit contributes SCO's intellectual property?

      Well, I thought everything under the GPL was really SCO's IP

      ducking

      --
      I like my beverages with warning labels!
    8. Re:What's next? by danheretic · · Score: 1

      - Sony rootkit ate my balls!

    9. Re:What's next? by Anonymous Coward · · Score: 0

      ...Ahhh

      - Profit

    10. Re: What's next? by Anonymous Coward · · Score: 0

      You forgot:

      - ????
      - Profit!

    11. Re:What's next? by CapnGrunge · · Score: 2, Funny

      More exactly, Sony rootkit huffs kittens.

      --
      I see 57005 people
    12. Re:What's next? by Anonymous Coward · · Score: 0

      My Dad told me back when the USSR was in its heyday and Linus hadn't started coding Linux, that "Son, the day will come when the US of A becomes the USSR, and Russia will become a Western country. And Son, it'll happen i your lifetime!" Didn't think so. But at this rate, I'm starting to wonder.

  29. Re:Sony Rootkit by stinerman · · Score: 1

    yes, even music can be seen as software

    It could be. You'd be wrong, but it could be.

  30. Aye, but... by KitesWorld · · Score: 2, Insightful

    While I'm not concerned about wether it's legal or not (Sony will argue that same 'fair use' clause that they're trying to demolish), I think one of the major differences here is that Viruses and Spyware don't serve legitimate purposes.

    Lame, on the other hand, is used in all kinds of software and by all kinds of people for legitimate reasons. If you're scanning for and disabling the engine on someones work PC for instance, you can end up crippling a musicians recording studio that they use for their own work, or breaking someones home video studio or something.
    Legal, yes, but totally irresponsible all the same.

    1. Re:Aye, but... by Anonymous Coward · · Score: 0

      Lame, on the other hand, is used in all kinds of software and by all kinds of people for legitimate reasons.

      Well it shouldn't be. From LAME's website:

      LAME is an educational tool to be used for learning about MP3 encoding.

      So it shouldn't be used for anything but learning about MP3 encoding. Of course, that's just a cutesy way for LAME to try and avoid getting sued by Fraunhofer Gesellschaft. I'll bet you Sony paid them MP3 licensing fees...

  31. Market Strategy by Anonymous Coward · · Score: 0

    "1. Install rootkit that contains licensed code without telling users 2. ???? 3. Profit!"

    2. Release new Playstation!

  32. I have a question... by ghislain_leblanc · · Score: 1

    What happens when you try to play a DRMed CD in a non-windows computer? Does is just play or is it not even recognised as a CD? I never had a chance to try, I just don't care much for the titles they have to offer. If this rootkit is meant to prevent people from ripping CDs but only works on one platform, they can't possibly think this is gonna work, right?

    Can someone explain this to me?

    Thanks

    1. Re:I have a question... by j-cloth · · Score: 1

      Nothing happens. It works like a normal CD. The rootkit (and all of the DRM) is Windows only.
      I can't find the link right now, but using a Mac is one of Sony's recommended solutions to importing their DRMed cds to an iPod.

    2. Re:I have a question... by Anonymous Coward · · Score: 0

      If the DRMd CD contains code compiled to run on Windows then nothing happens. If they wanted to target multiple OSs they'd have to include code for each. So in all non windows systems the CD will play just fine - after all the CD must contain WAV data or it wouldn't play in a standalone CD player.

      And on an OS with a sane permissions system the code on the CD wouldn't be able to run with adminstrator privileges anyway (without you expressly allowing it) so it wouldn't be able to install it's shitty root kit (without you being stupied enough to let it) either.

      So once again the "root" cause of the problem (excuse the unintended pun) is that Windows is fundamentally fucking shite. And will Microsoft ever fix it ? No. They're too busy adding bells, whistles, mirrors, flugelhorns and DR-fucking-M.

      But then again why should they care ? They're a marketing company after all and the rubes keep lapping it up.

      Quite frankly people who run Windows and who buy the sort of shite churned out by Sonys "artists" deserve this rootkit.

    3. Re:I have a question... by slick_rick · · Score: 0

      I can't believe I'm responding to an AC, but I just can't contain it...

      AMEN! Preach it brother!

      --
      apt-get install redhat please god - Me (take it easy, I love Debian)
    4. Re:I have a question... by MykeBNY · · Score: 1

      What's interesting is this uber-evil rootkit malware can be prevented from being installed by the mighty mighty shift key in Windows. Or even clicking "I do not accept" to the EULA. After that, simply then load up a favorite playback or ripping program, and voila!

    5. Re:I have a question... by Keyslapper · · Score: 1

      I don't remember where, but after a little googling last week, I found a post that suggested the DRM actually installs some Mac kernel extensions (PhoenixNub1.kext and PhoenixNub2.kext or something similar).

      I haven't yet researched whether these are actually legitimate extensions that are part of the Mac Os though (remember that old "Windows Virus" alert that convinced so many people to delete system files?).

      Use with care, even on MacOs X.

      BTW, It seems to me that if LGPL infringement can be proven, it would sure be nice to see a settlement for some fixed amount for each DRM'd CD released fed back to the open source projects infringed. Getting a cool $10 Million funding from Sony would certainly add to the quality of all these projects - not that they aren't excellent, but being able to refactor the whole codebase would undoubtedly put them in serious contention with the best players.
      Just a thought.

    6. Re:I have a question... by Keyslapper · · Score: 1

      Not necessarily. It was mentioned in one of the previous slashdot threads on this issue that by the time the Sony EULA pops up, it has already installed something (I don't remember what) into your system. Refusint the EULA sets something else up in your system according to some of the stories out there. The only thing that prevents it is turning off autoplay/autoexecute/whatever on your CD/DVD player. I don't know if the shift key affects this - I'm not a windows guru (anymore), so research this yourself before taking that chance.

    7. Re:I have a question... by Anonymous Coward · · Score: 0

      that's 2 mouth watering lines and 76 juicy sweet characters you just left on an AC's dinner plate. Please don't feed the trolls. Thanks you, and have a nice day. Bye bye now!

  33. Blame Sony? by putko · · Score: 1

    Isn't the company to blame the one that made the rootkit for Sony? It is some OEM stuff.

    I can imagine Sony doens't know much about this at all. Sure, they are the ones legally responsible -- but ultimately, they'll just sue the rootkit makers if this ever costs them a dime (unless they indemnified the other guys).

    --
    http://www.thebricktestament.com/the_law/when_to_s tone_your_children/dt21_18a.html
    1. Re:Blame Sony? by Anonymous Coward · · Score: 0

      " Isn't the company to blame the one that made the rootkit for Sony? It is some OEM stuff."

      The point missing, is that Sony Distributed the code, which is copyright infringment also. according to US Copyright Law.

    2. Re:Blame Sony? by mwvdlee · · Score: 1

      AFAIK, The (L)GPL requires sourcecode to only be freely/openly be available to _users_. Since only Sony seems to be a users (so they're the only ones who can request the code) and only Sony seems to distribute it to the public, Sony is the only one who is breaking the law.
      To resolve this (alleged; it's still not 100% clear so far; see other posts) copyright issue, Sony would have to request the code from the developers and pass it on to their customers if any customer wants access to it.
      Ofcourse those customers are free to further distribute the code to anybody under the original (L)GPL license.
      Essentially it boils down to the same, but forces Sony to be the middle man in this.
      IANAL.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    3. Re:Blame Sony? by Lisandro · · Score: 2, Insightful

      If anything, the rootkit makers are responsable of the LGPL violation (if that's proved). Saying Sony is off the hook because they licensed the rootkit from a third party is like saying Smith & Wesson is the responsable if i pick a gun and shoot someone.

          If they choose XCP knowing how it works (and what it would do), they're guilty. If they choose it unknowingly, they're incompetent. They're responsable either way.

  34. Confusing by TheComputerMutt.ca · · Score: 1

    Why isn't this labled as "Sony"? I decided to look for all articles about their great evils, only to realize that this wasn't among them.

  35. It even has some GPL compnonets by leuk_he · · Score: 4, Interesting
    looking at the licence of lame:



    *** IMPORTANT NOTE ***

    The decoding functions provided in LAME use the mpglib decoding engine which
    is under the GPL. They may not be used by any program not released under the
    GPL unless you obtain such permission from the MPG123 project (www.mpg123.de).


    So it is not only LPGL, but also the more strict GPL. This is of coarse all meaningless if nobody from the mpg123 project steps out and tells sony to go with the license.
    1. Re:It even has some GPL compnonets by Anonymous Coward · · Score: 1, Informative

      http://en.wikipedia.org/wiki/Mpg123

      "The license of the mpg123 player is GPL and the license of the mpglib inside the mpg123 package is LGPL."

      Or is wikipedia wrong...

    2. Re:It even has some GPL compnonets by WolfWithoutAClause · · Score: 1
      Actually, mpg123 project members don't have to. Sony has infringed copyright, and hence is subject to the penalties. Depending on the jurisdiction, it's thousands of dollars damages, probably per album.

      Quite honestly, I'd love to see them get thoroughly caned over this.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
  36. Re:Sony Rootkit by dwandy · · Score: 2, Informative
    Unless you're talking about shoplifting software from the local best-buy, "stealing" is incorrect.

    It's important to remember that "copy-right infringemnt" != "stealing", and if people on /. can't keep this straight, how can anyone expect Joe Public to keep it straight?

    This is as much a PR battle as a legal battle, and any succesful commercial organisation knows a thing or two about marketing/spin. And obviously judging by the crap they _sell_ (read push-on-consumers) as music and art, the *AA's must be succesful marketers.

    --
    If you think imaginary property and real property are the same, when does your house become public domain?
  37. Plus patents... by Bazman · · Score: 4, Funny
    "So apparently Sony violates your privacy to create a backdoor onto your machine using code that violates an Open Source license..."

    ... from a project that may be[1] in violation of patent law! Woohoo!

    Baz

    [1] in some lawyers opinion.... see http://en.wikipedia.org/wiki/LAME for info.

    1. Re:Plus patents... by AnObfuscator · · Score: 1
      "So apparently Sony violates your privacy to create a backdoor onto your machine using code that violates an Open Source license..." ... from a project that may be[1] in violation of patent law! Woohoo!

      So if LAME violates patent law, and Sony is redistributing LAME... does that mean Sony is violating patent law as well?

      Next slashdot headline: "Sony rootkit allegedly violates patent laws."

      ;-)

      --
      multifariam.net -- yet another nerd blog
  38. The Bad Plus, Suspicious Activity by Anonymous Coward · · Score: 1, Funny

    CD: The Bad Plus, Suspicious Activity: The empire strikes backwards

  39. Not stranger entirely consistent by Crashmarik · · Score: 2, Insightful

    The fact that sony has chosen to violate a license agreement is entirely consistent with the motion picture and music industry standard operating procedures. The only rights they acknowledge are their own. For someone else to assert their rights, would be considered meerly cheeky. Look at the Buchwald case, record industry and movie industry accounting practices.

    In short if you look at this from the perspective that these people feel that they own YOUR right to enjoy entertainment, it all becomes very consistent.

  40. "operating system on which the executable runs" by tepples · · Score: 5, Informative

    <sarcasm>Thus explaining why every single open source project includes the full GCC source tree with it?</sarcasm>

    The GNU General Public License and the GNU Lesser General Public License have an operating system exemption. The exact wording of the exemption in both licenses is as follows:

    However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

    True, the corner cases of this exemption have not been tested in a court of law, especially in conjunction with the "mere aggregation" exemption.

    1. Re:"operating system on which the executable runs" by maxwell+demon · · Score: 4, Informative

      Moreover, the gcc runtime libraries (the only part of gcc which ends up in gcc compiled code, and therefore could affect the licensing) all have special exceptions to the GPL, so that they don't cause the programs they are linked to to be covered by the GPL.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:"operating system on which the executable runs" by tbspit · · Score: 1

      No, the LGPL has no such exemption. The exemption in the GPL lets you LINK to non-free operating system software. It does not allow you to distribute the GPL code itself as non-free. Since with the LGPL you can already link to non-free software, such an exemption makes no sense and does not exist.

    3. Re:"operating system on which the executable runs" by I'm+Don+Giovanni · · Score: 2, Insightful

      The gcc runtime libraries have "special exceptions" to the GPL? Doesn't this essentially mean that that gcc libraries aren't covered under GPL but rather under their own license that's more BSD-like?

      --
      -- "I never gave these stories much credence." - HAL 9000
    4. Re:"operating system on which the executable runs" by Krach42 · · Score: 1

      Moreover, the gcc runtime libraries (the only part of gcc which ends up in gcc compiled code, and therefore could affect the licensing) all have special exceptions to the GPL, so that they don't cause the programs they are linked to to be covered by the GPL.

      The GNU Lib C library has no exceptions to the GPL, because it's covered under the LGPL.

      The LGPL requires one to give notice that it links against the LGPL library/program, and one of two conditions must be met: if the LGPL library/program is linked dynamically, then not much need be done. You just have to make sure that they can swap the library for a newer version.

      If the LGPL is statically linked, then you must give at least the object files to your program so that people can relink your program against a newer version of the library/program.

      Also, if no changes were made at all to the source code, then no release of source code is required, it's sufficient to say "we didn't modify the source code at all, and you can get the source code at..." and you know this would be true, because you're allowed to relink a newer/older version of the library to that program, and if it breaks, then you can start attempting to prove that they did change something.

      But all of this doesn't change the fact that the GNU C Library is covered under the LGPL and not the GPL. The GNU group would never release something under the GPL with an exception for allowing to link against it without becoming GPL, because that's the purpose of the LGPL.

      --

      I am unamerican, and proud of it!
    5. Re:"operating system on which the executable runs" by tepples · · Score: 1

      The GNU Lib C library has no exceptions to the GPL, because it's covered under the LGPL.

      You're talking about GNU libc. Maxwell demon is talking about libgcc. They're separate products. Libgcc is a generally smaller library that handles things such as program startup and floating-point emulation that even a "freestanding" implementation of ANSI C (one without an implementation of stdio.h, stdlib.h, etc) is expected to handle. A lot of programs for embedded systems use their own minimal libc but use the compiler's libgcc.

    6. Re:"operating system on which the executable runs" by Krach42 · · Score: 1

      Ah, that would be a different matter.

      I can't find anything online specifically about what license it is covered by, but I'm willing to admit that I'm likely wrong here.

      --

      I am unamerican, and proud of it!
    7. Re:"operating system on which the executable runs" by opbarnes · · Score: 1

      ... In addition to the permissions in the GNU General Public License, the Free Software Foundation gives you unlimited permission to link the compiled version of this file into combinations with other programs, and to distribute those combinations without any restriction coming from the use of this file. (The General Public License restrictions do apply in other respects; for example, they cover modification of the file, and distribution when not linked into a combine executable.) ...

    8. Re:"operating system on which the executable runs" by Krach42 · · Score: 1

      Awesome thanks.

      --

      I am unamerican, and proud of it!
  41. Sony needs to protect its image... by digitaldc · · Score: 4, Insightful

    ...not its CDs. They have done more to damage their image and profits with this story than they would have saved by installing its spyware.
    I also feel sorry for the poor chap who buys Ricky Martin, Neil Diamond or Celine Dion CDs, I really do.
    Sony should have some kind of disclaimer about installing its bad software, maybe a 'Spyware Advisory' sticker? It is only fair.

    --
    He who knows best knows how little he knows. - Thomas Jefferson
    1. Re:Sony needs to protect its image... by UtucXul · · Score: 0, Offtopic
      I also feel sorry for the poor chap who buys Ricky Martin, Neil Diamond or Celine Dion CDs, I really do.
      I only feel sorry for the people around the person who buys Ricky Martin, Neil Diamond, or Celine Dion CDs.
    2. Re:Sony needs to protect its image... by ettlz · · Score: 4, Funny
      I also feel sorry for the poor chap who buys Ricky Martin, Neil Diamond or Celine Dion CDs, I really do.

      Yes, but what about the DRM issue on these CDs?

    3. Re:Sony needs to protect its image... by Anonymous Coward · · Score: 0

      If you look at their stock, it doesn't look like their image has been hurt, at least to the investors.

    4. Re:Sony needs to protect its image... by Trails · · Score: 0

      Bad software nothing, they should give a disclaimer about listening to bad MUSIC to people buying those artists...

    5. Re:Sony needs to protect its image... by mpe · · Score: 2, Funny

      ...not its CDs. They have done more to damage their image and profits with this story than they would have saved by installing its spyware.

      Probably also increased the amount of their material being pirated. Since those wanting to listen to those artists are likely to prefer a "clean" copy.

  42. So... How about them statutory damages... by 91degrees · · Score: 1

    Sony have knowingly distributed an unknown number of copies of this file. I believe this allows the LAME authors to claim statuory damages of between $250 and $150 000 per infrignement.

    Anyone know what an "infringement" is in this case? Is it a single copy or a single work?

    1. Re:So... How about them statutory damages... by msdschris · · Score: 1

      If you were to copy a sony CD 1,000's of times and sell it how would you be fined if convicted?

    2. Re:So... How about them statutory damages... by Yartrebo · · Score: 5, Insightful

      IANAL, but judging from the RIAA's press releases when they sue grannies and kids, it's per copy and per work. So let's do the math. 20CD * 1 million copies each * $150,000/copy = $3 trillion dollars. That's if there's only 1 work on each copy. If they also infringed on several other projects, then you would have to multiply the damages accordingly.

    3. Re:So... How about them statutory damages... by Anonymous Coward · · Score: 2, Insightful

      don't forget the jailtime the beloved attorney general is pushing for copyright infringement...

    4. Re:So... How about them statutory damages... by HarvardAce · · Score: 1
      So let's do the math. 20CD * 1 million copies each * $150,000/copy = $3 trillion dollars.

      To prevent us from completely destroying your company's image, you must pay me.... 3 treeeeeelion dollars! You have my instructions, I bid you adieu.

      --
      Note to self: Stop putting jokes in my insightful comments so I can get something other than +1 Funny!
    5. Re:So... How about them statutory damages... by Jah-Wren+Ryel · · Score: 2, Interesting

      So let's do the math. 20CD * 1 million copies each * $150,000/copy = $3 trillion dollars.

      What incredible irony it would be if the LAME group ended up owning Sony Corp.
      Yeah, I know, not a chance in hell, but one can dream...

      --
      When information is power, privacy is freedom.
    6. Re:So... How about them statutory damages... by Hatta · · Score: 4, Insightful

      Any of you LAME developers reading? Please PLEASE! don't settle!

      Just once, I'd like to see a major corporation wiped off the face of the earth because it violated the law. It would send a nice message to the other megacorporations. If you're going to use the law as a weapon against us, we can use it right back.

      So please, talk to the EFF. I'll donate whatever I can to the legal fund.

      --
      Give me Classic Slashdot or give me death!
    7. Re:So... How about them statutory damages... by Alsee · · Score: 4, Interesting

      Ummm, does anyone know how many programmers (also know as copyright holders) have code in LAME?

      Because each copyright holder can sue independantly.

      Oh, and in case anyone forgot the RIAA sued a college student for $97.8 Billion. SO they have absolutely no right to bitch about how supid-huge copyright infringments can get to be. Their own lawyers participated in drafting the law the stupid-ass damages.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    8. Re:So... How about them statutory damages... by bbc · · Score: 1

      "$3 trillion dollars"

      Is that even a real number? What does that mean, 3 trillion dollars? Which country would you buy?

      Anyway, if anybody is going to sue, I suggest freezing all assets and bank accounts of any person or organisation even remotely linked to Sony. And do that yesterday. Otherwise they will be routing money out of the US faster than you can say DRM.

  43. I don't think it contains LGPL code. by SaleNowOn · · Score: 1, Interesting

    I'm sure I'm about to be proved wrong on this but....

    The strings just look to be a part of a search function for various LAME versions on the users computer,
    and both programmes contain an array with the highly original title of "largetbl".
    "Large Table" for those non programmers amongst us.
    I'd like to see a bit more evidence before I cry foul.

    What I find interesting. Why the Sony Rootkit is looking for LAME in the first place?
    Does it alter or break LAME in in some way if LAME is found ??

  44. Notification? by Grendel+Drago · · Score: 4, Funny

    This is all so ridiculous. It's not like Sony even asks the user if they want this crap installed. Where would they even put the copyright notice? Of all the underhanded nonsense...

    --
    Laws do not persuade just because they threaten. --Seneca
    1. Re:Notification? by Professor_UNIX · · Score: 5, Funny
      This is all so ridiculous. It's not like Sony even asks the user if they want this crap installed. Where would they even put the copyright notice? Of all the underhanded nonsense...

      This is the problem with the viral nature of the GPL and even the LGPL licenses and is why you should really consider using BSD licensed software in your DRM rootkits in the future. Screw the FSF!

    2. Re:Notification? by AvitarX · · Score: 1, Troll

      Do you mean the problem is you can't use it in stealth rootkits because everyone would be warned or the distributer is comitting copyright violation?

      To me this appears to be a case that the LGPL is doing its job well.

      The irony of things is that every CD distributed with help prevent infringement software is in itself a copyright violation.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    3. Re:Notification? by Randall_Jones · · Score: 2, Insightful

      why does someone who doesn't get the joke get modded to insightful?

    4. Re:Notification? by Anonymous Coward · · Score: 0

      The copyright notice and EULA are clearly in c:\$Sys$COPYRIGHT_NOTICE

      Your rights under the agreement are set out in this file c:\$Sys$YOUR_RIGHTS

    5. Re:Notification? by Bootvis · · Score: 2, Informative

      Because he's not alone? Lots of retards have modpoints.

      --
      Read, refresh, repeat.
    6. Re:Notification? by Anonymous Coward · · Score: 1, Insightful

      Whoooooosh!

    7. Re:Notification? by Anonymous Coward · · Score: 1, Informative

      And you're at Score:3, Insightful. The ultimate irony!

    8. Re:Notification? by Anonymous Coward · · Score: 0

      Viral is often used because many non believers in the GPL hate the fact that using GPL code essentially means you must GPL everything. For example, if I create a BSD Licensed application and then add gpl code it then must be released under GPL. This causes my code to be downgraded to GPL status. I don't want to protect the code from theft, I want EVERYONE to use the code. The GPL limits this FREEDOM. Its all about perspective.

      I have released code under gpl and bsd licenses. I've concluded over time that its stupid to release anything "Open source" if everyone can't use it. It defeats the purpose. GPL really pushed the envelope and got us to this point, but the BSD license means that code is truely free. I don't care if people submit patches or what not if i release code open source. IF they do great, if not glad they got use of the code anyway.

      You GPL types don't get that. Think of it this way, you borrow code with GPL.. much like you borrow beer.. it goes in as beer and you get piss in return. You get pure linux kernel source in and you get IBM bastardized code out (piss). Code thats submitted back to bsd licened projects tends to be mature before the patch is put in the code. Usually people run it for at least 6 months before their realize they want it in the main tree so they don't need to maintain it.

      Free as in beer isn't a good thing. I think of the BSD license as Free as in Advice. You can take it or leave it but its yours to keep forever.

    9. Re:Notification? by einhverfr · · Score: 2, Insightful

      This is the problem with the viral nature of the GPL and even the LGPL licenses and is why you should really consider using BSD licensed software in your DRM rootkits in the future. Screw the FSF!

      There is a psychology term called "projection" which is very important here. In this case and in the case you can sum it up as the rule that those who complain loudest about copyright violations are likely to be violating other peoples' copyrights.

      --

      LedgerSMB: Open source Accounting/ERP
    10. Re:Notification? by Lonath · · Score: 1

      Or, as I put it: "Gifts don't come with strings attached."

    11. Re:Notification? by thre5her · · Score: 3, Interesting

      Great, then rewrite all those awesome GPL libraries you link to and release the code under BSD. Better yet, just release it into the public domain, with *no* strings attached. Nobody's holding a gun to your head, and frankly, nobody cares what you do with *your* code. However, if you use *my* GPL'd code in your BSD-licensed program, you had better GPL your project, otherwise someone may take credit for *my* work; leaving you with one pissed-off developer hounding your ass.

    12. Re:Notification? by Anonymous Coward · · Score: 0

      But GPL is supposed to be viral. You know, like antivirus? It doesn't matter if some company can't use the code in their proprietary application. What matters, is that there is no such word as 'proprietary' in the Free Software Land, and that nobody actually cares. Except the companies, of course.

    13. Re:Notification? by coolgeek · · Score: 2, Insightful

      GPL source is not a gift.

      --

      cat /dev/null >sig
    14. Re:Notification? by Anonymous Coward · · Score: 0

      So it's your code then huh? So much for information wants to be free.

    15. Re:Notification? by Miros · · Score: 1

      Yes. And i'm sure he also has the time/money/resources to first, discover that you're misusing his software and second, take the time and the cash to sue you over it. It's fairly easy to assume that by far the vast majority of individuals who distribute software under the GPL are not this passionate about it, making much of this high minded debate pointless.

      If someone wants to steal your software, and you dont have the balls, the time, and the money to defend it, then what's the point on citing passages of the GPL all the time. It's only worth your willingness to go to war over it.

    16. Re:Notification? by Miros · · Score: 1

      Why should the companies care? I maintain that open source doesnt not have to be anti-capitalist... If you have a well run company, with an innovative product that you market correctly, open source software is of no threat, in fact, it's probably a benefit to your business if used properly. If anything, a free and open source software world would probably make most companies better off and more profitable since it would dramatically reduce their costs and increase their productivities.

    17. Re:Notification? by Anonymous Coward · · Score: 1, Funny

      There is a psychology term called "projection" which is very important here. In this case and in the case you can sum it up as the rule that those who complain loudest about copyright violations are likely to be violating other peoples' copyrights.

      There is a term called "psychologist" which is very important here. In this case you can sum it up as the rule that those who study psychology and bring up psychological terms on internet message boards are likely to be crazy.

    18. Re:Notification? by einhverfr · · Score: 1

      Thanks. Best laugh I have had in a long time....

      --

      LedgerSMB: Open source Accounting/ERP
    19. Re:Notification? by Anonymous Coward · · Score: 0

      Um, yes, my bad. I didn't mean I'm against companies in general, just arguing parent that GPL does not limit _any_ freedom in a free world. Since when taking away freedom qualifies as freedom?

  45. ... or maybe yes by muzzy · · Score: 5, Interesting

    That only concerns GO.EXE, and while the analysis is correct for that executable, I checked for LAME references against every binary in the compressed XCP.DAT file after I managed to unpack it (thanks to freedom-to-tinker.com guys for providing description of the format). Turns out, there's more binaries including references to LAME, and this time there's actually code that uses the data as well. And not just LAME, there's also Id3lib included in one dll, and bladeenc and mpglib distributed along with the DRM. All of this is LGPL, it's code, and it's being used.

    --
    -- Matti Nikki
  46. LAME is in there, just not in GO.EXE by muzzy · · Score: 4, Informative

    Regarding GO.EXE, it's a cockup. I've posted a few other posts here explaining the real situation. LAME along with some other LGPL code is being used in other binaries on the DRM, I couldn't initially find them since they're compressed in XCP.DAT on the cd but they get installed on the system.

    --
    -- Matti Nikki
  47. Not really stranger by djsmiley · · Score: 1

    Sony hired someone to stop people doing the dirty with their cds. What happened was they got someone (or some company) who either dont have ethics or morals, or are just plain dumb and gave sony exactly what they wanted. And now sony are paying the price.

    --
    - http://www.milkme.co.uk
  48. Article Text (dewinter.com dead) by Anonymous Coward · · Score: 2, Informative
    Spyware Sony seems to breach copyright
    Posted on Thursday, November 10 @ 11:44:47 CET by brenno

    GNU / GPL (Copyleft) The spyware that Sony installs on the computers of music fans does not even seem to be correct in terms of copyright law.

    It turns out that the rootkit contains pieces of code that are identical to LAME, an open source mp3-encoder, and thereby breach the license.

    This software is licensed under the so called Lesser Gnu Public License (LGPL). According to this license Sony must comply with a couple of demands. Amongst others, they have to indicate in a copyright notice that they make use of the software. The company must also deliver the source code to the open-source libraries or otherwise make these available. And finally, they must deliver or otherwise make available the in between form between source code and executable code, the so called objectfiles, with which others can make comparable software.

    Sony complied with non of these demands, but delivered just an executable program. A computerexpert, whose name is known by the redaction, discovered that the cd "Get Right With The Man" by "Van Zant" contains strings from the library version.c of Lame. This can be conluded from the string: "http://www.mp3dev.org/", "0.90", "LAME3.95", "3.95", "3.95 ".

    But the expert has more proof. For example, the executable program go.exe contains a so called array largetbl. This is a part used in the module tables.c of libmp3lame.

    This discovery can have far-stretching consequences for the music giant, who claims only to protect copyrights. Previously, judges in Germany already forced various companies to release source code to the public and to deliver the goods necessary for compiling. It is also possible to demand financial compensation for damages.

    Meanwhile, Other details are also becoming clear. The Electronic Frontier Foundation complains that the spyware makes the legal listening to the music on iPods impossble. The organisation is busy making a list of cds containing the hidden software and publishes this on her website.

    Various calls to SonyBMG remained unanswered despite promises to call back.

  49. Sabotage from within? by jeffs72 · · Score: 5, Interesting
    I could see the developer who had this project fall in his lap say "this is fucking stupid, lets teach them a lesson on integrating spyware with their cds" and violating this license (which will give them a black eye) and then write it in such a way that people can easily use it as a virus/trojan vector.

    The more I think about it, it really smells of dissention from within.

    Either that or it looks to me like this is a mix of business people not understanding their market, customers, or technology and sloppy code work. I mean, what asshat would grab some open source code and not adhere to the license? It is either a tremendous faux pas on Sony's part, or there was some intentional act here to make this as reprehensible as possible.

    Sort of like watching the music industry test the waters on this sort of thing and finding them extremely chilly.

    --
    This article has recently been linked from Slashdot. Please keep an eye on the page history for errors or vandalism.
    1. Re:Sabotage from within? by PeteDotNu · · Score: 3, Insightful

      "It is either a tremendous faux pas on Sony's part, or there was some intentional act here to make this as reprehensible as possible."

      IF the allegations are true, then I expect that Sony have actually been doing this kind of thing for years and getting away with it. Only NOW are people taking a closer look at Sony's code to see exactly how deep this seam of faeces runs.

      --
      My other processor is big-endian.
    2. Re:Sabotage from within? by Saint+Aardvark · · Score: 2, Insightful
      I mean, what asshat would grab some open source code and not adhere to the license?

      The sort of asshat who would write this thing in the first place?

    3. Re:Sabotage from within? by RoffleTheWaffle · · Score: 1

      So in other words... either First 4 Internet is full of geniuses or idiots. I'm putting my money on the latter. As for Sony, well...

      I don't think the possibility actually exists that they aren't being commanded by a troupe of retards.

    4. Re:Sabotage from within? by Anonymous Coward · · Score: 0

      hahhaah. Funny thought, but I doubt its the case. Others have said that the rootkit is poorly implemented and contains potential bugs, and the uninstaller from the rootkit company doesn't uninstall in a safe way (i.e. potential blue screens). So the rootkit company has crappy programmers. No, odds are that this company got the idea to do this with a couple of college studends and somehow knew someone in sony and approached them. Perhaps they were distant relatives of a VP or something. Then they told sony "yeah we can do some GREAT copy protection and best of all it will be hidden from the user so they cant complain about it." And threw out some other touchy feely crap. Sony sucked it up, paid them probably a small fee (my guess, a flat fee, no royalties, $100,000 probably sounds like big money to a couple college students, but its really peanuts), and went with it. No one at sony looked at the technical details and no one there knows about it, so they say "omg no we dont collect data" because they actually dont know.

      As for the open source stuff, another case of people not reading the liscense, and thinking open source means I can copy it and use it for wtf I want (not realizing the must release source code restrictions, etc).

      In other words, think more incompentance, not malice.

    5. Re:Sabotage from within? by frank_adrian314159 · · Score: 1

      Chances are some mid-level project manager outsourced the DRM development to some thrid-world job shop that realy doesn't understand or give a rat's ass about IP issues at all. And, of course, when the stuff came back, same mid-level (probably non-technical) functionary didn't even think about where the code came from, what it was made of, or anything else. In short, the kind of thing that goes on all the time unless you actually know what the hell you're doing...

      --
      That is all.
    6. Re:Sabotage from within? by BillKaos · · Score: 2, Insightful

      "never attribute to malice that which can easily be explained by stupidity"

    7. Re:Sabotage from within? by jsdcnet · · Score: 1

      "Either that or it looks to me like this is a mix of business people not understanding their market, customers, or technology and sloppy code work. I mean, what asshat would grab some open source code and not adhere to the license? It is either a tremendous faux pas on Sony's part, or there was some intentional act here to make this as reprehensible as possible." Never attribute to malice that which is adequately explained by stupidity.

      --
      no longer working for cnet
    8. Re:Sabotage from within? by T-Ranger · · Score: 1

      Someone who likes getting a cheque every two weeks, and have it clear.

    9. Re:Sabotage from within? by Anonymous Coward · · Score: 0

      Well, they don't care when suing if you knew you were geting an illegal copy. They don't care if you are allowed to agree to a contract, they don't care if it wasn't you but another using your computer.

      So why should I care if they outsourced or didn't check?

    10. Re:Sabotage from within? by Thud457 · · Score: 2, Funny

      "I told them I wanted my red stapler back."

      --

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

    11. Re:Sabotage from within? by randyflood · · Score: 1
      I mean, what asshat would grab some open source code and not adhere to the license?

      Maybe they were former SCO employees...

      --
      Randy.Flood@RHCE2B.COM
    12. Re:Sabotage from within? by dangitman · · Score: 1
      I mean, what asshat would grab some open source code and not adhere to the license?

      It's a Sony!

      --
      ... and then they built the supercollider.
    13. Re:Sabotage from within? by SpecBear · · Score: 2, Insightful

      I mean, what asshat would grab some open source code and not adhere to the license?

      The same asshat who writes software that violates the property and privacy rights of paying customers.

  50. The perfect comment by Anonymous Coward · · Score: 3, Funny
  51. Re:Thank god! - What's Next by Analogy+Man · · Score: 1, Funny
    The still untold story is the exploited child slave labor used to add this backdoor with their small nimble fingers...

    ....and don't mention the countless fuzzy bunnies that died in the animal testing phase of Barbara Streisand's latest release.

    --
    When the people fear their government, there is tyranny; when the government fears the people, there is liberty.
  52. Re:Sony Rootkit by AndroidCat · · Score: 2, Funny

    Too bad. I've certainly wanted to be able to execute a lot of the music that's published today.

    --
    One line blog. I hear that they're called Twitters now.
  53. Ironic? by Rakishi · · Score: 4, Insightful

    First of all it seems that there is more than just LAME in there: http://hack.fi/~muzzy/sony-drm/

    Second of all, am I the only one who finds it ironic that a DRM program designed to protect someone's copyrighted information is itself infringing on someone's copyright? I guess if Sony wants to fight those evil copyright violators they should start by putting themselves in jail.

    1. Re:Ironic? by ender- · · Score: 2, Funny

      Second of all, am I the only one who finds it ironic that a DRM program designed to protect someone's copyrighted information is itself infringing on someone's copyright?

      Well I suspect that if you *were* the only one who felt that way, this story wouldn't be on the front page of Slashdot. So no, you're probably not the only one.

      Of course, that's just my opinion. I could be wrong.

      ender-

    2. Re:Ironic? by mpe · · Score: 1

      Second of all, am I the only one who finds it ironic that a DRM program designed to protect someone's copyrighted information is itself infringing on someone's copyright?

      It's ironic, but hardly unexpected.

      I guess if Sony wants to fight those evil copyright violators they should start by putting themselves in jail.

      Or into political office :)

    3. Re:Ironic? by loyukfai · · Score: 1

      Except that you can't actually put a corporation into jail.

    4. Re:Ironic? by 615 · · Score: 1
      Second of all, am I the only one who finds it ironic [...]

      Uh, no, you're not.

  54. PLEASE, EDITORS CHECK GRAMMAR AND SPELLING by Anonymous Coward · · Score: 1, Informative
    • ... However, the source code has not also been distrbuted, hence breaching the license. Here is an english translation of the page....
    sigh,
    • distributed
    • English translation
    1. Re:PLEASE, EDITORS CHECK GRAMMAR AND SPELLING by Anonymous Coward · · Score: 0

      sigh,

      As if "sigh," is grammatically correct sentence!

  55. I don't get it by chrisgeleven · · Score: 2, Insightful

    Why would Sony include LAME (or parts of it) in with this rootkit? LAME is just a mp3 encoder.

    Unless Sony wanted high quality mp3's made from the CD (which I seriously doubt for some strange reason), I don't get why they would put it in there.

    It isn't like LAME has any DRM itself. Far from that.

    Anyone have any ideas?

    1. Re:I don't get it by jrcamp · · Score: 2, Interesting

      I read an article a week or so back saying that the rootkit would insert spots of noise into MP3's when you tried to burn them to degrade the quality. Perhaps this is where LAME could be used? Anybody know the article I'm talking about and can link it?

    2. Re:I don't get it by Arend · · Score: 1

      The kit contains a player, which apparantly supports mp3 playback. And since LAME can also de-code mp3, I assume they've used LAME for that task...

    3. Re:I don't get it by Walkiry · · Score: 4, Interesting

      >Anyone have any ideas?

      Well, according to some people who have had to exorcise the demon from their windows PC, what happened after installing the rootkit is that MP3 files ripped from other CDs came back worse to wear, with noise, loss of quality and whatnot.

      If that is true, you can probably connect the dots easily and see what Sony was after :-)

      --
      ---- Take the Space Quiz!
    4. Re:I don't get it by Anonymous Coward · · Score: 0

      A great question! Here's one possible scenario: The DRM hooks into the file system "create/modify file" function. When an application produces a file with an .mp3 extension, the DRM compares ID3 tags or a summary of the encoded audio against a list of protected tunes; if there's a match, it could quietly delete or corrupt the file. This way, not only would the DRM be able to stop known encoding programs, but it could also stop unknown encoders that produced an .mp3 file with the protected content. To produce a summary of the audio, the DRM would need at least an MP3 decoder like LAME.

    5. Re:I don't get it by WhiteWolf666 · · Score: 1

      LAME can be used for mp3 playback.

      Also, I believe the software allows you to rip one (three?) copies of the CD to your hard drive. Sony's DRM could be some form of encryption applied to bog-standard mp3s. Or they could use a portion of lame, or something like that.

      I was reading dilbert on the porcelain throne this morning, and I glanced over the comic where wally is coding the critical code for the nation's air traffic control system.

      "Suddenly, the gifted programmer employees a rarely seen strategy of, 'code reuse'"

      "The Crowd goes Wild!"

      First4Internet sounds like a fly by night operation, and I wouldn't be surprised if they just stole lame for this purpose rather than license some encoder at $x per copy.

      Even if they licensed it from Sony, their customer, it would cut into their fee.

      Free > Fee to these people, and they obviously don't give a flying fuck about ethics.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    6. Re:I don't get it by RGRistroph · · Score: 1

      Or maybe they just wanted to extract the mp3 tags information from the file to catalog and send back to the mother ship.

    7. Re:I don't get it by slide-rule · · Score: 1

      Wondering out loud ... if the "noise" is a machine-unique watermark which is being phoned home back to sony, it'd give them a way to trace back instances of a given P2P'ed rip to someone's machine.

  56. Sony by Stephan+Seidt · · Score: 2, Funny

    Maybe it was planned to upload the source later through their backdoor.

  57. In Case Anybody's Losing Track by trentrez · · Score: 5, Informative

    FYI. BoingBoing have compiled a comprehensive timeline of events surrounding this: http://www.boingboing.net/2005/11/14/sony_anticust omer_te.html

  58. Re:Thank god! - What's Next by DikSeaCup · · Score: 3, Funny
    Not just bunnies, but many cute furry animals die when subjected to Barbara Streisand's music.

    I know it causes me significant pain ...

  59. Reverse engineering by Durzel · · Score: 1

    If it is necessary to reverse-engineer something thus breaking Sony's EULA in order to prove that Sony themselves broke the LGPL by including LAME MP3 code without the accompanying source... who is in the wrong?

    If you hack into a website to prove that the company is storing customer details against the Data Protection Act (or whatever applies), are you suddenly in the right?

    1. Re:Reverse engineering by MykeBNY · · Score: 1

      It's not just the discovery of the encoding software, not only did the EULA have to be broken, but the DMCA as well, just to detect that it was a rootkit in the first place.

    2. Re:Reverse engineering by DMNT · · Score: 2, Informative

      Depends on the location. Muzzy lives in Finland, where a consumer has a limited right to reverse-engineer software they have legally received. This right is also non-contractable, so you can't give this right away in a contract, the part of the contract that holds limitations to reverse-engineer is invalid.. Also a common lawyers' opinion is that EULAs don't hold yet no one has tested them in court. Seems to me that companies' lawyers consider the EULA invalid too. After the money has changed hands you can no longer place new limits to the use of a product.

      Now that Muzzy has the facts that were obtained legally, using them is free. You can't violate an EULA by reading a website criticizing the software.

      --
      ?SYNTAX ERROR
  60. Sony...the other red meat. by Captain+BooBoo · · Score: 1

    I mean really folks, this is just the way Sony does business...they care not for any but the pot of gold. I have had many run ins with the company from the PIC-2000 to the rootkit...I think they will pay dearly for rootkiting millions of unsuspecting customers. They deserve the ame treatment any other hacker would get if caught and charged.

  61. i concur by Anonymous Coward · · Score: 0

    i love my trinitron

    good picture and an extremely high resolution for the price

    1. Re:i concur by SillyNickName4me · · Score: 1

      So do I (having some 5 of them around, the biggest being at around 28", and using oen right now).

      Some people are bothered by those 2 wires however.. and I found it funny to see someone complaining about the bottom one but not the top one...

  62. no excuse by r00t · · Score: 4, Interesting

    Sony may claim to be looking for LAME. If so, they are using copyrighted samples to do it.

    Since Sony already argues against fair use of samples, one need only supply the court
    with Sony's own arguments against fair use.

    1. Re:no excuse by Anonymous Coward · · Score: 0

      It may also be possible that Sony's kit is trying to LOOK LIKE LAME, in order to replace and disable any LAME rippers/decoders that may be on the system. In this case, they are intentionally disabling other software you have installed on your system without your permission. Another nasty, and probably illegal, thing to do.

  63. Modding up... by xtracto · · Score: 1

    Just a small comment on your comment:
    Mods please avoid modding up the grandparent.

    I think your comment (your GP) is still interesting although it may not be accurate, why?, if you see [your]parent comment, correcting you, you can see the poster did not quoted what he was correcting.

    I stumble very often with these kind of comments, someone posted a comment which it has lots of replies, the replies are answering back to it and are modded 3 or 4, but the original post is at 1 or less, so I can not see it (as I always read at 2).

    I think the mod system should give an +1 interesting when the post has some high (+4, +5) interesting/insighful modded replies.

    --
    Ubuntu is an African word meaning 'I can't configure Debian'
    1. Re:Modding up... by MadFarmAnimalz · · Score: 1

      +1 contextually relevant, perhaps? :)

      --
      Blearf. Blearf, I say.
    2. Re:Modding up... by Al+Dimond · · Score: 1

      It wouldn't even have to be built into the mod system such that it gave the post in question a real boost; it could be handled as a modifier that could be enabled/disabled by users (like how they can enable any extra local modifier for comments modded with any particular label, they could have a "has good kids" modifier).

      Trouble is, if this was default on, it could be badly abused by trolls (place an actual insightful comment under some nasty troll, and the nasty troll gets local modification). At least that wouldn't be as bad as actually auto-modding the nasty troll up automatically and giving its poster extra karma.

  64. What does the rootkit do when it detects LAME? by dmoen · · Score: 5, Interesting

    1. It seems that Sony has not actually included any executable code from LAME, only some data, which is likely used as a signature, to determine if you have LAME installed and are using it to rip MP3s. This is likely fair use, not wholesale copyright violation, as far as LAME and the LGPL are concerned.

    So the interesting question is: what does the rootkit do when it detects LAME on your hard drive? Does it disable or corrupt LAME? Does it phone home? Does it automatically initiate an RIAA lawsuit?

    *This* is what I think the next Sony class-action lawsuit should be about. I doubt there is enough grounds to get them on an LGPL copyright infringement suit.

    2. Muzzy points out that the Sony uninstaller installs a "safe for scripting" Active-X control with remotely exploitable entry points for rebooting your machine and possibly for installing arbitrary code on your machine. More fuel for the tasty class action suits that are starting up.

    3. Sony has done so many evil things with the rootkit fiasco (and we haven't discovered them all yet); the outrage is spreading, and it may lead to a major backlash against the whole industry practice of distributing corrupted CDs in the name of DRM. Here's hoping for a brighter tomorrow.

    Doug Moen.

    --
    I have written a truly remarkable program which this sig is too small to contain.
    1. Re:What does the rootkit do when it detects LAME? by Nynaeve · · Score: 2, Informative

      This google cache link seems to imply that LAME code was indeed used. The presence of an internal data structure contained within LAME source code was present in the executable go.exe. I'm willing to bet there is enough evidence to get a copyright suit started. It would be so ironic.

    2. Re:What does the rootkit do when it detects LAME? by VENONA · · Score: 1

      I loved "2. Muzzy points out that the Sony uninstaller installs a "safe for scripting" Active-X control with remotely exploitable entry points for rebooting your machine and possibly for installing arbitrary code on your machine. More fuel for the tasty class action suits that are starting up."

      One of the things that makes Active-X so very broken from a security standpoint is that the entire model is based upon code signing: "I know where this came from, and I trust them."

      In the case of the uninstaller, this means trusting the coporation that you know just installed a process and file hider on your system. And people are using it! Argh! The only recovery from this install is a system reload, and restoring data from backups.

      VENONA throws hands in air, walks away in disgust.

      --
      What you do with a computer does not constitute the whole of computing.
    3. Re:What does the rootkit do when it detects LAME? by h4ck7h3p14n37 · · Score: 1

      Did I read that correctly? You're saying that the uninstaller actually installs additional backdoors?

    4. Re:What does the rootkit do when it detects LAME? by VENONA · · Score: 1

      You did indeed. See:
      http://www.freedom-to-tinker.com/?p=927

      A remote reboot exploit exists as a proof of concept.

      Sony has hit bottom, and commenced digging.

      --
      What you do with a computer does not constitute the whole of computing.
    5. Re:What does the rootkit do when it detects LAME? by NutscrapeSucks · · Score: 1

      Uh, every Firefox plugin is "safe for scripting". If you run a thirdparty (un-)installation program, it could easily install a nasty firefox plugin that achives the exact same effect as this ActiveX control.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    6. Re:What does the rootkit do when it detects LAME? by VENONA · · Score: 1

      Yuck. Well, at least many of the more popular extensions get at least some degree of user testing, for whatever that's worth. Not too much, IMHO. That's nearly always a far better test for functionality than security.

      When I had to keep one Win machine in my cube I tried to keep the extension count to a minimum. I also had to run some other things I wasn't too comfortable with, but luckily I also had to have a Linux machine for development work. So I used that for connecting to the Unix machines, where security was most important (large closed-source Unix servers, Checkpoint Firewall-1, which ran on a stripped OpenBSD, etc.).

      This definitely wasn't an environment where you'd want to risk having a keylogger installed.

      Obviously, anything that went to the cloud was done from that Linux machine as well. We had lots of people running Win getting various bits of spyware, etc., installed, giving the MIS folk problems to chase. I never had a problem.

      --
      What you do with a computer does not constitute the whole of computing.
  65. I hate to prove your stupidity, but.. by Khyber · · Score: 1

    So, maybe Sony is just stupid and inept. After all, look at the trinitron monitors, with that horizontal wire ~ 1/3 of the way from the bottom;

    There's also a wire 1/3 of the way from the top, and those wires are there for a VERY SPECIFIC REASON: To adjust your monitor settings, like convergence of electron beams, for a razor-sharp image, AND realigning your monitor and adjusting it for every individual resolution that you run (sometimes Trinitron monitors will put an image slightly off-screen when switching resolutions, using those wires, you can re-align the image to a proper position, and save those changes.)

    I happen to own a 21" Trinitron monitor, and I've had to reset things many times. Those wires come in VERY handy.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    1. Re:I hate to prove your stupidity, but.. by Anonymous Coward · · Score: 0

      Bonehead. They have nothing to with alignment. They stabilize the screens. Without the wires your picture would go all to hell as the screens sagged and wobbled.

  66. Spin Off by PacketScan · · Score: 1

    I had an overwhelming feeling that BMG will be Spun from Sony.

  67. Not Sony by MaestroSartori · · Score: 4, Interesting

    Disclaimer: I'm a Sony employee, and I strongly disapprove of the rootkit DRM stuff in a completely unofficial not-representative-of-the-company way ;)

    But it's worth mentioning at this point that Sony didn't develop the software in question here - the XCP software was developed by First4Internet.

    Not being a lawyer, or particularly knowledgable about (L)GPL terms, who could be held liable when a piece of software is developed by one party, but distributed by another? Is ignorance a defence, for instance if Sony said "We didn't know it had unlicensed code!", how would that affect things?

    1. Re:Not Sony by lightweave · · Score: 2, Insightful

      Is ignorance a defence, for instance if Sony said "We didn't know it had unlicensed code!", how would that affect things? It depends on your contracts wether this is a defence or not. If I'm an unsuspecting customer that goes into a shop and buys a copy of Microsoft Word I doubt that I can be hold liable if there is an unlicenced piece of code in there hidden. If I develop In-House and a programmer includes unlicenced code I might be liable. In the case of Sony it depends on what the contracts say, but I doubt that Sony would be liable if they just bought the complete software and customized it to their needs.

    2. Re:Not Sony by Anonymous Coward · · Score: 0

      >But it's worth mentioning at this point that Sony didn't develop the software in >question here - the XCP software was developed by First4Internet.

      Yes, that's right! Lee Harvey Oswald also didn't kill JFK - it was the fault of the bastard who invented Gun Powder!

      >"We didn't know it had unlicensed code!", how would that affect things?

      "I didn't know it was unlicensed music!", how would that affect things?

    3. Re:Not Sony by jrcamp · · Score: 5, Insightful

      "But I didn't know my Internet connection was being used by my son to download Sony BMG artists' songs!"

      "I'm sorry sir but you're the owner. You owe $500,000 in damages."

      They don't allow the "but I didn't know" explanation. Why should they be allowed to use it? I say try to nail them. They've done far worse to others.

    4. Re:Not Sony by Kickasso · · Score: 2, Insightful

      So it appears I can violate anything and everything as long as there's a subcontractor that does all the dirty work? Interesting.

    5. Re:Not Sony by MaestroSartori · · Score: 1

      I thought the RIAA just sued the kids... :)

    6. Re:Not Sony by AceyMan · · Score: 1

      Ahh, the old "I just hired the hitman, I didn't pull the trigger, Your Honor" defense.

      It should go without saying, when you contract out work, you ought to obtain some measure of confidence that the work done on your behalf with be to your company's (hopefully) high standards, or even better, you first draw up a statement of work that says what is or isn't OK to do to complete the project.

      Sony, clearly, did none of this.

      --
      -- Experience is a wonderful thing. It enables you to recognize a mistake when you make it again.
    7. Re:Not Sony by bigbigbison · · Score: 0, Troll

      Probably the same reason why people keep asking "Did they know they were breaking the law when they released Plame's name?" and why I get a speeding ticket even if I didn't know I was speeding...

      --
      http://www.popularculturegaming.com -- my blog about the culture of videogame players
    8. Re:Not Sony by MaestroSartori · · Score: 1

      The reason I ask this is that it's not evident that Sony has any responsibility for the content of the software, but is responsible for the distribution of the software. Distributing infringing things could very well be a different 'crime' (not a lawyer, don't know the correct term, don't really care - you get what I mean), and I was wondering if, in this case, it was.

      Thus, if Sony is only guilty of *distributing* an infringing product, and this is indeed a 'crime' (see above), could ignorance be a defence?

    9. Re:Not Sony by Compulawyer · · Score: 1

      The (L)GPL is/are copyright licenses. One of the rights a copyright holder enjoys is the right to control copying. Assuming that Sony, as it pressed each disk, made a copy of the software onto each disk, it is an infringer. The developer may be as well, but the fact that Sony got the code from a 3rd party does not immunize it from copyright violations.

      --

      Laws affecting technology will always be bad until enough techies become lawyers.

    10. Re:Not Sony by lightweave · · Score: 2, Interesting

      That's not really a surprise. Would YOU take the risk of a patent violation and the attached costs for court and everything, if you buy some stuff as a company, but your businespartner 'forgot' to licence the technology (let's say an MP3 player)? I doubt it. Of course if two companies make business with each other, they usually reach an agreement about the responsibillities of each one of them. It's your fault if you are so blue eyed that you don't read what the contract says. I don't know if this is the case here, but I would be very surprised if Sony and First4Internet would have NO contracts signed before Sony uses their software. And if Sony just bought the rights to use the software then it COULD be that they just listed what they wanted to do with it and verified that the software actually does it, and that's it. Why would Sony want to know all the details about the used libraries? They shouldn't know it. Of course you can argue that it still would be in their interest, because like it is here it can destroy their name, but what if the vendor just says, "yes, of course everything is properly licenced." Sony could sue the vendor for the damages, but I don't think there is much more to do on Sony's behalf.

    11. Re:Not Sony by Anonymous Coward · · Score: 0

      People who distribute an infringing work get hung out to dry just as badly as the people who originally ripped the track from the CD, don't they?

    12. Re:Not Sony by WhiteWolf666 · · Score: 4, Informative

      No, its not cut and dry like that.

      In court, damages would be determined based upon the length of time when you were told you were in violation, and when you decided to correct this behavior.

      If you were warned that you were in violation, today, and correct the violation in a week, or stop distributing the code in a month (as soon as reasonably possible) damages would be 'negligible'.

      If you were warned that you were in violation, then ignored it indefinitely, until the matter was brought up in court, that would be considered willfully infringing. There would be damages, but of a limited amount, and an injunction against you for this kind of behavior.

      If you were warned that you were in violation, then you denied it, then you tried to disprove it, then you counter-sued, then you ignored it, attempted to settle, caused settlement negotiations to break down, filed to have the hearing moved to a different jurisdiction, etc etc, the court could be persuaded to lean towards the '$100,000 per CD copyright fine'.

      The court is given a fair amount of leeway in deciding this kind of thing. Behave badly, and unless you have a crack legal team, you'll get slapped. Judges, regardless of whether they are right wing or left wing have a _very_ serious sense of fairness. Fuck with some one in a willful way, and play with them in court to prolong your profiteering, and a judge _will_ come down on you hard.

      Hilariously, this seemed to work too well for Microsoft. They got the judge so damn pissed off that had to reverse his decision. In my opinion, however, you'll never see this happen again. No judge will make the kind of comments that were made in that case.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    13. Re:Not Sony by Kickasso · · Score: 1

      The law says you can't distribute stuff without a proper license. If you do, you're liable, no matter where you've got the stuff and what you know about it. If Sony indeed distributed copyrighted stuff, Sony is liable -- period. Everything else is between Sony and First4Internet and I couldn't care less about it. Note that it was Sony who massively profited off the alleged violation. It would be all too convenient if only some garage shop beared all the responsibility. I don't really believe in justice bit this goes a little bit too far.

    14. Re:Not Sony by lightweave · · Score: 1

      The law says you can't distribute stuff without a proper license. That implies something like a international unified law. What is 'The law' that you are refering to? As to Sony. If Sony buys the rights to distribute this DRM software from another company, than it HAS a valid license. The vendor has to know wether he has the rights or not, and if there are strings attached to it, then he should inform Sony that there are certain conditions to be met when it wants to redistribute it. So the question is more, what is the contractual relationship between Sony and the vendor? On a similar vein I'm developing a community project. A total conversion for Doom 3 http://www.thedarkmod.com./ There are developers sending in code and they put it into CVS which is my own server standing in my home. When I distribute this software to our beta testers you could say in the same vein that I'm responsible for the code, but I'm not. Because I tell teh developers that they have to make sure that they indeed have the copyright to the code they send me, or if they don't have the copyright themself (because they took the code from some other library) they must have at least made sure that they have the rigth to redistribute it. This is a normal procedure. Even more, even if I would look at each and every piece of the code (which I do for new members) I could never recognize that this code may belong to somebody else. I have to take their word for it and can just check it for functional requirements. So if Sony bought the rights from All4Internet then this is all they should need to know, until somebody brings it to their attention. As soon as Sony is made aware of it, of course they would have to stop shipping and clear things up with their vendor, but up until them I think you would have a hard time claiming a copyright violation on Sony's part. Of course this is pure speculation as I don't know the actual agreement between Sony and All4Internet.

    15. Re:Not Sony by Loquis · · Score: 1

      It'll depend on what contract there is between F4I and sony

    16. Re:Not Sony by Alsee · · Score: 4, Insightful

      Our copyright law has literally been written by lawyers employed by the publishing industry (and then out idiot congressmen pass it generally exactly as drafted). Thus copyright law is evil as hell if it is actually enforced.

      In particular copyright infringment is "strict liability". You have an afirmative duty not to infringe copyright, and if you do infringe copyright then you are guilty no matter how accidental or innocent it may have been. Assuming thier rootkit does indeed contain infringing code, Sony is legally liable no matter where they got it and even if they had no idea it was in there.

      However there is a clause in copyright law that if the defendant proves in court that he is an "innocent infringer" then the jude may reduce the monetary damages.

      Also Sony might be able to sue the rootkit authors to recoup any damages they had to pay for copyright infringment. But that would be a completely independant legal issue and an entirely different court case.

      And quite signifigantly, the complaining GPL copyright holder can likely get a court order for all of the infringing CDs to be DESTROYED.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    17. Re:Not Sony by vidarh · · Score: 1

      Ignorance is a defence, but depending on jurisdiction it will likely only reduce the damages. In the US I believe the cap for statutory damages for accidental infringement is $30,000 and that the cap for willful infringement $150,000. I believe those numbers are "per infringement" however the lawyers define that.

    18. Re:Not Sony by asynchronous13 · · Score: 1

      But it's worth mentioning at this point that Sony didn't develop the software in question here - the XCP software was developed by First4Internet.

      Smith & Wesson makes a gun.

      You buy a gun and shoot someone. Who gets charged for murder?

    19. Re:Not Sony by HiThere · · Score: 1

      Sony is a prominent member and strong supporter of the RIAA. If the RIAA does something, and Sony doesn't object loudly and publically, then it is quite fair to blame Sony for the action.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    20. Re:Not Sony by HiThere · · Score: 1

      Since the CDs as sold intentionally break laws against spyware in various jurisdictions, I don't see how Sony could claim to be an "innocent infringer". This was merely another crime that they conspired to commit during the commission of their primary crime. Since they were intentionally breaking the law, I believe that they are automatically guilty of any additional crimes committed by themselves or their co-conspiritors during the action.

      IANAL...and perhaps this doctrine only applies to felonies, or in certain jurisdictions.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    21. Re:Not Sony by Kickasso · · Score: 1

      1. Pretty much every country's law.
      2. If you distribute somebody else's stuff without the copyright holder's permission, you are in violation of the law, ergo, liable. Your relationships with your subcontractors is between you and them.
      3. If you cease the distribution as soon as you know about the violation, you might still be liable for actual damages (e.g. if the copyright holder sells his stuff and his sales suffer because of you). A court probably won't award ridiculous punitive sums like $100,000 per copy, only the money actually lost by the rightholder. In case of LAME actual damages are most likely zero, but it's up to the court to decide.

    22. Re:Not Sony by Anonymous Coward · · Score: 0

      My whole family has blue eyes, you insensitive clod!

    23. Re:Not Sony by R3d+M3rcury · · Score: 1
    24. Re:Not Sony by Anonymous Coward · · Score: 0

      I'm a Sony employee

      How do you sleep at night?

    25. Re:Not Sony by syousef · · Score: 1

      Clearly you're not a lawyer. If you were you wouldn't be posting on a public message board about your employer in regards to something that's legally actionable. Even though you're defending them you're opening yourself up to being fired or sued!

      --
      These posts express my own personal views, not those of my employer
    26. Re:Not Sony by ediron2 · · Score: 1
      A most excellent typo:
      is an "innocent infringer" then the jude (sic) may reduce the monetary damages.
      Hey, Jude.
      Don't make it bad.
      Take our sad crime
      and make it better --
      "Reduce fines"
      the voice says inside your heart.
      Then you can start
      to make it better.
    27. Re:Not Sony by Logi · · Score: 1
      Not being a lawyer, or particularly knowledgable about (L)GPL terms, who could be held liable when a piece of software is developed by one party, but distributed by another? Is ignorance a defence, for instance if Sony said "We didn't know it had unlicensed code!", how would that affect things?

      Also not being a lawyer, I expect that Sony would be responsible for making the source available to its customers - those they distribute the software to.

      First4Internet, on the other hand, would be responsible for making the source available to Sony - the entity they distributed the software to.

      So Sony is certainly infringing, perhaps unknowingly. First4Internet may be infringing if they did not give the source to Sony.

      --
      Logi - I can do anything, but not everything.
  68. Re:Bury LAME by Varun+Soundararajan · · Score: 0

    ren lame $sys$lame

  69. You know what they say... by the+MaD+HuNGaRIaN · · Score: 0, Offtopic

    In Soviet Russia, music listens to YOU!!!!

    In China, only old people buy Sony CDs.

    1. Hide Rootkit in Music CD
    2. Violate LGPL
    3. ???
    4. PROFIT!

    Does anyone know if this new DRM included on the new Natalie Portman CD "Hot Petrified Grits"?

    OK, which ones did I miss?

    1. Re:You know what they say... by Anonymous Coward · · Score: 0

      OK, which ones did I miss?

      How about the biggest /. classic of them all? Do I even need to say it?

      All your base are belong to us.

      n00b.

    2. Re:You know what they say... by Anonymous Coward · · Score: 0

      I believe: does this rootkit run linux?

    3. Re:You know what they say... by Zutroi_Zatatakowsky · · Score: 1

      Imagine building a beowulf cluster of DRM CDs!

      --
      All Hail Discordia. Hail Eris. Fnord.
    4. Re:You know what they say... by GigsVT · · Score: 1

      You forgot "I for one welcome our new Sony DRM overlords"...

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    5. Re:You know what they say... by megabyte405 · · Score: 1

      Something about a beowulf cluster of Music CDs...

      --
      I recognize people by their sigs. Is that a bad thing?
    6. Re:You know what they say... by LocalH · · Score: 1

      That's a /. classic?

      Right, and monkeys fly out of my ass, too.

      --
      FC Closer
    7. Re:You know what they say... by the+MaD+HuNGaRIaN · · Score: 1

      Mod parent up. This is not offtopic!

      Offtopic implies that the contents of the post are --offtopic.

      The parent was clearly on topic, and rather funny.

  70. They included the license!! by Anonymous Coward · · Score: 0

    Take a look at $sys$License.txt .. err... wait

  71. Watch your steps by courtarro · · Score: 1

    Remember that disseminating false information about a company is libel, so for those of you getting ready to create webpages that list the included code, you'd better make sure your evidence and assumptions are accurate. Otherwise, you might be setting yourselves up for a nice fat lawsuit by Sony, reminiscent of Maui-X. Wouldn't that be ironic?

  72. LAME encoder by cdrguru · · Score: 1

    Isn't the LAME encoder an MP3 encoder that still needs to be licensed from Thompson? And, if you are going to get the license from Thompson, why use the LAME encoder instead of the nice licensed one?

    While I can understand a bunch of patent-adverse geeks using an unlicensed encoder, it is really difficult to understand Sony doing this. This actually sounds like it all came from First 4 Internet.

    How incredibly lame are these guys?

    1. Re:LAME encoder by sd4l · · Score: 4, Informative

      Isn't the LAME encoder an MP3 encoder that still needs to be licensed from Thompson?

      In short, No!

      Longer version: According to Dave Arland, a U.S. spokesman for Thomson Multimedia - 'its policy has always been to allow free use of the company's MP3 patents in "freely distributable software"'

      Newsforge Article

      --
      -- Andy Jeffries Scramdisk for Linux (Change the orgy to org to reply)
  73. Re:Sony Rootkit by cyclop · · Score: 0, Offtopic

    When I was 7, I played VIC20 software tapes on my tape deck. It was really fun, it was the first electronic music I heard indeed.

    Later I remember I played .exe files in some kind of wave editor. It was cool, but not as cool as VIC20 tapes. I used it for some kind of electronic-noise project I had when I was in high school, I think.

    --
    -- Patent no.123456: A way to personalize /. comments with a sig attached to the end.
  74. shouldn't matter anyway by cout · · Score: 0

    If this LGPL'd code is so lame, why does anyone care about it in the first place? :)

    1. Re:shouldn't matter anyway by maxwell+demon · · Score: 0, Offtopic

      Hey, that's a lame joke! :-)

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:shouldn't matter anyway by Anonymous Coward · · Score: 0

      FYI: I got your joke and therefore metamodded the asshole mod who gave you an "offtopic" as unfair.

      Once again, the humorless Slashdot mods hits another innocent victim. Hopefully, I've just prevented him from doing it again, at least for a while.

  75. Re:Sony Rootkit by hackstraw · · Score: 1

    It's important to remember that "copy-right infringemnt" != "stealing", and if people on /. can't keep this straight, how can anyone expect Joe Public to keep it straight?

    Software is not a service, its a product.

    Someone owes me $300 for back rent when they lived with me. They did not "steal" anything from me, but he believes he owes me the money and I sure do.

    Obtaining a software product that is commercially available and using it as if you had paid for it is pretty damn close to stealing. I guess staying in a hotel without using any electricity or water and not paying is not stealing, but its still not right.

    Killing someone could be misconstrued into stealing their life. Walking out on a bill at a restaurant is not considered stealing I guess, even though it is in part stealing.

    What difference does it make?

    Stealing a CD from wal-mart is not going to put them under, and neither is copying a CD that your friend bought from wal-mart. So, in order to avoid copy-right infringement, why not just steal the disk from wal-mart instead? Who cares?

    The loosest version of the definition of stealing is to take a product without permission and using it just as if you paid for it.

    Now taking Linux and mucking with it and then selling it w/o the proper attribution or source, is copyright-infringement. But nobody lost a sale here. Taking a copy of MS Office without paying for it and using it for yourself, is much closer to stealing than copyright infringement. Making other copies of it and selling it at a lower cost than the retail value is something entirely different.

    No, copyright infringement is not stealing, but its certainly close enough. Kinda like the difference between identity infringement and identity theft.

  76. It's getting pulled anyhow by confusion · · Score: 4, Informative

    Not that it lessens their tresspass, but Sony is apparently pulling the "infected" CDs:
    http://www.usatoday.com/tech/news/computersecurity /2005-11-14-sony-cds_x.htm

    Jerry
    http://www.cyvin.org/

    1. Re:It's getting pulled anyhow by Slashcrap · · Score: 5, Insightful

      Not that it lessens their tresspass, but Sony is apparently pulling the "infected" CDs:
      http://www.usatoday.com/tech/news/computersecurity /2005-11-14-sony-cds_x.htm [usatoday.com]


      Are they also pulling all of the infected PCs in for free repairs?

      No? Then let's not help these wankers by helping to spread their desperate PR pieces.

    2. Re:It's getting pulled anyhow by igny · · Score: 1

      But we can help the untold numbers of lawyers by spreading the infection.

      --
      In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
    3. Re:It's getting pulled anyhow by FunkyChild · · Score: 1

      Yeah, how dare he report about what is actually happening so people can make up their own minds, rather than repeating groupthink propaganda.

  77. outdated info, it's LGPL nowadays by muzzy · · Score: 5, Informative

    That's outdated. mpglib was relicensed under LGPL some years ago already, check www.mpg123.de

    --
    -- Matti Nikki
    1. Re:outdated info, it's LGPL nowadays by leuk_he · · Score: 1

      In that case you need to find out IF mpglib is acutaly used in the sony distibution, and if it is, what version. maybe some old lame version is used.

  78. Re:Sony Rootkit by Anonymous Coward · · Score: 0

    Enough with the "we're not stealing, we're sharing" argument. Here's the definition of stealing from the New Oxford Dictionary: take (another person's property) without permission or legal right and without intending to return it. The record companies are money-hungry beasts & they do overcharge for their wares, but "sharing music == stealing". The only argument here is that some people feel justified in stealing the property because the cost to obtain it legally is too high. That feeling doesn't obviate the fact that taking songs we didn't obtain from an authorized source is stealing.

    The other argument, that the music industry foists crap on us doesn't hold either. If the products were so undesireable, nobody would be stealing them! So, be honest with yourself and others. If you really think it's crap or overpriced... DON'T BUY OR STEAL IT! That sends the loudest message to a vendor. Stealing just makes them feel that their product is desired, but they are being ripped off. Imagine if nobody stole music anymore, or bought it from the record companies... they would be forced to either sell better stuff, or lower prices to make their products desireable.

  79. Just wait... by TheNetAvenger · · Score: 1

    Just wait...

    After watching them destroy fan bases in their online games like Star Wars Galaxies and Everquest, I can't wait to see what insane ideas they come up next. This DRM thing isn't surprising after watching their 'great ideas' destroy Lucas Arts and SOE's games, let alone the people that were wrapped up in them.

    Should we try to guess what new features Sony is working on FOR THE CONSUMER?

    Maybe when you plug in your new PS3, if you don't accept the EULA, it instantly shocks you to death.

    Or Maybe they have a new online game for the PS3 that is filled with subliminal marketing to sell Sony products that failed in the marketplace.

    And in the process, they will use as much open source code as possible, and then claim they invented it and go on to claim ownership of BSD and Linux. LOL

    Ok, had to be a bit silly today, but Sony lately is acting like a chicken with its head cut off and don't know how to regain whatever it is they have lost or think they might lose (i.e. XBox 360 might have them scared) I know World of Warcraft made them go 'oh crap' and destroy virtually all of their online games that were once what the industry looked to for quality and consistency. So much for consistency, and you can guess the quality part.

  80. Re:Sony needs to protect its image...not so! by glesga_kiss · · Score: 1

    Consumers don't care about record labels, they care about the acts. The fact that any particular artist is on Sony isn't going to bother at least 90% of the buying public. They don't even look, and why should they?

  81. dosn't matter if it's unused by r00t · · Score: 1

    Having opposed the idea that sampling is fair use, Sony doesn't have a leg to stand on. The code was included. It really doesn't matter if the code runs or just sits there. Copyright law is about copying, not running.

  82. How is it worse? by Vo0k · · Score: 1

    How is the Sony DRM worse than other such ones? There's quite a few distributors and quite a few CDs with similar copy-protection mechanism (installs to harddrive vithout user consent, adds self to autostart, hides from process list, breaks CD drivers etc), but none gets as much bad publicity as the SONY one. What "feature" makes the Sony rootkit so evil that it's all over the net while the others remain relatively unheard of?

    --
    Anagram("United States of America") == "Dine out, taste a Mac, fries"
    1. Re:How is it worse? by ceoyoyo · · Score: 1

      Because the others aren't rootkits. They install and hide, but they don't help OTHER programs install and hide. Sony's can be used by ANY program to hide from the system, opening a huge security hole on your machine. Apparently their uninstaller opens an even bigger one, allowing any web page to execute arbitrary code on your machine.

  83. Okay...where are the LAWYERS? Big $$$$ here... by PortHaven · · Score: 1

    Now, let me get this straight. Copyright violations hold up to $150,000 fine for each occurrence, right? This is what "RIAA" and the record labels have been threatening 12 yr olds in court with for the past few years.

    The SONY rootkit was installed on how many computers? Am I correct here...in that the LAME project should potentially be able to sue SONY corp $150,000 for each violation. (Sounds like LAME might become the best funded open source project!)

    Or do our laws only apply to the powerful? the rich? the mega-company? And if that is the case WHY should I give a damn about infringing on copyrights if they don't protect me as well?

    1. Re:Okay...where are the LAWYERS? Big $$$$ here... by cannuck · · Score: 1

      Of course the laws are their to protect the Rich against the middle class as well as the low income class - both in the U.S.A. abd Canada. You have to remember in both countries the constitutions we set up so that originally only the rich could vote. And in both cases the Senate was set up for Rich people sit and decide which laws made by the lower houses we okay for the Rich - and if not were disallowed. If it was for Nader, Chomsky, DVD Jon, ACLU, EFF and a handful of other people and organizations - we all would be royally screwed.

    2. Re:Okay...where are the LAWYERS? Big $$$$ here... by Anonymous Coward · · Score: 0

      Chomsky is an assbag. His opinions reek of intellectual sophistry and his support of the Khmer Rouge has removed every ounce of credibility he ever had.

      Your statements about the rich is partly true, but not entirely. You should read up on federalists vs. anti federalists (basically, rich elites vs. more modest agrarians) and also the various populist movements that gained momentum for a while in the USA.

    3. Re:Okay...where are the LAWYERS? Big $$$$ here... by WhiteWolf666 · · Score: 1

      Nader, Chomsky, ACLU, EFF, DVD Jon, and a handful of other organizations.

      One of the above doesn't belong.

      (Hint, begins with a C, and ends with a Y)

      The rest, even if you don't always agree with them, have contributed significantly to society.

      Even as a libertarian, with strange views, one who was, at one point, suckered by a small sampling of Chomsky's writings, I acknowledge that the rest of that group represent very positive forces.

      Chomsky, as the other poster listed, is indeed a useless assbag.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    4. Re:Okay...where are the LAWYERS? Big $$$$ here... by cannuck · · Score: 0

      Hmm do you mean you don't agree with:

      "Avram Noam Chomsky, Ph.D. (born December 7, 1928) is the Institute Professor Emeritus of linguistics at the Massachusetts Institute of Technology. Chomsky is credited with the creation of the theory of generative grammar, often considered the most significant contribution to the field of theoretical linguistics of the 20th century. He also helped spark the cognitive revolution in psychology through his review of B. F. Skinner's Verbal Behavior, which challenged the behaviorist approach to the study of mind and language dominant in the 1950s. His naturalistic approach to the study of language has also impacted the philosophy of language and mind (see Harman, Fodor). He is also credited with the establishment of the so-called Chomsky hierarchy, a classification of formal languages in terms of their generative power."

      http://en.wikipedia.org/wiki/Noam_Chomsky

      Or is it that you don't agree with his viewpont back up with thousands of pages of data from the USA goverment documents that shows that the United States Of America is likely the biggest terrorist that ever existed!

      Or is his veiwpoint that people are fools not to own the company the work "at"? Rather than being a slave working for some mindless corporate CEO - of whom fortunately a handful are now serving time in prison, For example, see http://today.reuters.co.uk/news/newsArticle.aspx?t ype=businessNews&storyID=2005-11-10T230907Z_01_FLE 083316_RTRUKOC_0_UK-FINANCIAL-REFCO.xml

      Need to add NYS Attorney General Eliot Spitzer to the list for going after the white collar CEO crooks who have bilked millions of investors out of billions of dollars http://www.oag.state.ny.us/

    5. Re:Okay...where are the LAWYERS? Big $$$$ here... by multipartmixed · · Score: 1

      > both in the U.S.A. abd Canada. You have to remember
      > in both countries the constitutions we set up so that
      > originally only the rich could vote.

      Care to back that assertion up with facts?

      You can start here -- http://laws.justice.gc.ca/en/const/

      --

      Do daemons dream of electric sleep()?
    6. Re:Okay...where are the LAWYERS? Big $$$$ here... by Anonymous Coward · · Score: 0

      both in the U.S.A. abd Canada. You have to remember in both countries the constitutions we set up so that originally only the rich could vote. And in both cases the Senate was set up for Rich people sit and decide which laws made by the lower houses we okay for the Rich

      Canada has a constitution? And a senate? and elections?

      My, you guys have come along way. We had the impression it was a subarctic free-for-all up there.

    7. Re:Okay...where are the LAWYERS? Big $$$$ here... by cannuck · · Score: 0

      Facts!?

      The Canadian Constitution originally was prepared by the British for Australia - who read it over and said no thanks. Left the german queen running England in charge of the country!!Does that appear in your "proof".

      It was later peddled to the Scots running Canada - who loved it! The Catholic Church would run Quebec - and the UNELECTED Senate would run Canada. As you know the Kanadian Senate is based on the British Senate whereby only the Rich born of royality may sit (where of course the Rich can also buy a seat in the Senate - e.g. the Kanadian crook Conrad Black bought one!!!) Does that appear in your proof?

      For example, women were not considered a person under that "Canadian" constitution (couldn't vote etc. etc. ) - and the Canadian parliament and the Canadian courts agreed. Women living in Canada would still not be a person if the complainant didn't take the case to the Queen Of England's Privy Council - who overturned the Canadian Supreme Court ruling and the Canadian Parliament stance - that a woman was not a person. Does that appear in your proof?

    8. Re:Okay...where are the LAWYERS? Big $$$$ here... by multipartmixed · · Score: 1

      1. You don't like my "proof?" I offered to prove nothing, and merely referenced the actual document being discussed.

      2. My original query did not discuss the senate. Therefore, your senate argument is a straw man.

      3. My original query did not discuss the issue of sex, only the issue of prosperity. Since sex is not directly linked to prosperity, your argument is irrelevant.

      4. The origin of the constitution is independant of its content.

      Are you debating skills really so poor that you can't even make one point on topic?

      Incidentally, if you actually believe that the Senate runs Canada, you have some serious learnin' to do. You could kill every last senator today, and the country would not change one iota.

      --

      Do daemons dream of electric sleep()?
    9. Re:Okay...where are the LAWYERS? Big $$$$ here... by cannuck · · Score: 0

      When you say "I offered to prove nothing" - but somehow I have to proof my viewpoints - this is classical facist nonsense.

      Noam Chomsky talks about this issue on a regular basis. If someone (me in this case) challenges the established ideas of the ruling class - I have to provide mountains of proof to prove I am right. But anyone who challeges my viewpoint has to provide no such proof that either they are right or that I am wrong. Q.E.D. Thanks for helping me - in making this so clear.

    10. Re:Okay...where are the LAWYERS? Big $$$$ here... by ceoyoyo · · Score: 1

      Come on, sure killing all the senators would change things. There'd be a lot fewer flights to tropical islands, for instance. And what would we watch on the news if not the latest antics of those wacky senators?

    11. Re:Okay...where are the LAWYERS? Big $$$$ here... by multipartmixed · · Score: 1
      I did not challenge your view point, I invited you to back it up with something other than 3rd-grade name calling. I had, apparently mistakenly, assumed that you were offering your viewpoint in an attempt to be educational, rather than inflammatory.

      > Noam Chomsky talks about this issue on a regular basis. If someone (me in
      > this case) challenges the established ideas of the ruling class -
      > I have to provide mountains of proof to prove I am right.

      Political Science, and even Philosophy, require more than hypotheses in order to advance understanding. From your rants, am I to gather that you believe that Chomsky believes that when you're challenging an established viewpoint that no proof whatsoever is required?

      I believe Noam would actually disagree with you on this issue. For example, in the context of his criticism on the corruption of French high society, he has said:

      There are more important things to do, in my opinion, than to inquire into the traits of elite intellectuals engaged in various careerist and other pursuits in their narrow and (to me, at least) pretty unininteresting circles. That's a broad brush, and I stress again that it is unfair to make such comments without proving them: but I've been asked, and have answered the only specific point that I find raised. When asked about my general opinion, I can only give it, or if something more specific is posed, address that.

      (emphasis mine)
      --

      Do daemons dream of electric sleep()?
    12. Re:Okay...where are the LAWYERS? Big $$$$ here... by cannuck · · Score: 0

      So we are in a debate or is it a discussion? So if I understand you correctly, I have to prove:

      "> both in the U.S.A. abd Canada. You have to remember > in both countries the constitutions we set up so that > originally only the rich could vote. Care to back that assertion up with facts?"

      But as Chomsky states about status quo: you don't now have to prove anything - even though you have challenged me. While I have to prove that both constitutions were set up to limit voting. As I said - the classical approach by the elites - the rich - the ruling class - just sit back and complain but don't have to prove anything " because if it ain't status quo - it ain't real".

      Since you mentioned the Senate - Here's one pearl to begin with:

      "Governor General shall from Time to Time... summon qualified persons to the Senate...?. Properly qualified persons had to be at least 30 years old, hold property, be worth at least four thousand dollars and reside within the province for which they were appointed"

      How much was$4000 worth in 1870s?

      Here's an intro to the voting issue:

      "Even among those not deemed "foreign," most adults were also disqualified from voting because they did not have a sufficient stake in the community. This prejudice, though hardly unique to England, was very well established in English common law. A variety of property qualifications were enacted in all the colonies at various times to keep the riff-raff out. As we've already seen, such restrictions could either be relaxed or tightened up, as the needs of public policy, in the eyes of the establishment, required. Property qualifications were used much longer in Canada than in the United States, into the 20th century, almost as long as they were in Britain."

      For example, at Confederation, voting was oral and public in all provinces but New Brunswick. The necessity of a voter standing on a platform and declaring his preference to the world at large allowed plenty of scope for intimidation, at, before, or after the poll. Efforts to bring in the secret ballot were resisted as contrary to the "manly spirit of the British people" and as contrary to the realities of electioneering. HVC quotes an MP who defended hardnosed politics in the Canadian House of Commons in 1874:

      "Elections cannot be carried without money. Under an open system of voting, you can readily ascertain whether the voter has deceived you. Under vote by ballot [the secret ballot], an elector may take your money and vote as he likes without detection. "

      "Indeed the Conservative party of John A. MacDonald had "a profound aversion to universal suffrage, which he considered one of the greatest evils that could befall a country." (HVC, p. 49). MacDonald, who did not lack for other achievements (including Confederation itself), considered "the greatest triumph of my life" the Electoral Franchise Act of 1885, which created a federally-administered franchise that was more restrictive than had existed earlier, when provinces defined the franchise for federal elections."

      "The institutional, legal, and cultural commitment to an open political process was capped by the adoption of the Canadian Charter of Rights and Freedoms in 1982. Included in its provisions was an article guaranteeing the rights of Canadian citizens to vote in federal and provincial elections and to stand for office in them. This marks a defining moment: the older British and Canadian legal and constitutional tradition held that there no fundamental right to vote."

      By 1900, most women property owners across the country could vote in municipal elections, but none had the right to cast ballots in provincial or federal elections or to run for election.

      1867 At the first general election after Confederation, only males over the age of 21 who met certain property qualifications were eligible to vote and run as candidates in a federal election. Women, registered Indians and members of certa

    13. Re:Okay...where are the LAWYERS? Big $$$$ here... by cannuck · · Score: 0

      The silence is deafening. Eh!

  84. tables count by r00t · · Score: 1

    Copyright law doesn't even mention executable code. The tables count.

    Look, some free software developers are going to retire now. At what, $75000 per CD-ROM (thanks to Sony's lobbying efforts), the LAME developers just got rich.

    Even if the case settles for 10% and the lawyers take 90% of that, the LAME developers make off with millions.

    1. Re:tables count by Rogerborg · · Score: 1

      They could argue fair use, but they'd have to argue it. It's not clear on the face of it. They are making commercial use, but only of a small part of the work and with no effect on its market. "quotation of excerpts in a review or criticism for purposes of illustration or comment" might be stretched to cover it, but I agree that until they prove otherwise, it's infringement.

      --
      If you were blocking sigs, you wouldn't have to read this.
    2. Re:tables count by arkanes · · Score: 1
      I almost hope they do and win. It would be incredibly awesome if Sony vs Lame et all become the landmark case defining as fair use the ability to distribute other peoples object code without permission for the purposes of demonstration. All those copyrighted windows themes? No more! Want to sample a top 10 hit for the alert sound in your new email client? Go for it! Distribution of Windows source code for purposes of interoperability?

      Of course, it won't happen. Sony will cease distribution of the rootkit (already has, I think?), Level4 or whoever will write a new one, and Sony will be on the phone with their friends at Fraunhoffer to make this LAME threat go away.

  85. Damn you slashdot community! by Anonymous Coward · · Score: 0

    A perfectly good opportunity for more Sony-bashing, and quotes like "This sort of thing makes copyright infringement morally acceptable and in some states totally legal", and you morons come along with your lawyer-speak and analogies, arguing over mere technicalities. I've got news for you - Joe Desktop doesn't care whether his rootkit binary is linked against LGPL work: he just wants his rootkit to just work. Until the open-source rootkit community gets its act together you can forget any ideas you may have about linux desktop malware adoption.

    So anyway... Sony sure sucks, huh?

  86. The Rage Of Corporation by cannuck · · Score: 1

    The rage exhibited by Sony, Apple and other Corporations and their "Trade" (no trade) associations to monpolize and control what and how we consumers live and act should be a growing concern to everyone.

    This has to be just the tip of the iceberg - "we" likely only learn about 2% of these devious efforts. It's only laughable when "we" learn about how these corporations themselves are breaking all kinds of agreements, all kinds of laws - are in fact the biggest crooks. But the biggest problem is the number of apologists there are lurking amongst "us" - trying to spin away the obvious.

    I was at the house of a hollywood movie mogul this weekend - who is always complaining about copied movie DVDs being sold around town. Sunday evening he showed me the new Bose box he just bought for his black and red iPod. He said someone from his last movie crew sent him the iPod with 500 songs on it. There was no hestitation in playing copied songs on the iPod! Anyone who has hing around crews on movie productions knows where those songs came from.

  87. How many of you have PS3's on preorder now? by C.+Mattix · · Score: 5, Insightful

    So is the Slashdot crowd going to complain and moan about Sony being a servant of the devil, and then happily go to Best Buy and get ther shiny new PS3?

    1. Re:How many of you have PS3's on preorder now? by Dwedit · · Score: 1

      Even Sony's consumer electronics division has been sued by their music division. Sony is one big schizophrenic corporation.

    2. Re:How many of you have PS3's on preorder now? by darkmeridian · · Score: 1

      So is the Slashdot crowd going to complain and moan about Sony being a servant of the devil, and then happily go to Best Buy and get ther shiny new PS3?

      No. I'm going to buy my console from a responsible corporate citizen, uh, >cough, Microsoft. No, I guess I'm going to build a gaming system with the Intel processor because...they're not a mono--... Damn.

      How can I not get modded down now?

      --
      A NYC lawyer blogs. http://www.chuangblog.com/
    3. Re:How many of you have PS3's on preorder now? by aurifex · · Score: 0

      Nope, I'm buying my next console from the other servant of the devil. Mircosoft!

    4. Re:How many of you have PS3's on preorder now? by Cyno · · Score: 2, Interesting

      No PS3 for me. This was the straw that broke the camel's back. Sony and Lucas recently destroyed SWG and I bought a Sony DVD DL/DF DVD burner that won't burn DVD+R media even though it says so on the box and I hate DRM so much it makes me want to torture the Sony Exec who made the decision in my secret prison.

      Sony just lost any possibility of purchases from me. If I find out a product is affiliated with Sony in any way I will look for alternatives. They are now considered worse than Microsoft, Sun, and possibly even SCO. I don't care what you do, I'm going to boycott.

    5. Re:How many of you have PS3's on preorder now? by MikeBabcock · · Score: 1

      Sony's behaviour with the PS2 when it was released should be enough to convince people not to buy a PS3. However, I do own one (waited till it was under $200 CAD) and will probably buy a PS3 when its similarly cheap.

      That said, Sony Music is not Sony Electronics, and the engineers getting paid to develop the PS3 don't deserve to be punished because lawyers (my best guess) wanted this type of "protection" software on the Sony Music CDs.

      In a large corporation like this, its not guaranteed either side talks to the other much, or that these decisions make it to the top. All in all, their quick response (although somewhat half-hearted -- they need to reassure shareholders afterall) has reassured me that the management understands that user concerns are most important.

      Look at all the other copy protection systems out there that aren't been withdrawn by other producers.

      --
      - Michael T. Babcock (Yes, I blog)
    6. Re:How many of you have PS3's on preorder now? by Anonymous Coward · · Score: 0

      If I do, I won't be buying any games.

    7. Re:How many of you have PS3's on preorder now? by Peter+Harris · · Score: 1

      Not yet. I'll wait a while and see if that rumour about pre-installed linux HD kits is true. Then wait a bit longer for someone to port Python and Pygame. Then wait a bit for the price to come down.

      Then, I'll maybe get one. But I might not *buy* a lot of PS3 games.

      --

      -- What do you need?
      -- Gnus. Lots of Gnus.
    8. Re:How many of you have PS3's on preorder now? by Anonymous Coward · · Score: 0
      In a large corporation like this, its not guaranteed either side talks to the other much, or that these decisions make it to the top.

      Nice job rationalizing your decision to fund copyright lobbyists. Sony makes all kinds of proprietary hardware with built-in DRM. Their music division sells all kinds of music that uses the same standards. The hardware and entertainment divisions have been working together for years. Sony has been leading the world in DRM technology. Yet the thought of being without your PS3 troubles you so much that you have to make up excuses to explain why it's okay to buy one.

    9. Re:How many of you have PS3's on preorder now? by kabloom · · Score: 1

      No. I'm going to buy my console from a responsible corporate citizen, uh, >cough, Microsoft. No, I guess I'm going to build a gaming system with the Intel processor because...they're not a mono--... Damn.

      Make an AMD64 gaming system.
      Is it possible that Intel isn't a monopoly anymore because of AMD?

  88. What next? by DrSkwid · · Score: 1

    Price fixing :

    http://www.channelregister.co.uk/2005/11/15/sony_v ariable_pricing/

    Sony in internet 'price-rigging' rumpus
    Ramps up wholesale cost to UK e-tailers

    Sony and other manufacturers have been accused of asking online retailers for 10-15 per cent more for wholesale electronic goods than they charge their traditional counterparts, The Times reports.

    Online retailers have naturally cried foul and will meet today to decide whether to "name and shame" the guilty parties. Sony already faces Office of Fair Trading (OFT) and European Commission examination of its pricing strategy.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:What next? by SirTalon42 · · Score: 1

      The RIAA was already found guilty of price fixing in the US (it happened during the NAPSTER thing, or one of the big Music Industry vs P2P media events)

  89. tell the developers about the money by r00t · · Score: 4, Insightful
    Thanks in part to lobbying efforts by Sony, each CD-ROM carries a penalty of around $75000.

    Suppose the case settles for 10% and the lawyers take 90%. That leaves $750 per CD-ROM for the mpg123 developers. Now think about how many CD-ROMs have been produced.

    Oh, what I'd give to have Sony infringe my open source project! The mpg123 developers are some lucky bastards for sure. I need to learn how to write Windows multimedia software instead of just Linux system software.

    1. Re:tell the developers about the money by RobinH · · Score: 1

      Suppose the case settles for 10% and the lawyers take 90%. That leaves $750 per CD-ROM for the mpg123 developers.

      Assuming your $75,000 number is correct, then 10% of that is $7500 per CD.

      --
      "I have never let my schooling interfere with my education." - Mark Twain
    2. Re:tell the developers about the money by RobinH · · Score: 1

      Oh, you mean if they settle for 10 cents on the dollar, and then the Lawyers get 90%, right? Yes, then it would be $750 - sorry.

      --
      "I have never let my schooling interfere with my education." - Mark Twain
    3. Re:tell the developers about the money by benjamindees · · Score: 1

      Thanks in part to lobbying efforts by Sony, each CD-ROM carries a penalty of around $75000.

      Holy crap. It would be nice to bankrupt a major corporation for abusing their customers. Using their own laws to do it would be icing on the cake. And the proceeds would go towards excellent Free Software.

      Are there two million Linux users out there who'd like to help? Buy a Sony CD with the DRM malware (keep the receipt). Run it. Spend a few minutes wiping your computer clean.

      Somebody can set up a website where people can post their experiences.

      I know there are lots of lawyers on Slashdot. So, how about it? Who wants to be a billionaire?

      --
      "I assumed blithely that there were no elves out there in the darkness"
    4. Re:tell the developers about the money by Anonymous Coward · · Score: 0

      This is absolutely awesome.

      Really, the EFF or someone with a snowball's chance of winning the court case (why isn't the ACLU interested in this kind of thing?) should get involved, because sadly the developers of this likely have no resources to pursue such a great test case.

  90. Re:Sony Rootkit by Anonymous Coward · · Score: 0
    yes, even music can be seen as software

    It could be. You'd be wrong, but it could be.

    True, but I could see some patent attorney in court arguing that it is.

  91. Call This Guy at Sony Music Ent UK by Anonymous Coward · · Score: 0

    Paul Birsch (44) 0207 384 7500

    Leave a message on his ansafone & he "will" get back to you with a complete explanation.

    Honest!

  92. so? by routerguy666 · · Score: 1

    So what, another license violation that no one will do anything about. I've not heard of any legal fallout from any of the numerous license violations Slashdot has reported on. At this point you have to wonder why the license exists at all. If it's never enforced it may as well not.

  93. Re:Sony Rootkit by AndroidCat · · Score: 1

    I thinking more of a firing squad at dawn.

    --
    One line blog. I hear that they're called Twitters now.
  94. Re:Sony Rootkit by Hakubi_Washu · · Score: 1

    The magic words are "take property" and "without intending to return it". When I copy something (which is a technical necessity on electronic data systems, you'd have to actively destroy the original to "just move" it) I cannot "take", let alone "return" the original thing.
    Let me illustrate:
    If I came to your house (without doing any damage), carrying a portable photocopier, and copied a book from your shelf (without even leaving a fingerprint on it), then left again. Did I just steal the book from you? Or am I guilty of trespassing (your house) and copyright infringement (the books copyright owner)?

    I'm not arguing "sharing" music is legal under all circumstances (though there are more cases than the Recording Industry wants everyone to believe), but it is not "stealing". The correct term is "copyright infringement" and in legal debates precise choice of words is essential.

  95. only because of intense scrutiny? by captaineo · · Score: 1

    I'd guess that improper use of (L)GPL code is pretty wide-spread. It's only been discovered in this case because of the intense scrutiny on Sony's DRM system. I bet there are plenty of other cases out there that haven't been picked up because nobody's bothered to scrutinize the executables.

  96. But LAME author doesn't want to take action by oddmake · · Score: 3, Insightful
    1. Re:But LAME author doesn't want to take action by Anonymous Coward · · Score: 0

      Engrish pease.

  97. Re:Wrong. Because the best-kept secret about LGPL. by Dr.+Manhattan · · Score: 2, Informative
    When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not.

    Note the words "may be". Copyright law is funny. Using things that are necessary to interoperate (e.g. simple definitions of constants and function prototypes) is not a problem from a copyright perspective (c.f. "scenes a faire"). If there's only one way to express an idea (e.g. "errno.h", which maps POSIX specified numbers to POSIX specified constant names), it's called "merger" and is not subject to copyright.

    Now, if the header file contains substantial code in its own right, either in the form of code that compiles or just macros, it's possible that a case might be made that the resultant object file might be considered a derived work (though note that the other source code is expressly not).

    Indeed, there might be a case to be made that dynamic linking doesn't create a derived work, and that would make the GPL legally equivalent to the LGPL. But no one's tried to make that case in a court yet.

    --
    PHEM - party like it's 1997-2003!
  98. Yep. Would you settle? by r00t · · Score: 1
    Let's see...

    Give me a seat on the board, 30% of Sony's stock, a hundred million dollars, and a few hundred million dollars for my lawyers.

    Good enough? No? How about one hundred billion dollars?

    I love how Sony lobbied Congress to make the statutory damages so ludicrously high.

    1. Re:Yep. Would you settle? by Anonymous Coward · · Score: 0

      How about one hundred billion dollars

      You need to say this with your pinky finger raised to your mouth

  99. Days old? by Inoshiro · · Score: 1

    Yes, indeed. Some nice folks posted up and down the Sony stories a few days ago about it, and the nice mods rated them up.

    I am probably only one of hundreds who have this on their info page:
    "
    Inoshiro's Recent Submissions
    Title Datestamp
    Sony spyware in breach of LGPL. 15:35 11th November, 2005 Rejected
    "

    By now, there should be some real followup info. Is the EFF going to sue? No one knew what was going on there last week. I hope they've finalized a plan of action this week!

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  100. WRONG by samjam · · Score: 4, Interesting

    "to a website" WRONG WRONG WRONG.

    If Sony don't provide the source they must make THE source available to all third parties for at least 3 years.
    This is an obligation they must fulfil.

    http://www.gnu.org/licenses/gpl-faq.html#Distribut eWithSourceOnInternet
    http://www.gnu.org/licenses/gpl-faq.html#TOCSource AndBinaryOnDifferentSites
    Merely pointing to "a website" or "the website we got it from" is not enough.
    You have to make-sure-it-stays-there. And thats not enough.
    You also have to let people request it by mail charging only a minimal fee.

    You have to track your releases and make sure you keep the source of each release seperately so you can give people the source to the version they had.

    Too many people consider only casually the obligation that the GPL puts on them. GPL is not an easy way out.

    It's easy to receive GPL software because the burden is on the distributor, but you must understand and fulfil the burden when you are the distributor.
    With most commercial software you pay some money before you receive it but you still have to follow the license guidelines.

    Is it too often for me to say again that too many people distibute binary packages to open source software and distribute the source they compile to make the binary package but do not distribute the source to making the binary package; i.e. the .spec file, or the dev-src equivalant.

    Sam

    1. Re:WRONG by DataPath · · Score: 1

      Thank you for the further clarification. Web distribution by itself is insufficient to fulfill the requirements, and the need to make sure the separate sources for each released version are available.

      One thing I'm unsure of - do .spec files need to be distributed? Isn't a .spec file essentially a special shell script that describes the steps in creating the package? Does that mean that if you distribute as a tar.bz you need to make available the command with which you made the tarball?

      I certainly agree that it's in the spirit of open source, but would that be a hard-and-fast requirement of the license?

      --
      Inconceivable!
    2. Re:WRONG by samjam · · Score: 1

      This is a good question.

      I think a .spec file must be included because it is a LOT of shell scripts, some of which form the pre-install and post-install scripts which form part of the package.
      Also because it contains the instructions for building and often for enabling/disabling various options in what is compiled.
      Sometimes it even defines helper functions that help the compile.

      But mostly because the .rpm (or .deb) is a derivative work, and it's source is usually a .spec file (or equivalent) and as a deriviative work its distribution is governed by the GPL or LGPL

      Sam

    3. Re:WRONG by Lemming42 · · Score: 1

      And to think, my company decided creating and maintaining an open-source product was too much work...

    4. Re:WRONG by roystgnr · · Score: 1

      And to think, my company decided creating and maintaining an open-source product was too much work...

      If your company is the sole copyright owner of an open source project, their two legal requirements under open source license are: jack and squat. Licenses are just what allow non-copyright-owners to redistribute - and if the GPL or LGPL are too complex for you, as a copyright owner you are free to choose other licenses.

      If you want your product to be a derived work of other open-source products under the GPL and LGPL, there's a simple solution: distribute source code along with your binaries, and you don't have to offer to repeat that distribution later. Not much work at all, is it?

      So, do you actually have a company that will now be reconsidering their stance on open source, or am I just feeding a troll?

    5. Re:WRONG by eonlabs · · Score: 1

      What if it is a link to a Sony Operated Website, that still fits under the "point to a website" aspect of the grandparent comment. I think the point of the statement was they don't need to distribute source code with it.

      Yes, they do need to make it accessible, and no, none of this is going to affect how much sony stuff I buy.

      I stopped buying their stuff six years ago.

      --
      I wouldn't consider the mad hatter mad. Just reality impaired. He sure can make a mean cup of tea.
    6. Re:WRONG by samjam · · Score: 1

      "point to a website" is NEVER enough to fulfil the GPL or the LGPL unless the "a website" is the same place of the same website where the binary was distributed from.
      In this case the binary was distributed on a CD, so pointing to a website is never enough.

      See: here and here

      Sam

  101. Still applies to the LGPL by samjam · · Score: 1

    For those of you who think I am wrong because I am quoting from the GPL faq and not an LGPL faq, read the LGPL:

    http://www.gnu.org/licenses/lgpl

    clause 4 of the LGPL contains the requirements I described.

    Sam

  102. Two key issues become clearer by Blitzenn · · Score: 3, Insightful

    I am seeing two issues here that are becoming clearer in the Open Source arena. One is that when there is a violation, there is not currently anyone willing to spend the huge dollars needed to litigate the issue. With Comercialware, there has always been someone with fairly deep pockets to pay an attorney to pursue the violators in court. Who is that going to be in the Open Source community? Who is making money on this stuf so that they can pay the expense of litigation when necessary? Is the 'free' trajectory shooting itself in the foot that way?

    Another interesting point I see is that someone, sooner or later is going to challenge the legality of Open Source under the 'free' standard and litigate that it is tantamount to price fixing, i.e. antitrust. How long before someone challenges that the contractual language that forces someone to provide code at no cost is the same as being forced to sell it at an inflated price. The price is still fixed, whether at zero or at some other number.

    These are a couple of major challenges that await open source. I hope someone gets their ducks in a row before these things come to fruition. Open Source has driven the industry in a very good direction. I would hate to see it fall because it can't support itself, financially, when and where it is needed. Justice is NOT free, in fact the costs are enormous to obtain justice. Somehow that has to be worked into the Open SOurce equation in a way that works for us all or the likes of Sony are going to kill it off.

    1. Re:Two key issues become clearer by trollable · · Score: 1

      Sometimes no dollar is needed. Many companies will admit and fix. Read GPL Violations.

    2. Re:Two key issues become clearer by Alsee · · Score: 1

      contractual language that forces someone to provide code at no cost

      False. The GPL (and LGPL) explicitly allow you to charge as much as you like.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    3. Re:Two key issues become clearer by 99BottlesOfBeerInMyF · · Score: 1

      One is that when there is a violation, there is not currently anyone willing to spend the huge dollars needed to litigate the issue.

      Yup no lawyers ready to work on commission and sue the pants off of Sony for a huge fee... what you say there are 400 waiting outside asking to talk to anyone with any of the copyrights involved? Oh, never-mind.

      Another interesting point I see is that someone, sooner or later is going to challenge the legality of Open Source under the 'free' standard and litigate that it is tantamount to price fixing, i.e. antitrust.

      First for antitrust you have to have a company, individual, or group dominating a market. How is that going to happen with Open Source software, considering any other company can come along and sell it as well? Second, no forces anyone to set any price for the software. You can charge as much as you want. Third, the license only applies to companies reselling copyrighted material which is of course a government sanctioned monopoly on that product and perfectly legit.

      Open Source has driven the industry in a very good direction. I would hate to see it fall because it can't support itself, financially, when and where it is needed. Justice is NOT free, in fact the costs are enormous to obtain justice.

      Companies that use and provide support and services for open source tools have been pretty effective litigating on behalf of the copyright holders. e.g. IBM.

  103. GPL gives rights beyond copyright law by chihowa · · Score: 5, Interesting
    Of course you're a troll, but I'll bite anyway.

    The thing that people don't seem to realize is that if the GPL doesn't hold any water (and it may not), then the whole thing just collapses back to plain old copyright law. In that case, they can't copy and sell the code at all without permission from the writer.

    If I write a book and release it on the internet for everybody to download for free, you still can't copy and sell it without my permission. The fact that the code is offered for free doesn't mean that the writer has given up his rights to the work. In fact it is the GPL that gives people the right to copy and sell the work, if they follow the rules outlined in it. Breaking the GPL means you don't have permission to copy and sell the works at all. It is the GPL itself that makes it legal for people to copy and sell GPLed work. Without the GPL it's just plain ol' copyright infringement.

    --
    If you want a vision of the future, imagine a youtube comments section scrolling - forever.
    1. Re:GPL gives rights beyond copyright law by hackstraw · · Score: 1

      If I write a book and release it on the internet for everybody to download for free, you still can't copy and sell it without my permission.

      Oh yeah? I'll take 10 dollars for the text above this line, or best offer.

    2. Re:GPL gives rights beyond copyright law by Limecron · · Score: 1

      >> If I write a book and release it on the internet for everybody to download for free, you still can't copy and sell it without my permission.

      > Oh yeah? I'll take 10 dollars for the text above this line, or best offer.

      Oh yeah?? I'll take $5 for for all the text above THIS line, or trade for a pizza.

    3. Re:GPL gives rights beyond copyright law by Anonymous Coward · · Score: 0

      Why do you hate America?

    4. Re:GPL gives rights beyond copyright law by chihowa · · Score: 1

      Well, I've already got some text, but... it's not this nice! Deal!

      --
      If you want a vision of the future, imagine a youtube comments section scrolling - forever.
  104. I think we know what to do by Trailer+Trash · · Score: 2, Insightful

    The people who own copyrights in lame need to go after Sony for $160K/cd that has been shipped. Perhaps they can set up a call center where Sony can call in to "settle".

    Yes, I'm serious. It's time to turn this shit back around on these bastards.

  105. Re:Sony Rootkit by jedidiah · · Score: 1

    > Obtaining a software product that is commercially available and using it
    > as if you had paid for it is pretty damn close to stealing. I guess staying
    > in a hotel without using any electricity or water and not paying is not
    > stealing, but its still not right.

    When trying to take the "moral high ground", try not to be such a lying sack of sh*t.

    All the examples you try to cite actually include consuming physical resources of the owner for a time. This is something that copyright infringement does not do. Trying to associate one with the other is highly dishonest and is as morally bankrupt as genuine shoplifting. It is even worse since you're also indulging in moral pomposity.

    You are cloning the ware, as if you could hammer out a copy of this years Lamborghini in metal shop. This is in no way comparable to conventiional larceny that has been a common law crime since the beginning of time.

    It's more like counterfeiting, making fake Levi's and whatnot.

    Use of the item doesn't require any sort of deprivation of the owner, not even deprivation that might be inconsequential to them.

    Copyright infringement is nowhere near stealing.

    Also, copyright is not a natural property right. It never has been. It's simply an inducement to encourage creative people to be creative.

    The ultimate point is to have another Illiad or Beowulf, not to create new classes of criminals and robber barons.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  106. Sony is competing against Microsoft by Anonymous Coward · · Score: 0

    And this is the kind of shit you do when you're against a larger company that has absolutely no "morals", either. Business is war. The only thing that Microsoft has done differently is they haven't got caught. Or, when they almost got caught, they bought ("lobbied") all the right senators to make sure justice was done.

    Sony got caught, and it's their own fucking fault just like it was Standard Oil's and AT&T's. Kill, cheat, lie, steal, sabotage, infiltrate, deceive. Just don't get caught.

    I say make an example out of them, to make it a lesson to all the other would-be-caughters out there.

  107. Let EFF know what you think by chihowa · · Score: 4, Interesting

    This seems like a pretty good GPL test case. The irony of copyright infringement being used to develop a copyright protecting program would likely go over will with the court!

    --
    If you want a vision of the future, imagine a youtube comments section scrolling - forever.
  108. Correct me if I'm wrong but... by swelke · · Score: 3, Insightful

    Isn't the minimum way to comply with the GPL's (and I assume also the LGPL's) source code distribution terms to make the source code available upon request? (IE you don't necessarily have to distribute source to those users who don't want it.) So has anybody tried requesting? It's worth a shot. I don't think we've ever had open source DRM crap before.

    --
    Have you ever wondered How to Take Over
  109. This came up on the sysinternals forum IIRC by MemeRot · · Score: 0

    Some people posited that it was an LGPL violation, while others thought that this was included only as binary signatures of the software that the DRM process was supposed to monitor. You know, how anti-spyware programs have definition files that let it recognize spyware, this DRM software presumably has definition files of ripping software to look for. That seems more likely to me.

  110. come on, close the irony strange loop! by Thud457 · · Score: 1

    Somebody needs to modify the worm that takes advantage of the rootkit so that it will : A) distribute Sony's copyrighted music and b) distribute the DRM code with the LGPL violation in it.

    --

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

  111. It's a rootkit! by Spy+der+Mann · · Score: 1

    Since it's become a fundamental part of the operating system (try to delete it if you don't believe me :P), then there's no obligation, right? ^^;

  112. Re:Sony Rootkit by SageMusings · · Score: 1

    You say software is not a service but a product.

    Isn't Miscrosoft considering offering future versions of MS Office as a subscription-based service via web clients? I could be wrong but I thought I read that somewhere. If they are, would this not make the software a service and not a product the customer actually owns?

    I think the the distinction is murky. Can you make the distinction clearer to me?

    --
    -- Posted from my parent's basement
  113. Ya know... by Anonymous Coward · · Score: 0

    I wonder if the programmers who had to make this in the first place might have done that on purpose. Can't do anything to stop the big company but slip in a few pieces of viral code....

  114. Nonsense by chihowa · · Score: 1, Interesting

    This is the code should still be controlled religion. If you want to copy somebody else's work and use it for your own ends, should they not have any say over the process? If you want to avoid the "viral LGPL", stop copying other people's code. It's silly to think that you should be able to do whatever you like with somebody else's work without respecting their restrictions. Have you heard the saying: "Don't look a gift horse in the mouth"? You're getting the code for free (you didn't have to pay for it or write it yourself), so play by the rules of the giver or don't accept the gift. This really isn't that difficult.

    --
    If you want a vision of the future, imagine a youtube comments section scrolling - forever.
    1. Re:Nonsense by mmeister · · Score: 1

      Actually, I'm not getting code for FREE because I avoid GPL code at all costs. As soon as I see the GPL license, I turn the other way. I had heard that LGPL was a less viral, but apparently not much less. I'm sure I'm not the only one that avoids this code. Any business that doesn't rely solely on GPL code is in danger of infection and would avoid this.

      The point is that the code is not FREE by any means as there are serious restrictions applied to it. And that's fine. But I hear the same group of folks proclaiming GPL as the salvation of coding attacking businesses that apply restrictions on their code by "not setting it free." There is definitely a bit of hypocrisy in that.

      As I said, you either buy into the religion or you don't. But clearly, this "free" code is not free. The strings attached are no better than those of proprietary license code, just different.

      A BSD license, on the other hand, allows me to benefit from other code AND contribute back without sacrificing my entire business model. I don't have to buy into the religion.

      Regardless, I'm not going to give Sony a free pass. They broke some serious trust (and likely laws) regarding their relationship with the customer.

    2. Re:Nonsense by ceoyoyo · · Score: 1

      The LGPL doesn't seem unreasonable to me. It requires that you inform the user which LGPL code your program uses (giving credit -- yes, you absolutely should be required to do that), and also requires that you make it possible for the user to swap a different version of that free library into your program. If statically linked that means you have to make your object files (not source) available. Seems perfectly reasonable and I don't see how it could possibly affect your business model, unless your business model is taking credit for other people's work.

    3. Re:Nonsense by Miros · · Score: 1

      Finally, someone who properly understands the LGPL! Nobody else seems to realize in this thread that the point of providing the object files is so you can swap in differnt versions of the free software. Object files are specified specifically because when teh LGPL was written their intension was to allow for proprietary programs to link free libraries. If sony did their job right, all they need to do is provide a single text file to solve the problem, and have an obscure section of their website with the object files. They dont have to give anything up at all, they probably wont even go to court or anything stupid like that. I'd call what they did the equivalent of J-walking on a dirt road.

    4. Re:Nonsense by ceoyoyo · · Score: 1

      I REALLY like the idea that LAME (and maybe some other groups, who knows what they use) might be able to take them to the cleaners though. Under the exact rules that the RIAA (of which Sony is a member) has pushed for, someone did a back of the envelope calculation that they'd be liable for something in the trillions. Hopefully this will go to court and the ridiculousness of the current state of copyright law will be driven home, to Sony themselves.

      Not bad, being fined a few trillion for jaywalking on a dirt road. It's actually even dumber... like caught and sentenced to death for jaywalking when there's a pedestrian crossing right next to you -- you just have to take the time to press the button and make the lights flash.

    5. Re:Nonsense by Miros · · Score: 1

      Yeah, but somehow that doesnt seem like justice. Here we all complain about many of the injustices done by these large organizations through copyright law, it feels wrong to use our love of freedom to hurt them using their own traditional weapons. How can we continue to take the higher moral ground if we do go after them like that? Are we not just saying they are right do to the same to us?

    6. Re:Nonsense by ceoyoyo · · Score: 1

      Okay, so after the five trillion dollar judgement against Sony LAME can take enough to reimburse all the people sued by the RIAA, a reasonable amount of damages (per CD) for copyright infringement (not $150,000 but not zero either) and then take the moral high ground and excuse Sony from the rest of their debt. Hopefully one of their number being at the absolute mercy of a bunch of communist open sourcers will be enough to convince the RIAA that they've erred.

  115. Yeah but... by Spy+der+Mann · · Score: 3, Funny

    let's not forget that the rootkit would have to distribute the source code with it!

    Hmmm I wonder...

    $sys$rootkit.cpp
    $sys$rootkit.h
    $sys$drm.cpp
    $sys$drm.h
    $sys$lgpl.txt
    ...hmmmm Nah.

  116. Yet all they had to do by joelito_pr · · Score: 2, Funny

    &sys&/rootkit/sources

  117. LAME is for research/education only by v3rgEz · · Score: 1, Informative

    Since LAME violates several mp3 patents, besides the obvious LGPL violations (if they are distributing LaME, which is disputed) Sony is violating several more people's rights. LAME is ONLY available for non-commercial, educational use. This would be a glaring violation (hence the reason that few distros ship (especially free ones) with mp3 support (legally)).

  118. Re:part != whole by Bastian · · Score: 1

    Of course distributing all of Windows would be copyright infringement. So would distributing entire copies of books - or entire copies of LAME for that matter.

    Fair use covers taking small snippets of something for various uses. Aruging that you can't duplicate an entire work says nothing about whether a particular use of a small snippet is fair use.

  119. More "Sony are evil" ammunition by Zog+The+Undeniable · · Score: 1
    --
    When I am king, you will be first against the wall.
  120. Re:Thank god! - What's Next by BrokenHalo · · Score: 1
    ...many cute furry animals die when subjected to Barbara Streisand's music.

    I guess it is one of the more ironic (and we could just as easily contract that to "moronic") features of present business proctice that insists that the corporations that sell the crappiest muzack are the same ones that are most vigorous in suing their potential customers.

    There should be a lesson there, I suppose, but some folks are slow learners.

  121. Here's what next by Anonymous+Brave+Guy · · Score: 1

    Microsoft(!) declared Sony's XCP software to be malware, and said they'd remove it in the forthcoming December update of the Malicious Software Removal Tool, as it violated "objective criteria". Check out the MS Anti-Malware team's blog for more fun.

    <obligatory> And I submitted this yesterday, but apparently the editors didn't think it was worth mentioning, instead going for a dubious LGPL angle that was debunked in at least two previous discussions. <sigh/> </obligatory>

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Here's what next by AnotherLostAtom · · Score: 1

      All I can say is, this is a call to action!! For this holiday season do not buy any gifts that have the brand Sony ANYWHERE on them. If we as consumers give Sony a swift kick to the groin by making their sales this Christmas in North America a record low. Then they will think twice before they continue trying to ($#*^%# us in the name of progress.

  122. Re:Sony Rootkit by hackstraw · · Score: 1

    Use of the item doesn't require any sort of deprivation of the owner, not even deprivation that might be inconsequential to them.

    Copyright infringement is nowhere near stealing.


    But it is very damn close. Would everybody copyright infringing on Doom III instead of buying it or everybody taking a copy off of the shelf do anything different to ID Software? Would it deprive them of jobs and money? Yes it would.

    In one of my examples, taking off without paying at a restaurant. That is not semantically called "stealing", but it is more technically "stealing" than copyright infringement of software.

    I'm sorry, but who the fuck cares about "copyright infringement"? That means nothing to most people, and it sounds like its making someone uncomfortable at the most.

    Identity infringement sounds stupid. Identity theft, although it might not be theft in any sense of the law, just sounds better in writing and speaking.

    My point was and is that sometimes theft is not called theft when it is (leaving a restaurant) or simply isn't as in identity theft.

    I'm a hedonist, my moral philosophy is to do whatever the fuck you want so long as you get away with it. I'm against stealing of software or infringing on the intellectual property owners rights or whatever you want to call it because you simply cannot get away with it. If that were universally or beyond some threshold to make software a profitable business, everybody looses.

    So, is it stealing if nobody notices the item missing? I don't know how much money I have in my wallet right now. Around $50 plus or minus. Someone could take a 5, 10, or 20 and I would have no idea. Regardless, if I catch you in my wallet, you better be bigger and/or better armed than me. If I'm feeling particular feisty, that might not matter. If at all possible, you will not get away with it.

    Value is just that. If people stop valuing software and "steal" it, then it will only hurt people like me in the end because I'm in the business. I value software. I use free and commercial software. I feel as though I am doing myself a disservice by "use better word than steal"ing software.

    I once heard that someone once said that if someone rips off something inexpensive like a pack of gum or something, then their integrity is worth less than the cost of a pack of gum. There is some saying that goes like "It not that you lied to me that bothers me, its the fact that I can no longer trust you that bothers me".

    Does any of this make sense? Is your mom's basement still OK for you?

    No, in a legal sense it is not "stealing". But objectively it is.

  123. This is news to everyone? by Korexz · · Score: 2

    I cannot tell you how many times I have found commercial software using source from open source projects. Most of the time the product has just had the front end altered, but the application is the exact same project from sourceforge.net. I have alerted many many open source developers and every time they thank me for the notification, but they are also helpless to persue the offending party.

  124. Sue for Damages by JBHarris · · Score: 1

    IANAL...but most of these Copyright lawsuits are based around compensation for damages. If software is LGPL, then the amount of monentary damages would be close to zero. The software is free, as long as you use it for x purpose and include y source code.
    If they broke the LGPL, there may be another set of rules to follow.

    Who knows, maybe Sony got permission from the original authors of these binaries for this purpose (HA!).

    Either way, I'm scared that these guys are operating above the law, and would bend a court to thier every whim. Exciting times.

    1. Re:Sue for Damages by vidarh · · Score: 1

      Copyright infringement in the US allows for statutory damages to be awarded - that is there is a presumption of damage even if the copyright owner can't prove any actual loss (monetary or otherwise) as a result of the copying.

    2. Re:Sue for Damages by Steve+B · · Score: 1
      Copyright infringement in the US allows for statutory damages to be awarded - that is there is a presumption of damage even if the copyright owner can't prove any actual loss (monetary or otherwise) as a result of the copying.

      Sony's epitaph: Live by purchased legislation; die by purchased legislation....

      --
      /. If the government wants us to respect the law, it should set a better example.
  125. Re:Sony Rootkit by dwandy · · Score: 1
    wow. get a grip... there's so many irrelevant points in your post, I can't begin to discuss each one separately.

    Let's be clear here: I'm not making legal definitions; law makers did, and they decided that the act of copying software w/o permission was called "infringement" as opposed to theft. They did this since they are not the same thing. They also decided that "murder" was not simply "life theft", as it is not simply a form of theft.
    The points I made were neither to condone copy-right infringement or the breaking of any law, nor did I say anything about whether the *AA's are evil, or right, or wrong, nor offer any other such opinion. Let's stretch your analogy until all law breaks down to X-theft as the only remaining legal term.
    so, we already have murder==Life theft, let's do some more:
    Kidnapping==Freedom Theft.
    Speeding==FastLane Theft
    Assault causing bodily harm==Epidermis Theft
    c'mon! together we can re-write the laws so everything is theft..!

    Legal definitions are important, and I think we all know that a rose-by-any-other-name is in fact no longer a rose. 'Digital Rights Management' is a corp-speak way of saying 'Digital Rights Restrictions', but try selling that as a feature on your MP3 player. There's a reason that the words 'piracy' and 'theft' are used by those that own copyrights. These words are far stronger, and conjure mental images of wrong-doing that the correct legal words never can.

    It's Orwellian to allow others to redefine how and what you think by using newspeak.

    ps:
    [quote]Walking out on a bill at a restaurant is not considered stealing I guess, even though it is in part stealing.[/quote] uhm... I'm pretty sure you'd in fact get charged for theft if you walked out on a restaurant bill... but hey, IANAL... :)

    --
    If you think imaginary property and real property are the same, when does your house become public domain?
  126. Clinton + Pot = Modern Youth Logic! by Anonymous Coward · · Score: 0

    > Did I just steal the book from you? Or am I guilty of trespassing (your house) and copyright infringement (the books copyright owner)?

    wtf? This is why most of us sit back and laugh at you adolescents reaching for justifications for your p2p crimes. By the way, thanks for the definition of stealing from the Modern Clintonian Dictionary...

    What you conveniently fail to point out is the fact that you STOLE from the author of that book, not to mention committing a few other crimes (against MY property) along the way. If you don't understand that you just stole $25 from that author by copying his book instead of purchasing it, you fail to see many things I suppose. Oh, the irony. I guess in that sense, by your very own logic you illustrate the "marijuanna use leads to hard drug use" theory. A crook is a crook. Give 'em an inch and they'll take a mile...

    1. Re:Clinton + Pot = Modern Youth Logic! by Hakubi_Washu · · Score: 1

      *Yawn* Back that up by posting non-AC and I might be interested... Until then I'll consider it flamebait, if you don't mind.

    2. Re:Clinton + Pot = Modern Youth Logic! by Anonymous Coward · · Score: 0

      Yawn? Does all that piracy on the p2p high seas tire you out or something cap'n?

      Way to duck a clever observation made by the AC. By the way, a "flamebait" response typically implies the inability of an adolescent to comprehend (or deal with the) truth. I still don't see a good response to your casual oversight of the obvious when describing "theft". Oops. Maybe even I am asking to much from you afterall. Nothing left in your wicked clever arsenal? You, sir, as they say in the military, have "dry fire"...

    3. Re:Clinton + Pot = Modern Youth Logic! by Hakubi_Washu · · Score: 1

      Is that all you* got? "Casual oversight" and, previously, "drug abuse"? Bad troll, put your heart in it, you can do better! :-)

      Or should I assume you're actually trying to argue? You should learn about logic and argumentation first (Hint: Your previous posts were, uh, dumb**, ok?). Then risk you pretty karma (as if that was worth a thing). It's not as if anyone is going to set your house on fire if you're an ass and everybody knows your slash-ID, you know?

      *I'm assuming I'm talking to the same person, or at least some with a close enough mindset...
      ** Would you've actually understood "fallacious"?

    4. Re:Clinton + Pot = Modern Youth Logic! by Anonymous Coward · · Score: 0

      hmm...

      We're still waiting patiently for you to answer why it's not stealing again. Duck, dodge, and avoid. Brilliant! Even Clinton would be proud. Hakubi Washu? Latin for "Reefer Rationale"? Please continue flying "Mexican Airlines", pull another excuse outta your ass, and post back by all means! I can see the puffs of smoke collecting over your head now - you know, where that lightbulb should be...

    5. Re:Clinton + Pot = Modern Youth Logic! by Anonymous Coward · · Score: 0

      > Back that up by posting non-AC and I might be interested... Until then I'll consider it flamebait, if you don't mind.

      Posting AC equals purity of thought disconnected from the /. Borg hive. You must be new here, dumbass. Now, try and disconnect yourself from the reefer hive and take another stab at re-defining "stealing". If you can that is...

    6. Re:Clinton + Pot = Modern Youth Logic! by Hakubi_Washu · · Score: 1

      Better, congrats.

    7. Re:Clinton + Pot = Modern Youth Logic! by Anonymous Coward · · Score: 0
      > If you don't understand that you just stole $25 from that author by copying his book instead of purchasing it, you fail to see many things I suppose.


      Mod AC +5 Insightful!


      Kenneth Star, "Mr. Hakubi_Washu, what is your definition of stealing?"
      Hakubi_Washu, "[scratches chin]...hmm, what exactly do you mean by is?"

      ...and so goes the justification by many for stealing as this AC points out. It need only fit their narrow scope of the law, not society's at large...
    8. Re:Clinton + Pot = Modern Youth Logic! by Anonymous Coward · · Score: 0

      The AC Tribe has spoken!

    9. Re:Clinton + Pot = Modern Youth Logic! by Anonymous Coward · · Score: 0

      Donald Trump to Hakubi_Washu, "you're fired!"

  127. Where's the justice? by Anonymous Coward · · Score: 0

    The thing that pisses me right the fuck off is, where's the justice for this? Sony has committed heinous acts against the computing world and everyone is just like, "Damn, they suck a lot. Oh well, let's argue about the GPL license they may or may not have violated." Aren't we missing the point of the whole thing?

    Sony date-raped computers and NO ONE SEEMS TO CARE TO DO ANYTHING ABOUT IT!

    How can this be prevented in the future? Is there ANYTHING we can do against companies that shit all over their customers? Just imaging what would happen to a company like Pepsi or Coca-Cola if they stared serving their delicious colas laced with Hepatitus B.

  128. The polymorphic humor FAQ by Thud457 · · Score: 1
    The Sony DRM rootkit FAQ

    The Sony DRM rootkit will re-write your hard drive. Not only that, but it will scramble any disks that are even close to your computer. It will recalibrate your refrigerator's coolness setting so all your ice cream goes melty. It will demagnetize the strips on all your credit cards, screw up the tracking on your television and use subspace field harmonics to scratch any CD's you try to play.

    It will give your ex-girlfriend your new phone number. It will mix Kool-aid into your fishtank. It will drink all your beer and leave its socks out on the coffee table when there's company coming over. It will put a dead kitten in the back pocket of your good suit pants and hide your car keys when you are late for work.

    The Sony DRM rootkit will make you fall in love with a penguin. It will give you nightmares about circus midgets. It will pour sugar in your gas tank and shave off both your eyebrows while dating your girlfriend behind your back and billing the dinner and hotel room to your Discover card.

    It will seduce your grandmother. It does not matter if she is dead, such is the power of The Sony DRM rootkit, it reaches out beyond the grave to sully those things we hold most dear.

    It moves your car randomly around parking lots so you can't find it. It will kick your dog. It will leave libidinous messages on your boss's voice mail in your voice! It is insidious and subtle. It is dangerous and terrifying to behold. It is also a rather interesting shade of mauve.

    The Sony DRM rootkit will give you Dutch Elm disease. It will leave the toilet seat up. It will make a batch of Methanphedime in your bathtub and then leave bacon cooking on the stove while it goes out to chase gradeschoolers with your new snowblower.

    --

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

  129. Re:Wrong. Because the best-kept secret about LGPL. by moro_666 · · Score: 1

    actually ... in some cases you dont need to use the header file of the library :D

    man dlopen
    man dlsym

    there you go ... there are a lot of libraries out there that can be used this way :)

    ---
    as for sony, what did you do with the poor dude that invented the idea to install silently drm software into user computers and thereby fgging the user computers up? concrete boots & the ocean ?

    luckily my ubuntu box won't care if you have zillion .exe's on that cdrom, i will still get my music ...

    --

    I'd tell you the chances of this story being a dupe, but you wouldn't like it.
  130. Re:Sony Rootkit by Anonymous Coward · · Score: 0

    But it is very damn close. Would everybody copyright infringing on Doom III instead of buying it or everybody taking a copy off of the shelf do anything different to ID Software? Would it deprive them of jobs and money? Yes it would.

    My wife wanted a car. We bought a used Toyota because of it's reliability and she liked the style. I guess in doing so we've deprived Detroit of jobs and money. We deprived the financiers of extra gravy because the vehicle wasn't new. We deprived the State of more licencing tax for the same reason. We're depriving the insurers since our premiums are lower.

  131. Eye for eye by mr_typo · · Score: 1

    If I remember correctly they were asking for $20.000 in copyright violations from single unemployed parent with income around $30.000 a year. According to the latest report (according to annual report filed at nasdaq) sales and operating revenues for sony was $66,912mil for last year, so they sould be made to pay two thirds of that, which would equal to

    $44,608 mil.

    Only fair, no?

  132. Re:part != whole by terrymr · · Score: 1

    Fair use generally covers your own taking of part of a copyrighted work, you don't often here of a fair use defense in cases of commercial mass distribution.

  133. Sony, Stand-by with your checkbook by Anonymous Coward · · Score: 0

    That would be how many thousands of dollars per infringment (cd)? If the open source copyright holders pull their horns in on this, they are nuts.

  134. Sony's finally pulling CDs/offering replacements by iambarry · · Score: 1
  135. This gives new meaning.... by KGB+is+My+Name · · Score: 1

    This gives new meaning to the words:

    "Its a sony."

  136. No. Perfectly aligned with Sony's Policy by javamagnoman · · Score: 1

    Sorry,

    But this is perfectly aligned with Sony's other actions. Look at the Blu-ray spec, or the myriad of crap they've put on music CD's in the past. All that has happened here is that they've been encouraged by lack of penalties to extend their intrusion into user's rights. They got caught is all.

  137. You've "heard"... by pantherace · · Score: 1

    as in you haven't examined it for yourself?

    1. Re:You've "heard"... by Sarisar · · Score: 1

      erm... sorry did I load the wrong page? I thought this was Slashdot, where we always quote wiki articles that anyone can write and claim knowledge of stuff that God himself (or Q or alternate deity / deities) doesn't know

    2. Re:You've "heard"... by mmeister · · Score: 1

      "heard" as in previous discussions about using LGPL as an alternative to GPL for closed-sourced programs. This is ONLY TRUE if the LGPL library is dynamically linked in, something that is apparently just implied.

      Since I have not needed a LGPL-based library thus far, I didn't need to read the license. However, upon this latest article, I read the license.

  138. Sony quote by Tankerbay · · Score: 1

    Heh, they should just issue a release, "Look, we can only fire the guy responsible for this once."

  139. Re:Sony Rootkit by stinerman · · Score: 1

    I suppose the analog would be reading an audio file as a set of x86 instructions. I do have the feeling that your computer would crash upon "executing" such a file.

  140. Sony's probably indemnified by First4Internet by Sagarian · · Score: 1

    It's very common in commerical software licensing deals -- the licensor indemnifies the licensee for any breach of patent, copyright, etc... meaning it's highly likely that First4Internet has probably indemnified Sony in this case, and would be the eventual victims of any GPL-wielding lynch mob!

    1. Re:Sony's probably indemnified by First4Internet by sgent · · Score: 2, Insightful

      Yea, but if First4Internet goes bankrupt, they are off the hook, and Sony is stuck with it. Indemnification is only as good as the company behind it.

    2. Re:Sony's probably indemnified by First4Internet by ceejayoz · · Score: 1

      To my knowledge, bankruptcy law doesn't work that way.

    3. Re:Sony's probably indemnified by First4Internet by Anonymous Coward · · Score: 0

      If Sony distributed copyrighted code without permission, *Sony* is liable.

      Sony may have gotten it from someone else fraudulently selling rights that they didn't own. That doesn't let Sony off the hook, it just means that Sony can sue the third party to recover damages. Sony has to pay the copyright holders whether or not Sony can collect from the third party or its insurance company.

      If I don't pay my mortgage, my bank will foreclose. It doesn't matter to the bank that the reason that I couldn't pay was because my paycheck bounced.

  141. Uninstaller open a Huge security hole... by formant · · Score: 1

    Serious design flaw in Sony's web based uninstaller : http://www.freedom-to-tinker.com/?p=927

  142. Question by ZachPruckowski · · Score: 1

    Which means someone can legally release a script that changes Sony's DRM to allow LAME? Or, even change those lines of code to send the whole program entirely?

  143. It gets better. (price fixing the hardware, too!) by mr.+methane · · Score: 1

    Looks like sony is also Engaging in price-fixing to keep customers from buying their equipment on-line.

  144. Never attribute to malice... by Aero+Leviathan · · Score: 1

    ...that which can be adequately explained by stupidity.

    --
    ~ Aero
  145. Note from Wired: Boycott Sony by Anonymous Coward · · Score: 0

    Probably not a bad idea - poke 'em in the eye: http://wired-vig.wired.com/news/digiwood/0,1412,69 559,00.html?tw=wn_story_top5/


    MCI The URL - send it to your friends and family...

  146. GPL/LGPL corner cases. by einhverfr · · Score: 1

    IANAL, but I think that the issue of corner cases are really iffy on these cases and could well vary from juristiction to juristiction. The key issue is not what is permitted but what the limits are to the concept of derivative works. Does linking imply derivation? Does it? Why or why not?

    I would tend to think that mere linking in absense of other substantive derivative aspects might well be insufficient at least in juristictions requiring something like the Gates test (abstraction, filtration, comparison). In these cases, I would think that the header files would be required to be filtered out as unprotectable for the reason that a) they are required for interoperability and b) they are not in themselves substantively expressive outside those areas required for interoperability. In other words, if I write a module for compilers to support, I don't know, raw compiling of Python code, and I choose to make this available for the GCC among other compilers, the fact that it can be linked against the GCC might not be sufficient to require that it be covered by the GPL and the fact that a small amount of literal copying (as *required* for interoperability) takes place would not change that, I would think.

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:GPL/LGPL corner cases. by Anonymous Coward · · Score: 0

      Yeah YANAL, and you're not even versed in the LGPL either.

    2. Re:GPL/LGPL corner cases. by einhverfr · · Score: 1

      Yeah YANAL, and you're not even versed in the LGPL either.

      My point was actually that the LGPL linking exception might not always be meaningful. Yes, you have a linking exception. But until it is tested in court, we don't know excactly how we determine whether software is derivative of other software in a given juristiction.

      The FSF's position is simply the position they are willing to fight over and think they have a generally good chance of prevailing in.

      --

      LedgerSMB: Open source Accounting/ERP
  147. Re:Can Sony be sued ? by Anonymous Coward · · Score: 0

    I'll never understand why you can mod someone "Redundant" if they're only the first-fifth poster and said something original, or when you can mod someone "Overrated" when said message was never even rated in the first place. Way to go with the logical moderations, Slashdot!

  148. Sony is not legally responsible by Anonymous Coward · · Score: 0

    Not to pee on the parade here, but didn't sony license this software from another manufacturer? Almost all corporate software license agreements have "hold harmless" clauses and copyright indemnification, so you are probably talking about the scum sucking author's being guilty here, not the scum sucking record company.

    1. Re:Sony is not legally responsible by VENONA · · Score: 1

      That's OK, there are enough scum sucking lawyers out there to cover both bases. :)

      --
      What you do with a computer does not constitute the whole of computing.
  149. Sick SCO on em!!! by rastin · · Score: 1

    Who needs a reason?

  150. Plastic.person touched my junk liberally by Anonymous Coward · · Score: 0
    Plastic.person touched my junk liberally. he strapped me in to his trollmobile and he couldnt keep his offensive hands off of me. he was performing many red flag touches. i couldnt believe what the fuck was going on. i told Plastic.person that Hemos would not approve of a basement-dwelling lackawit touching an underage kid for free.

    Can you believe it? Plastic.person did all this. He picked me off the street, strapped my arms and legs down in the trollmobile's passenger seat, and just wouldn't stop fondling my cock'n'balls.

    They definately were red flag touches. the goddamn referee he had in the back seat kept on raising up this red flag every time he touched my junk but did Plastic.person care? NO WAY! He just kept on doing it. I couldn't believe what the fuck was going on, indeed. I pleaded with Mr. person but to no avail. I told Zonk would not approve of such a smelly man touching an underage kid like me (at the time I was 13) without at least compensating me for the trauma and the use of my body as his own personal plaything.

    This got to him, worrying about his image. He continued to fondle me, all the while ignoring the referee's red flags. Then he drove the trollmobile to my house and *ejected the seat I was in*! It was amazing. But surprisingly, after I woke up the next morning, my bank account had $1.50 in it! Can you believe it?

  151. Re: so, how about mp3 patents? by Anonymous Coward · · Score: 0

    Ummm, does anyone know how many programmers (also know as copyright holders) have code in LAME?

    You really think any of them are going to step forward? Frauenhofer owns patents on just about Everything That Is MP3. So pursuing a case against Sony for violating LAME's copyright would only expose yourself to a patent-infringement lawsuit from Frauenhofer.

  152. Too many license lawyers by Arandir · · Score: 2, Interesting

    I used to always think a license meant what it says, not what the hordes of Slashdot children wishes it did. Please people, GO READ THE FRIGGING LGPL!

    The LGPL does not require you to distribute the source code, it only requires you to give the source code to a user who asks for it. Including the source code with the software is only one of several means to accomplish this. Has any legal user of the software asked Sony for the source code? Anyone? I thought not...

    It's not that I think Sony is innocent. Hardly! But that's no excuse for hundreds of Slashdot posters to be whining about licnese terms that don't even exist.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
    1. Re:Too many license lawyers by Kickasso · · Score: 2, Interesting

      //GO READ THE FRIGGING LGPL!//

      Good advice! Now follow it.

      You will notice that there are several requirements in LGPL, and some of them include words like "reverse engineering" and "prominent notice" and "a copy of this License".

    2. Re:Too many license lawyers by Arandir · · Score: 1

      You will notice that there are several requirements in LGPL, and some of them include words like "reverse engineering" and "prominent notice" and "a copy of this License".

      Yet nowhere does it say that you must attach the complete source code. That's what the whine is about. NOT that there wasn't a notice, NOT that there wasn't a copy of the license, but instead a lack of SOURCE CODE. Notice the difference?

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  153. because by samjam · · Score: 1

    Because if you don;'t distribute the source with the binary then YOU have to make the SAME source available to all 3rd parties for 3 years.

    And how are you going to do that when the project author changes the version available on sourceforge so that the version you used isn't available anymore?

    The only admin-low way to abide by the GPL is to distribute the source WITH the binary. Anything else puts a severe admin burden on the redistributor, esp. if you start shipping multiple versions of the library over time.

    Sam

  154. Re:Thank god! - What's Next by shotfeel · · Score: 1

    And the soon to be told story -SCO alleges they've been unable to identify the infrining code IBM improperly put into Linux because they have poor taste in music, and as a result all pertinent files have been hidden by Sony's rootkit. As a result, SCO has been forced to ask for a 6 month extension for discovery and has requested that IBM and Sony turn over all the files SCO doesn't know about.

  155. Re:Sony Rootkit by hackstraw · · Score: 1

    wow. get a grip...

    Grip now firmly applied. Good suggestion.

    there's so many irrelevant points in your post, I can't begin to discuss each one separately.

    Now, that my grip is applied, I'm confused why any sane person would discuss the irrelevant points.

    Giraffes have long necks and never infringe on copyrights. Discuss!

    It's Orwellian to allow others to redefine how and what you think by using newspeak.

    ps:
    [quote]Walking out on a bill at a restaurant is not considered stealing I guess, even though it is in part stealing.[/quote] uhm... I'm pretty sure you'd in fact get charged for theft if you walked out on a restaurant bill... but hey, IANAL... :)


    My whole irrelevant point was that I'm trying to say that, yes, in the literal strict meaning of the word theft and copyright infringement are not theft. Neither is identity theft. Walking out of a restaurant is not talked about as theft, but its closer to theft than copyright infringement, but the term "theft" and "stealing" are more commonly used for copyright infringement on commercial software, movies and music than it is used when leaving a restaurant without paying.

    I did not make any of this up.

    I will say that also according to the lawsuits going around, I would personally rather be charged with theft vs copyright infringement. If I were to run out of a store with a CD not much would happen if caught. If I were to "share" the same CD on the internet, it looks a bit nastier.

    I have stolen things before, I have infringed on copyright before. Does that make me cooler now?

    I guess its a losing battle, but I would like to end the infringement vs theft thing. Its stupid. No, they are not literally or legally the same, but pretty damn close.

    I don't "infringe upon copyrighted software" because I'm selfish. I want there to be a software industry with quality supported software, and not just hacked together stuff by CS students before they go to collect unemployment.

    Its just easier to say I don't steal software. But apparently it really makes people feel better to infringe on copyrights and face those lawsuits and/or criminal cases than those of theft which is not theft, but you end up in the same place.

    No. Everybody with any basic concept of theft and copyright infringement know they are not literally the same, but in written and informal speaking, they are.

    Even people that blatantly "infringe on copyrights" consider themselves thieves. Ever hear of http://thepiratebay.org/ Pirates are known as people that steal stuff off of boats. Not infringe on their copyrights.

    The words will be inseparable as long as I can tell. Its no big deal.

  156. DBS by Futurepower(R) · · Score: 1

    DBS: Don't buy Sony.

    Many, or most, people who call themselves marketers believe that marketing must be adversarial to be effective.

    I wonder whose sink-the-company idea it was to include rootkit software.

  157. SKYNET is growing exponentially! by Thud457 · · Score: 2, Interesting
    Welcome to planet Sony!

    This researcher has probed the caching on DNS servers to see how many requests are made for the www addressed used by the rootkit. He's gone a generated some nice geospatial plots of the results. The West is burning!

    --

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

  158. Sony's Missed Opportunity by FaulterEgo · · Score: 2, Interesting

    Is anybody else just awestruck by the delicious irony of Sony violating a licensing/ distribution agreement in an effort to prevent folks from violating theirs? This has the potential to venture into Greek tragedy territory before it's all over, folks.

    You know you've hit rock bottom when even the Bush Administration has enough politcal clout to condemn your actions. Sony'd be better off if they were using this stuff to actively spy on users. That way, they could spin it as some kind of Patriot Act double-secret probationary counter-terrorism measure to prevent Al Queda pirating their content and funneling the black market proceeds to imbedded cells worldwide. That they didn't dub their root kit "the Freedom patch" was truly an opportunity missed.

  159. Even More info : by Arend · · Score: 1
    Check this out: Is Sony in violation of the LGPL? - Part II :

    "I'm sure you've been waiting for updates that prove what we're talking about. Here it comes. I want to talk about the file ECDPlayerControl.ocx which the fanstastic muzzy found yesterday while I had nothing better to do than to listen to my pillow. It uses LAME code (and code from at least one other LGPL library)."

    1. Re:Even More info : by Tolomir · · Score: 1

      Don't you think, this LAME code is just a red hering?

      I mean, what if they found out about the program "strings" and used all relevant strings in LAME to identify unauthorized ripping?

  160. In Soviet Russia by SilverspurG · · Score: 1

    You rootkit Sony!

    The world is so mixed up these days.

    --
    fast as fast can be. you'll never catch me.
  161. Andrew Bird by DanTheLewis · · Score: 1

    http://www.andrewbird.net/

    He rules! [On Righteous Babe.]

    --

    Q: What did the comedian say to the crowd?
    A: If I knew, this joke would be funny.
  162. count me in by usernotfound · · Score: 2, Funny

    So i think i'm headed out to the store to buy a couple cd's that contain this XPC rootkit crap, and hope I can get some sweet class action cash. Not that i'd ever be caught dead listening to the music, but maybe i could give them to a friend, and have them sue me for ruining their computer and valuable ($100,000,000) work. Then i can sue Sony because their cd cost me $100,000,000......fu#ck, someone just give me money.

    --
    You call it excessive, I call it ambitious.
  163. Ummm...wow. By my math... by Kythe · · Score: 1

    ...since Sony says over 2 million disks containing the rootkit have been sold, that puts them under the gun for roughly U.S. $150 billion in damages :)

    Perhaps the copyright owners could offer to settle: have Sony repay all of the people who have been extorted for money because of filesharing (double for damages), set up a legal defense for other file-sharers and promise to stop all such activities in the future. That would only run them about $100-$200 million, so it would be quite a deal.

    (posted also at p2pnet)

    --

    Kythe
  164. Nikki suspected that some weeks ago by hurtta · · Score: 1

    Nikki suspected that LAME reference on some weeks ago http://hack.fi/~muzzy/sony-drm/.

    That was mentioned at least 2.11.2005
    http://www.digitoday.fi/tekijanoikeus/?p=102#comme nts.

    1. Re:Nikki suspected that some weeks ago by hurtta · · Score: 1
  165. WRONG WRONG WRONG by Krach42 · · Score: 2, Informative

    You have to make-sure-it-stays-there. And thats not enough.
    You also have to let people request it by mail charging only a minimal fee.


    These are DISJUNCTIVE positions. You only need to do one, not all of them.

    Saying "we have used unmodified versions of the LGPL library XY, and that you can obtain them from the website of the project which was at __url__ as of __date__"

    *IS* sufficient. The automatic requirement to redistribute the LGPLed code is not included anywhere in the LGPL code. Were it, it would say that you must redistribute the source code for the LGPL project if you release binaries.

    This is not the case. If you haven't made any changes to the LGPL code, then there is no reason to redistribute the source code, and there is no REQUIREMENT either.

    --

    I am unamerican, and proud of it!
    1. Re:WRONG WRONG WRONG by samjam · · Score: 1
      "Saying "we have used unmodified versions of the LGPL library XY, and that you can obtain them from the website of the project which was at __url__ as of __date__"
      is NOT enough.

      If you don't provide source at the same point of distribution you MUST provide the source by MAIL for 3 years.
      Only providing by a website at a point which was not the point you distributed the binary from is NEVER enough and also foolhardy if it is not your website because then you cannot make sure the source (or the SAME source) stays there.

      The requirement to distribute the source to the LGPL code is included in the LGPL license, see:
      LGPL Clause 4 whic states:

      4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.

      If distribution of 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 satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.


      There is a clear requirement to re-distribute the source even if you didn't change the library.

      If you think I am wrong, please cite your authority or source.

      Sam
    2. Re:WRONG WRONG WRONG by Krach42 · · Score: 1
      Ok, point one, you said: "You also have to let people request it by mail charging only a minimal fee." Which means that it's not an "either... or", situation, but an "and" situation. (also == and) In your response you make it clear that it's "either... or". You don't *have* to provide for the ability for someone to mail in and receive a copy, as long as you gave them the source code in the beginning.

      You have a point mostly, but there's a bit of a loophole: Section 6d)

      d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.


      Feasibly, if you said "newer versions of the library can be found at __url__, and so can the source code." then you could claim that you're off the hook, and if people really push you, just hand out the source code on email request basis.
      --

      I am unamerican, and proud of it!
    3. Re:WRONG WRONG WRONG by samjam · · Score: 1

      First point; yeeeees. But not quite. You misunderstand the (6d) loophole.

      But to be clear (6d) only applies to certain methods of distribution. Sony distributed on a CD which is more than "offering access". 6d also specifies the "same place" and "equivalent access". For instance 6d could apply to offering ftp access to the binary and specifies that you fulfil the requirements if you put the source alongside it.

      Pointing to a URL at a different place does not fulfil this, and is fraught with danger to the person with the liability to ensure source distribution; if they don't have control over where the source is being distribtued from how can they ensure that they fulfil the license terms?

      Further it is not enough to offer access to "newer versions" of the library, you must offer access to the _same_ source. Which is why for .rpm packages it is important to distribute the .spec file, but by distributing the .src.rpm it is EASIER to be SURE you have fulfilled the license agreement, sometimes the .spec is not enough and it takes thoughtful examination of the .spec file to be sure.

      So there are
      *) requirements
      *) sensible codes of practice

      The most sensible code of practice to fulfil the requirements is to distribute the source side-by-side with the binary.
      The only safe "pointer to the source" you can provide is a mailing address and an offer for 3 years. Any other "pointer to the source" must point to the same place the binary was distributed from.

      Sam

    4. Re:WRONG WRONG WRONG by Krach42 · · Score: 1

      The most sensible code of practice to fulfil the requirements is to distribute the source side-by-side with the binary.

      I'd say the most sensible code of practice would be to dynamically link against the library, and have the user install the linked to library seperately. You could do this as simply as directing them to the library on the internet. I've found that this holds true in most situations for F/OSS software. Kind of a policy of "you can get the library easier than it would be for me to comply with the terms of the license for redistribution."

      I still just don't see the necessity of the person using the library to be forced to redistribute the unmodified version of the source code if they use it. It makes sense for modified source code of the LGPL library, but in cases where that source code is unmodified, and it's dynamically linked, so that the only thing they have to do to update that library is copy over a newer DLL / make install with a newer version of the library...

      It just seems overly encumbering if they're just using the code.

      --

      I am unamerican, and proud of it!
  166. Re:Thank god! - What's Next by Anonymous Coward · · Score: 0

    You're a cute furry animal?

  167. Sony Music != Sony Computer Entertainment (?) by DanTheLewis · · Score: 1

    We don't know how deep the taint goes. If we find out the Sony music CDs don't infect the PS3 with the rootkit, we'll know there was some collusion between the different branches of the company. Then we can return our PS3s for repair, further increasing Sony's expenses and hurting their launch.

    So everybody wins. Right?

    Oh. Not Sony. Right. But that's good.

    --

    Q: What did the comedian say to the crowd?
    A: If I knew, this joke would be funny.
  168. Speaking of Lawsuits... by serutan · · Score: 1

    Could individuals who bought these CDs sue Sony for not including the LGPL source? Imagine a beowulf cluster of such lawsuits.

  169. Re: so, how about mp3 patents? by Anonymous+Bullard · · Score: 1
    You really think any of them are going to step forward? Frauenhofer owns patents on just about Everything That Is MP3. So pursuing a case against Sony for violating LAME's copyright would only expose yourself to a patent-infringement lawsuit from Frauenhofer.

    Sshhh! Frauenhofer actually needs to slip a check or two under LAME's door before the two can walk into the sunset happily ever after. Half of something (esp. from $ONY) is a whole lot more than all of nothing, and lawyers aren't exactly free either.

    And since you brought up the MP3 "ownership", wouldn't it be poetic justice if $ONY's rootkit was repurposed to benevolently convert all the world's MP3's into OGG's before setting up a BT tracker... :-)

    "But your honor, it was designed to screw our customers, not us!"

    --

    Should invading one's peaceful neighbours be opposed, or rewarded with trade deals?

  170. WOW! Now that's hypocrisy! by ivanmarsh · · Score: 1

    We stole your code to prevent people from stealing our product.

    Who says the music industry's not just a bunch of scumbag thieves?

  171. Re: so, how about mp3 patents? by 91degrees · · Score: 1

    But patent damages aren't quite so insane as copyright damages. Willful infringement is something like 3 times the amount they would have paid. If they win against Sony (which they probably wouldn't, but we can dream), they'll have enough to cover the cost of a licence for everyone who might have downloaded a copy of LAME. And that's only if the judge disagrees that source code is merely a description rather than an implementation.

  172. No, no he couldn't. by tkrotchko · · Score: 1

    "An employee could accidentally (or purposefully) make the switch w/o realizing the effects"

    It doesn't work that way.

    Unless the employee has been given authority to make the change in license then it has no effect.

    For example, if an employee of Sony took Red Hat, and inclued in mp3's of a Sony CD with the distribution, that doesn't force Sony Music to GPL the music. That would simply be unauthorized reproduction of the song and there would never be a valid permission for distribution.

    Same is true of software.

    As to your other point, there is no imperitive to use any GPL or LGPL software in anything! Write it yourself or pay the author of the program money to release it to you in a special license. That's always a possibility. You can simultaneously release your copyrighted work in GPL, LGPL, BSD, etc to different people.

    --
    You were mistaken. Which is odd, since memory shouldn't be a problem for you
  173. Abusiveness is common at Sony, apparently. by Futurepower(R) · · Score: 1

    So many people are ready to assume that Sony didn't realize the destructiveness of the Sony rootkit.

    However, that ignores that the rootkit is merely one more example of the abusive Sony culture, in my opinion.

    For example, I bought a Sony laptop that came with a $150 Sony rebate. It took 18 months to get Sony to pay.

    All three Sony laptops that we bought failed seriously. I can think of other examples, but I need to continue working now.

  174. There has to be an exception for detection by Anonymous Coward · · Score: 0

    If copyright prevents programs from including enough of other programs to detect them, how can antivirus and antispyware exist? If sony is indeed not running the code but is only using it to detect the presence of LAME, we have to give them the same fair use that we would expect any antivirus or antispyware would have. It would be far worse if copyright was allowed to extend that far, it is likely nobody would be allowed to detect something like Sony's rootkit.

  175. Ani Difranco - best (c) statement -ever-. by Olinator · · Score: 1
    She Gets It:
    "Unauthorized reproduction or distribution, while sometimes necessary, is never as good as the real thing."

    That's the copyright statement (or near enough -- I'm not in the presence of my CD collection at the moment) on every Ani disc I own. She's awesome. Particularly recommend the album she did with Utah Phillips, especially for anyone who's woken up to the fact that corporate media are constantly rewriting history, even of things that happened within living memory.

    (She's also one hell of a guitarist.)

    Ole
    1. Re:Ani Difranco - best (c) statement -ever-. by devonbowen · · Score: 1

      I once dropped by her office in Buffalo to pick up an older CD I couldn't find in the stores and was shown around a little and introduced to people. I talked to her lawyer and he said they are rather aggressive about going after people that infringe. Of course, I don't know that means and he didn't want to discuss it further. But it was interesting to me given what is written on her CDs about unauthorized reproduction.

      Devon

  176. Woody Guthrie - best (c) statement -ever-. by Anonymous Coward · · Score: 0
    Pete Seeger, June 1967:
    When Woody Guthrie was singing hillbilly songs on a little Los Angeles radio station in the late 1930s, he used to mail out a small mimeographed songbook to listeners who wanted the words to his songs, On the bottom of one page appeared the following:
    "This song is Copyrighted in U.S., under Seal of Copyright # 154085, for a period of 28 years, and anybody caught singin it without our permission, will be mighty good friends of ourn, cause we don't give a dern. Publish it. Write it. Sing it. Swing to it. Yodel it. We wrote it, that's all we wanted to do."
  177. This could be BAD news for Open Source Software... by ardle · · Score: 1

    Or, at least, it's a pretty tricky situation.

    There's a possibility of word spreading, somehow, that Sony used an Open Source program to compromise its customers' computers. How many people will understand what Lame is for?

    In order to counteract the bad press, it may become necessary to pursue a case against Sony. Pity the software product for which the case must be pursued is one whose legal status is dubious when distributed in binary form.

    Thankfully the makers of Lame have been very careful with their legal position (here's their links page) but it's a pity this is the software that could take the (L)GPL to court.

    Don't get me wrong - Lame's a great MP3 encoder. Or not ;-)

  178. IIRC by Anonymous Coward · · Score: 0

    bladeenc dll is illegal in the US.
    Wonder who in Sony obtained it. Maybe time to arrest someone with an anti terrorism law.

  179. And what better time... by benjamindees · · Score: 1

    To remind everyone what that asswipe Orrin Hatch said about copyright infringement:

    "There's no excuse for anyone violating copyright laws,"

    --
    "I assumed blithely that there were no elves out there in the darkness"
  180. that's a different lawsuit by r00t · · Score: 1

    Only the open source developers (of mpg123, etc.) stand to win absurdly high per-CD statuatory damages.

    People buying CDs get to do the class-action thing instead. There, only the lawyers get rich. Everyone else gets something lame (arrrgh...), like a $2 coupon good toward the purchase of a Sony CD-ROM. Unclaimed awards probably go to "purchase" Sony's least wanted CD-ROMs for inner-city schools. The end result is still useful as a deterrant for Sony and others, but nothing to get all excited about.

    If you want a piece of the big money, try to find a mpg123 developer who doesn't want to bother with the lawsuit. If you find such a person, ask him to assign copyright to you. You'll need it in writing, and somebody needs to register the copyright. Be sure to ask a lawyer if offering payment is good or bad; it may come up in the courtroom. Perhaps something non-monetary would be wise, like what the FSF does.

  181. Summary: violate copyrights to protect copyrights by kabloom · · Score: 1

    That summary didn't come out right. It should probably say something like "Sony violates LGPL copyrights to protect their own"

    Sony has reached a new level of evil.

  182. Who can step up? by kabloom · · Score: 1

    Does the FSF provide legal backing for projects under their license? Would the EFF help? Also, didn't Red Hat put aside a pool of money during the SCO flap to help OSS developers with litigation? Can that be used for this?

  183. MOD PARENT UP by kabloom · · Score: 1

    I don't have any mod points, but someone please mod the parent up so he reaches +4.

  184. Sue for every instance (i.e. CD!) by SRA8 · · Score: 1

    Similar to their lawsuits, Sony needs to be sued 10,000 USD for every instance of this violation. Lets define instance as every CD with the unlicensed [stolen] code!

  185. Sony violates DMCA, commits IP theft? by lpq · · Score: 2, Interesting

    So this boils down to Sony ignoring the access control (LGPL) in place on the LAME library and commits theft of someone else's Intelletual Property in order to construct their DRM code?

    If this isn't the most blatent case of a pot calling a kettle black. They should be sued under the DMCA for each CD they have sold in the US market.

    It would seem this is no longer a civil matter but a criminal matter. Will this be taken as a case by the FBI?

    -l

  186. I Don't Think Sony Can Argue "Fair Use" by Steve+B · · Score: 1
    It seems that Sony has not actually included any executable code from LAME, only some data, which is likely used as a signature, to determine if you have LAME installed and are using it to rip MP3s. This is likely fair use, not wholesale copyright violation, as far as LAME and the LGPL are concerned.

    According to the US Copyright Office, the key parameters to be evaluated are:

    1. the purpose and character of the use, including whether such use is of commercial nature or is for nonprofit educational purposes;
    2. the nature of the copyrighted work;
    3. amount and substantiality of the portion used in relation to the copyrighted work as a whole; and
    4. the effect of the use upon the potential market for or value of the copyrighted work.

    Going down the list:

    1. Sony is clearly using the copied LAME code for a commercial purpose.

    2. Obviously, both LAME and the rootkit are software. It's unclear how this affects the evaluation.

    3. Remains to be seen, but there seems to be enough evidence for discovery to begin.

    4. Almost any plausible answer to the original question "What does the rootkit do when it detects LAME?" constitutes a direct assault upon "the potential market for or value of" LAME. On this point, Sony is big-red-capital-Superman-S screwed.

    --
    /. If the government wants us to respect the law, it should set a better example.
    1. Re:I Don't Think Sony Can Argue "Fair Use" by Anonymous Coward · · Score: 0

      Sony is clearly using the copied LAME code for a commercial purpose.

      But they aren't making a direct profit from the sale of each copy. They are only profitting from reduced piracy.This weakes rule 1 considerably.

      Obviously, both LAME and the rootkit are software. It's unclear how this affects the evaluation.

      It doesn't. What does affect things is how the LAME code is used. Is it just data being used comparison or is it being executed?

      Almost any plausible answer to the original question "What does the rootkit do when it detects LAME?" constitutes a direct assault upon "the potential market for or value of" LAME. On this point, Sony is big-red-capital-Superman-S screwed.

      This is not what this factor means. What it means is will this copyright infringement, in and of itself, result in lost sales of LAME. Will people choose the Sony Rootkit as an alternative to LAME. This is the argument Sony woul duse in court, and the judge will quite likely agree with this interpretation.

  187. Discovery by Anonymous Coward · · Score: 0

    Oh you fools, their computers should be seized NOW as part of discovery. The evidence is being removed.

    Steve Jackson Games.

  188. Hmmmm by samjam · · Score: 1

    Hmmm, I wonder why Sony didn't do that.

    Sam

    1. Re:Hmmmm by Krach42 · · Score: 1

      Because as with any company, they want people to just insert a CD and have it just installl; so they go with redistribution.

      In a lot of ways, I've found providing source code much easier than providing executables for distribution. If I go for executables, then I have to package it up and get it working for blah blah system.

      If I distribute the source code, then I just have to give out the source code, and how I compile it. If it doesn't work on someone else's system, then they can either adjust the source code, or they can just not use it.

      Life's a hell of a lot easier when you're not driving by comptetitive ambitions.

      --

      I am unamerican, and proud of it!