Slashdot Mirror


Microsoft And The GPL/LGPL

AnimeFreak writes "In this CNET news article, it talks about how Microsoft's new license that will allow competing companies to read-over software code for their products does not allow software covered under the GPL/LGPL licensing agreement (such as Linux, SAMBA, and Mozilla)."

23 of 573 comments (clear)

  1. Just like... by LinuxInDallas · · Score: 2, Interesting

    this?

    http://slashdot.org/article.pl?sid=02/04/05/1456 25 2&mode=thread

    I thought we had hashed this one out already ;)

  2. Re:So? by thomas.galvin · · Score: 5, Interesting

    It's their code, they can licence it however they damn well please.
    That's what "freedom" is all about. You get to choose how your code can be used. MS has decided, now it's up to us to honor that decision.
    Otherwise, you have no right to expect anyone to respect licences like the GPL.


    Normally, you would be right, but Microsoft has been found guilty of illegaly abusing a monopoly. This trial is in the penalty phase, not the "did they do it or not" phase; Microsoft is being punished.

    The very heart of "punishment" means that Microsoft is going to have to do things that they do not want to. The fact that this is an anti-trust trial means that they are going to have to do things that hurt themselves and help their competition. GPL software represents some of their strongest competition, so a "punishment" that does not help GPL developers is not a punishment at all. Remember, they have been abusing their competitors and their customers.

    In the past, when Microsoft did whatever they damn well pleased, they broke the law. They cannot continue to do whatever they damn well please to correct this.

  3. Re:So competing means???? by josh+crawley · · Score: 3, Interesting

    Wow, a first post that probably wasnt aiming for it. Well, that aside....

    Anyways, how can MS compete with GPL? I see they're trying to look _good_ by allowing some source to leak out to freeBSD. Still, with their standards, how can they prevent/make sure that somebody doesn't share the standards with somebody in the samba group? Still, isn't decryption/decoding of standards compliance ommitted in the DMCA? I thought the Sony v Colecio setteled that (I knew it's sony versus some other vid game company, as the other company won).

    Oh well, MS is outliving their usefulness with their ever constricting contracts and costs. I've even shown Linux to friends who never have had a computer. They prefer KDE over windows. They realise setting up is a chore, but learning a bit is cheaper than resorting to a Evercrack(-like) software. Just fork over 200 bucks and we'll give you a patch^H^H^H^H^Hupgrade!

    I still use Windows(2k), But I'm trying to find the best way to port over to linux, as the major tool I need is an avi video editor(VirtualDUB in linux would be wonderul, but I have very little skills in that area). I game a bit, But I OWN the metal box Quake3. I also have UT, RtCW, and other fun linux games. No probs there.... :-) ePSXe works great in linux too....

  4. The picture I get by Tremul · · Score: 3, Interesting

    The picture I get of Microsoft when I read articles like this, is that of a spoiled child who wants all of the toys, wants them his way and wants them right away. However eventually this child grows up and learns that he has no friends. In Microsofts case, the child has grown up and learned to beat the other children with his toys.

    --

    "Can't sleep. Clowns will eat me"
  5. Other Counties by LinuxOnHal · · Score: 2, Interesting

    Ok, I know that there are lots of samba developers here in the U.S., but is this as enforcable in other counties equally as well?

    It would greatly hinder development, but what if the protocol work was done overseas? Software is regulated in different ways in different locations.

    Just a thought

    --
    Trying is the First Step to Failing --Homer Simpson
  6. This is about *Software Patents* by Ogerman · · Score: 5, Interesting

    From the text of the license:
    3.2 Patent License. Subject to Sections 3.3 - 3.7, Microsoft
    hereby grants Company a worldwide, royalty-free, non-exclusive, personal,
    transferable, non-sublicensable, license under its Necessary Claims to (1)
    make, use, import, and (2) offer to sell, sell and distribute, directly or
    indirectly, to End Users, Company Implementations that fully comply with the
    Technical Reference. The above license is limited to implementing the CIFS
    communication protocol itself, and does not include any express or implied
    licenses or other rights to any underlying technology (operating system
    technology, local file system technology, etc.) that may be used to make a
    complete file server or other CIFS compatible device.


    Reciprocal Patent License. To the extent Company owns,
    controls or can sublicense without payment of a fee to an unaffiliated third
    party, any patents that are required for Microsoft or its licensees to
    implement CIFS as set forth in the Technical Reference and distribute such
    implementations, Microsoft and its licensees are hereby granted a license to
    such patents solely for the purpose of implementing CIFS as set forth in the
    Technical Reference and distributing such implementations.


    If I understand this correctly, Microsoft is claiming patent rights (5,265,261
    and 5,437,013) on technology related to implementing CIFS. Basically they're saying "everybody can use our patents royalty-free as long as it's not part of (L)GPL'ed software." Essentially this is a patent license, not a software or documentation license. The "technical reference" is just along for the ride--also free under the same terms. I predicted this about 2 years ago--that Microsoft would turn to software patents after realizing that GPL software was undefeatable by any other means. This is their first attempt.

    It seems there are 3 options:
    1.) Develop CIFS software outside the US, ignore the patent for use within the US.
    2.) Develop a CIFS module for Samba under the BSD license (license compatibility?)
    3.) Develop CIFS software at will and ignore M$ altogether.

    All three cases probably require some degree of civil disobedience for US citizens--in the form of not honoring software patents. I say go for it. This could become the first time M$ ever legally fought individuals, and believe me--it could raise such a stink in public opinion that it destroys them completely.

    1. Re:This is about *Software Patents* by Anonymous Coward · · Score: 1, Interesting

      All three cases probably require some degree of civil disobedience for US citizens--in the form of not honoring software patents. I say go for it.

      Wow, you're going to stand up for your right and get me arrested? What a martyr.

      To my point, Microsoft spends more on innovation than you can fathom. Nothing compared to OSS. Why? What kinda jackass CEO is going to put money into research just to have jackass2 CEO take the code and use it in their distro? Microsoft has a business model that supports research and development because what they research is theirs to make money from. The next time you put billions of development bucks, do you want something out of it? If you got nothing back from your 4B dollar investment, you wouldn't invest it again. If Microsoft doesn't make money of their research, they aren't going to research anymore.

      and believe me--it could raise such a stink in public opinion that it destroys them completely.

      There will be no outcry against people that actually know how to pay developers instead of kicking them in the teeth like other companies.

      Marx knew that there's one thing above all others that motivates people, and that's their pocket books. Every day more "free" distros release subscription services and things like open office. If consumers have to pay (especially for a service, instead of a one time deal) they aren't going to care about OSS. And if OSS companies can't make money off OSS, now NO one cares. The OSS comapnies should learn how to make money and stop screwing over employees if anyone is ever going to support them. One way to do that is through patents, which MUST be enforced if anyone is going to make money for innovation.

  7. Allow BSD, but not GPL, how? by jmv · · Score: 5, Interesting

    Can anybody explain to me how Microsoft can allow BSD software to use their license while forbiding GPL? Since BSD software can be re-licensed under any other license (the property that MS likes), why couldn't it be re-licensed under the GPL. In other words, what would prevent me from writing a very small BSD program that just used the MS doc but doesn't really do anything useful, and then re-license it under the GPL.

    Or probably better, all the MS interoperation code could be put in a BSD library (since there'd be nothing innovative in that part, MS won't even bother) and then link all kinds of GPL programs to that library. Does that make sense?

    1. Re:Allow BSD, but not GPL, how? by Osty · · Score: 2, Interesting

      Can anybody explain to me how Microsoft can allow BSD software to use their license while forbiding GPL? Since BSD software can be re-licensed under any other license (the property that MS likes), why couldn't it be re-licensed under the GPL. In other words, what would prevent me from writing a very small BSD program that just used the MS doc but doesn't really do anything useful, and then re-license it under the GPL.

      It's not so much that BSD-licensed code can be relicensed (GPL code can be relicensed as well, by the author or with the author's consent). It's more about how the GPL forces the code to be released.

      There are really two ways to look at the GPL. The first is from the perspective of a programmer writing GPLed software. He licenses under the GPL because he wants to make sure his code is always available (alternatively, he worships RMS, or doesn't really know what the GPL is but has heard it used as a buzzword, or is trying to keep companies from profiting from his work, whatever). This is fine. Anybody who wants to use that code has to abide by the GPL or get a special license from the author.


      The second way is what this is all about. Somebody writing a GPL application links to a non-GPL library. Now, it's not very clear on what the licensing situation should be at that point. The obvious solution is "don't do that", but there are plenty of ignorant people out there so we can't rely on that answer. Now, the way Microsoft (and most other GPL-unfriendly companies) interpret this situation is that the viral nature of the GPL goes both ways -- if you link to a GPL library, you're now forced to GPL your app, and if you link a non-GPL library to your GPLed app, that library must now be GPLed. This is exactly what Microsoft is trying to prevent. Remember, the GPL has not been tried in court yet (I don't remember exactly what happened with the recent MySQL case, but I seem to recall it was settled out of court. Anybody want to clear this up?), and so the lawyers are interpreting it pretty broadly to be safe.


      This is not Microsoft being malicious about the GPL. It's Microsoft following the CYA (Cover Your Ass) policy with their own intellectual property.

  8. Can you spell Prior Restraint? by mattr · · Score: 4, Interesting
    Section 3.2 says M$ is giving away the technology for free with the stipulation that it cannot be freely redistributed. The reasoning is that M$ is limiting the scope of intellectual property rights being granted so that no free implementation of their spec can exist. It would seem that an implementation for $0.01 or less might be okay.

    This shit is legal?

    If it is, why not just ruin their market? A client which on installation calls a 3rd party server anonymously, to indicate a sale. The dealer donates all the money to the dolphins or maybe the FSF. No money is collected, he just donates on behalf of all the users.

    Scenario two: The software is only sold in 1000,000-packs, price is 1 cent. What constitutes a sale? What constitutes prior restraint on business? Microsoft does not make money directly from this license it would seem. Is it possible for them legally to force a licensee to take a profit?

    This could sprout a new anti-anti-GPL: Just like BSD but the FSF or somebody else puts up 1 cent for enough copies to cover the world population. We can have a $10 fund to cover any number of M$ products which use this until the sun explodes. Perhaps we should use a dead currency that will give us better compression..

  9. new status quo worse for open source by fishbowl · · Score: 4, Interesting

    If this license is allowed by the court,
    it is now far worse for the open source developer
    than before the trial!

    Now there is a specific exclusion for a specific competitor. Would the contract be legal if it named a company instead of the GPL?

    --
    -fb Everything not expressly forbidden is now mandatory.
  10. They don't like GPL? Fine! by Alex+Belits · · Score: 5, Interesting

    All reimplementations of this then will be released under a different license that is an exact copy of GPL, plus an additional clause that Microsoft or any entity that is owned by Microsoft is prohibited from using it. Technically it will be perfectly ok under Microsoft's license -- it's not GPL at all, it's not even compatible with GPL.

    --
    Contrary to the popular belief, there indeed is no God.
    1. Re:They don't like GPL? Fine! by Alex+Belits · · Score: 5, Interesting

      This probably requires clarification -- it complies with the license because distribution is no longer free -- Microsoft is excluded.

      --
      Contrary to the popular belief, there indeed is no God.
  11. Re:Microsoft can do this, but... by kennyj449 · · Score: 2, Interesting

    Of course. Think about it: just for one example, what if someone sat down one evening and seriously made Outlook Express secure? BILLIONS of dollars in repair costs saved worldwide. Driver support extended to other OSs, as well - offering more choices. WINE would begin to kick ass. Possibly offer MUCH better network transparency in Windows more akin to that in *nix. Improved security in Windows so it won't have stupid holes like raw socket access to anything that wants it. Improved compatibility with Windows protocols in *nixs. NTFS support in *nix that's safe. *nix bootloaders like GRUB able to boot NT, 9x, even DOS "kernels" directly instead of relaying through native loaders. The possibilities are limitless. And, there are sure as hell a ton of programmers out there who are Win-only for whatever inane reason who'd have a lot of interest in, at the very least, seeing how M$ implements higher-level API functions, for example. All in all, open Windows source would result in massive improvements in both Windows and *nix. M$ won't be able to make money off of it using the same business model they currently rely upon (pay per license or face rabid lawyers) however, and as a result it'd never happen.

  12. Welcome To The Real World. by Carnage4Life · · Score: 4, Interesting

    First of all, there is no way Microsoft can enforce conditions upon the implementation of a standard (read: "standard"). Entering into a contract requires, well, that you enter into a contract.

    The above sentence is meaningless. First of all what do you mean by "standard"? A defacto standard like Flash, a standard ratified by a standards body, an industry standard (like Java), or something else? Secondly, regardless of what you meant if MSFT has patents on technology they are well within their rights to license it however they see fit.

    Here's the argument that Microsoft and other anti-GPL nutballs are making: "You're not making any money off this, so we want to steal your intellectual property, violate the hell out of your license, and make money from our criminal activities." The underlying, unstated argument is, of course, that unless you're in it for profit, you have no intellectual property rights. This is utter bullshit, of course, and serves only to show what basically unethical and indecent people we're dealing with.

    Interesting, I am curious as to what MSFT literature you read that made you come to that conclusion. From what I've seen of the anti-GPL rhetoric that has come out of MSFT, they are primarily against Richard Stallman's political agenda that comes with the GPL. They see nothing wrong with altruistically giving away code (which is what the BSD license and its ilk are about) but licenses like the GPL that attempt to devalue the cost of software are anathema to such people. The GPL drives the cost of software to 0 or at worst the cost of distribution media (just take a look at Cheapbytes for a living example of this). This means that any entity that produces GPL software most augment their income in some way be it through moonlighting, consulting, support, selling hardware, etc. This is not a mere side-effect but was an explicit goal of the GPL which can be garnered by reading Richard Stallman's early writings especially the gunk about software developers should work as waiters so that we can afford to give our software away.

    Since the GPL makes it near impossible for an entity to simply produce and sell software as its core business, it is unsurprising that the world's largest software company would be wary of doing anything that encouraged the spread of this meme. What is surprising is that most observers find it difficult to realize this and instead of applying Occam's Razor, resort to conspiracy theories about how MSFT wants to steal their code. Then again this is the same website where people bitch about Slashdot's responsibility to slashdotted webservers and how The Great Slashdot Whine Out will strike a blow for Freedom so maybe I shouldn't be so surprised after all.

    Disclaimer:This post reflects my opinions and does not reflect the opinions, strategies, thoughts, plans or intentions of my employer

    1. Re:Welcome To The Real World. by Chris+Johnson · · Score: 3, Interesting
      They don't want to STEAL your code. They write their own code, thank you.

      They want to be able to say: "*ahem* Your program is taking too much of our marketshare. Now, when you agreed to our shared source license, you agreed that you've seen our IP, and further agreed that you have no right to our IP, and further agreed that any patents you may have cannot be used to defend yourself against us. Therefore, kill your program."

      "You heard us. Kill your program. Take it off the market or we sue for infringement of our intellectual property, using the admissions you have already made in assenting to our license."

      Why should they steal your code when they can deep-six it just so long as you have been, at some time, exposed to 'Shared Source'?

  13. Monopolistic argument? by cipset · · Score: 2, Interesting

    Isn't this also a way of restricting competition? If there is a company which has a bussiness model based on GPL/LGPL then is this not a method of throwing them out of the market by forbiddig them access to info otherwise accesible to other companies?

    It is like showing the people how a disease can be cured and then forbid them use the cure because they give it for free and insist that their cure to be free.

    I do agree GPL/LGPL makes about the same but shouldn't we apply here the general interest bias?

  14. Layer between M$ and GPL'd software by DocSnyder · · Score: 3, Interesting
    What about choosing a license for a library or a dynamic module between M$' "property" and Free software which does not count as IPR Imparing License but permits being used by GPL'd programs?

    For example, the Linux kernel is GPL'd but allows non-Free modules to be loaded dynamically. Lots of Free programs may be linked against non-Free system libraries, e. g. on AIX or Solaris. Why can't we do the same with Samba? Of course, the module or library has to be optional, but so is a non-Free kernel module.

  15. Re:Unenforceable, self-contradictory, and stupid by Beliskner · · Score: 2, Interesting
    "You're not making any money off this, so we want to steal your intellectual property, violate the hell out of your license, and make money from our criminal activities." The underlying, unstated argument is, of course, that unless you're in it for profit, you have no intellectual property rights. This is utter bullshit, of course, and serves only to show what basically unethical and indecent people we're dealing with.
    Sounds like Microshaft is copying the Government's encryption export tactics.

    There's an easy way to get around this - get a Saudi Arabian coder to read Microsoft's "secret" documents and implement them(under Sharia law IP laws are unIslamic and therefore don't apply). Microshaft is based in Redmond, so they have to follow US law more or less worldwide. But some OSS coder in Pakistan is untouchable. Of course if the CIA implants the right politicians like Karzai in Afghanistan then we could see worldwide IP laws in which case Microshaft IS the law.

    It's a sad day when OSS coders must use the same tactics as binLaden to evade the law :-(

    --
    A caveman dreams of being us, the incalculable power and riches. We dream of being Q, then what?
  16. Beat them at their own game? by uglyduckling · · Score: 2, Interesting
    I don't know if I'm missing something here, but is there anything that MS can do about the following sequence of events:-

    1. Developer with access to the source code writes a paraphrased or pseudo-code representation of a key algorithm or data structure.
    2. Developer posts their representation to a NG anonymously, using a cyber cafe or open-access computer somewhere so they can't be traced.
    3. OSS developer downloads the representation and writes their own implementation.
    Now, I realise that step 1 is agains the contract terms, but I could realistically see a situation where a developer working in a software company could take a photocopy/ burn a CD of the source without having ageed to the license themselves; or to put it another way, if the code gets distributed widely enough for it to get close to increasing competition in the OS and apps market then it will be on a lot of desks in a lot of companies with lots of margin for error in terms of who gets to see it.

    My questions are:

    • Would MS have grounds for prosecuting the OSS developer for basing their SW on code that they knew/ suspected came from an unauthorised disclosure of the source? Or would it simply be the developer in step 1who could be prosecuted.
    • If the source become widely distributed (verbatim or otherwise) would the 'trade secret' (or lack of) thingy come into play, meaning that anyone involved in computing above a novice level could be expected to know that particular algorithm or data structure, and it therefore not legally be considered 'secret' anymore
    • If this was the case, would everyone have to stop writing open-source software, or would the reverse be true, that MS would no longer be able to enforce their 'IP rights'?
  17. New approach required by Anonymous Coward · · Score: 1, Interesting

    A while back I was looking for a decent free implemation of an NFS client for Windows 2000, for talking to a Linux Server.

    I couldn't find one (maybe I'm blind). This is a bad thing. It means the community is bending over for a MS network protocol. Turn the tables and make the MS platform the network's bitch.

    My point here is that instead of dealing with bullshit IP patents and paying royalties to use a defacto networking standard, use the "released" source to build better NFS (or whatever you fancy) clients for Windows platforms.

  18. The net effect (sorry for the pun!) (Not!) by Rocketboy · · Score: 3, Interesting
    It seems to me that the net effect of Microsoft's abuse of the patent system (and not only Microsoft, but I expect them to be a very aggressive enforcer of their "patents") is to destroy the very concept of intellectual property in the United States. Consider that A) Most software patents are, as has been noted, idiotic to the most casual observation, completely ignoring in most cases the existance of prior art, and B) the art of software development is not the exclusive playground of US developers. I believe that the time is coming when the software market will be split into two spheres: the United States and the rest of the world.


    Between the DMCA and other laws passed for the express purpose of enriching large corporations at the expense of the multitude of small niche competitors, and the rampant abuse of patent law, software development in the United States is rapidly becomming a closed guild wherein only the large corporations who own portfolios of spurious software 'patents' can afford to play. When an independent software developer or a small software company discovers that fundamental computing concepts are locked up in idiotic patents which they can not afford to either license or litigate, they will, I believe, decide to do something else with their time. Why not? If every piece of software you release into the world exposes you to the threat of financially ruinous litigation, how can you release anything? That is exactly the environment Microsoft is creating.


    Yet not all software is developed in the United States. At the moment the rest of the world pays lip service to US copyright and patent law, including the DMCA, because the US is such a large market. But what happens when it becomes much more expensive to do business in the US because of the cost of defending your products against patent litigation, or due to the need to purchase multiple patent 'licenses' for every product you sell? In this case, extensive portfolios of software patents become a barrier to trade and I would expect to see action in international trade court against them at some point.


    History teaches us that when confronted with difficult obstacles people tend to find a way over, around, or through them. I believe that we will find ways around these spurious, artificial legal barriers as well. Being a simple sort of person, I imagine that we'll end up simply ignoring them. Even Microsoft can't bring 10,000 patent infringement lawsuits against every individual writing GPL'd or otherwise competing software. They'll pick a few high-profile cases as warnings to others but eventually people will figure out that Microsoft is not about to spent a couple of million dollars suing each independent developer. I expect to see cases where developers release software and then 'disappear' into the void, essentially becoming phantom targets. I expect to see developers release software in other, more innovation-friendly countries. I expect that net effect of the DMCA and current patent law will be, like the tax code of the IRS, simply to make most of us criminals, just because no-one knows all of the law or all of the moronic patents which have been granted. We live with it now, we'll manage to live with it then. The difficulty for a societal point of view is that once people begin ignoring 'bad' laws, they ignore the 'good' ones also. Injudicious use of intellectual property law in a misguided attempt at protecting software monopolists will simply result in widespread disregard of all intellectual property laws, including copyright.


    "Sten". My name is "Sten". As far as you know!

  19. BSD LIcence that inhibits MS by theolein · · Score: 2, Interesting

    What is needed is to stop MS treating everyone like dirt. It needs a BSD style licence that specifically states that MS can in no way use this software but anyone else can. Since MS is not above using BSD style code it means that this option will no longer available for them.

    I'm not an American and I will be writing to the European comittee investigating MS and ask them to note this new MS licence and it's possible effects on the European Software industry.

    I'm pretty sure IBM will have noticed this as well and this will negatively impact their business since they into Linux as well.