Slashdot Mirror


Linus Speaks Out On GPLv3

Slagged writes to mention the word that Linus Torvalds isn't a fan of the new GPL draft. News.com has the story, and someone purporting to be Linus is causing a ruckus in the Groklaw thread on the subject. From the News.com article: "Say I'm a hardware manufacturer. I decide I love some particular piece of open-source software, but when I sell my hardware, I want to make sure it runs only one particular version of that software, because that's what I've validated. So I make my hardware check the cryptographic signature of the binary before I run it ... The GPLv3 doesn't seem to allow that, and in fact, most of the GPLv3 changes seem to be explicitly designed exactly to not allow the above kind of use, which I don't think it has any business doing."

11 of 615 comments (clear)

  1. Linus is wrong by Anonymous Coward · · Score: 5, Insightful

    I don't think manufacturers have any business preventing me from running my own code on hardware I purchased, at that stage I may as well be using MS Windows.

    1. Re:Linus is wrong by Spazmania · · Score: 5, Insightful

      This is a twisted and difficult issue.

      On the one hand, the whole point of open source is that you can change it and then run your changed version. That shouldn't be suddenly untrue at the arbitrary border between hardware and software. Hardware that uses approved versions of open source while actively preventing my version from running violates the spirit of the thing.

      On the other hand, most of us have spent the last decade saying that its OK to use both open source and closed source software on the same machine. No one argues, for example, that you can't run GCC on top of a closed-source unix kernel even though it requires that kernel in order to run. Nor does anyone argue that the processor and other chips used by the kernel must be an open, free design.

      The real problem, I think, is that RMS (via the FSF) is trying to force it down our throats as usual. He's a strange bird in that he really gets the freedom issue at one level while it flies totally over his head at another.

      I think I'd put the DRM stuff in GPL3 as an optional component and see what happens. Let us authors decide whether we want it. If it works for us, it can be made permanant in GPLv4.

      So I'd do something like this: Software released under the GPL MAY designate (on either a file-by-file or full release basis) that it can not be used by any device which by design actively prevents its legitimate owner from adjusting the software or data. Distribution of code so designated would be fully compatible with distribution of any other interlinked GPLv3 code with the sole exception that binary forms of the portions so designated may not be distributed for use with the restricted systems.

      But then I'm a vi guy. Maybe if I'd written emacs I'd see it differently.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  2. on the other hand by ptr2004 · · Score: 5, Insightful

    Say I'm a hardware consumer. I decide I love some particular piece of hardware and buy it with my hard earned money. But when I try to run one particular version of open source software customized for me, it doesnt run because the hardware complains it is not validated.

  3. You are wrong by Phillup · · Score: 5, Funny

    Manufacturers should be able to go out of business in any method they desire.

    --

    --Phillip

    Can you say BIRTH TAX
    1. Re:You are wrong by Anonymous Coward · · Score: 5, Informative

      Yup. GPLv3 is just plain dumb. It "addresses" a non-existent problem. People have a choice between DRM and non-DRM platforms and software. They can and do vote with their wallets.

      Yes, but currently Free Software authors are subsidising the development of platforms that takes their Free code and locks it up so that it can't be modified or replaced. A lot of Free Software authors don't like this because it defeats the whole point of Free Software. That is the problem that it solves.

    2. Re:You are wrong by illuminatedwax · · Score: 5, Insightful

      No, it fixes a very important issue.

      You know the story of rms' printer driver: he wanted to be able to modify the printer driver so it would bloody work right or work better. He couldn't do that, so he made GNU.

      Now let's say the new rms. smr wants to fix his printer which is running embedded GPL software. Great, he thinks, I have the source code to this, so I can just fix the source and make my printer work/better.

      Oops! The printer doesn't allow you to do this. This is an awful loophole that restricts your freedom to modify the program. You can modify it, but you might as well write it on on a piece of paper for all that's worth. What the user needs to be able to do is modify the software and use it to really have that freedom. GPLv3 protects this. Linus is really being a stubborn idiot about this.

      --
      Did you ever notice that *nix doesn't even cover Linux?
  4. Re:Of Course That's the Point by Anonymous Coward · · Score: 5, Insightful

    And the copyright owner of the software has the right to restrict the use of that software on devices which perform that hardware check. What's your point?

  5. Re:Of Course That's the Point by Pausanias · · Score: 5, Insightful
    BlackGriffen wrote:
    It's fine to have the hardware validate the software, I don't think anyone can rationally argue against that. What's not fine is to have the hardware refuse to run the software at all. If the user is conscious that the software is modified and therefor unsupported, then the user should have the ability to run any software he chooses. So, have a cryptographic check alongside a message or error light or something about running in unsupported mode, but don't completely cripple the hardware just because you want to avoid support headaches.
    What you say makes sense; however, I don't think the current language of the GPLv3 draft is clear on this point. Here is the relevant passage, emphasis mine:

    The Corresponding Source also includes any encryption or authorization keys necessary to install and/or execute modified versions from source code in the recommended or principal context of use, such that they can implement all the same functionality in the same range of circumstances. (For instance, if the work is a DVD player and can play certain DVDs, it must be possible for modified versions to play those DVDs. If the work communicates with an online service, it must be possible for modified versions to communicate with the same online service in the same way such that the service cannot distinguish.)
    It seems that the first phrase in bold allows what you describe: "implement all the same functionality" does not seem to prohibit a pop-up warning that the code is unsigned. However, the second phrase in bold says that modified versions must be indistinguishible from the original source from the point of view of an outside device. This seems to prohibit that same pop-up warning. So, it seems that Moglen & Stallman still have some clarifying work to do.
  6. Benevolent Dictatorship... by d.3.l.t.r.3.3 · · Score: 5, Interesting

    By my point of view a benevolent dictator is still a dictator.

    We should thank Torvalds to keep the questioning open, otherwise it would be like Christian Church: the Pope speaks, the lambs obey.

    The article also makes a very saddening statement: the GPL3 is basically written by the companies behind the FSF. The article cites that HP is pushing to have their own interests protected. Do you really think that other GPL-oriented companies (like IBM or Novell) will just stay and look or they will also try to drive the boat towards their coasts?

    After all, FSF made just a favour to many commercial distributions (another case of uninterested philantrophism?), claryfying that if you have to fork a distro, you have to redistribute every single packet by yourself, instead of shipping only the relevant, modified ones like GPL says. GPL is too generalized and vague. You can't have a license that has hundreds of pages of "clarifications" continuosly swapped and rewritten to praise an actor or to damage another. Most of the clarifications are just more ambiguos or simply idiotic. Do you know that by FSF interpretation, subclassing or implementing an interface is considered a derivative work? That's makes impossible to use any object oriented library released over LGPL by the term of the license, they will be as plain and simple GPL licensed code. There's a lot of OOP libraries wrongly placed in the LGPL domain. Do you really think that their author bothered about the implications? They just followed the leader. For not good reason and without a clue. Why LGPL3 talks only about header files and libraries? Open source licenses should be technlogy neutral and C/C++ is not the only language out there. Sure our benevolent dictator may pretend that the other technologies are not there gut they will not fade away. Today IT rarely uses anything compiled aside core OS programs and it's hard to find a place for the delusional aims of a puppet in the hands of other non-Microsoft corporations.

    Sure A guru's life is expensive and big corporations makes hefty donations. Let Stallman explain to us mortals why Microsoft has to be destroyed and IBM or HP are valiant partners whose interests are to be protected.

    HP advanced pressures to make the GPL3 more friendly towards their PATENTS! The world got upside down or what?

    --

    Matteo Anelli

    .brain - http://www.dot-brain.com

  7. Re:Of Course That's the Point by GigsVT · · Score: 5, Informative

    Linus's whole point is that the GPL 3 dictates technical details of projects that use it, where V2 didn't.

    GPLv2 dictated technical details that affected the next user's right to modify the software. For example, you couldn't link a modified GPL program with a closed source library, since that would hamper the ability to modify the software.

    The spirit of the GPL has not changed. The "political goal" is to ensure that all downsteam users that wind up using GPL software have the same rights to modify and distribute the software that earlier users had. That has not changed. It's only closing a loophole that some companies can use to take away those rights without violating the letter of the GPL.

    --
    I've had enough abrasive sigs. Kittens are cute and fuzzy.
  8. The heart of the issue by PostPhil · · Score: 5, Insightful

    The FSF's stance is controversial (as exemplified by the GPL 3) because it's about freedom, which for all of human history has been hardly understood.

    Licenses like BSD/MIT have a view of freedom that is more like anarchy: the "do anything you want" style of so-called freedom (but at least give credit to who wrote the code). This stance doesn't actually create freedom because "anything you want to do" can also include taking freedom away from others. BSD people used to argue that you would still have freedom, only it's with the old code before the proprietary fork, etc. But DRM and other methods of preventing you from modifying and running software is not protected by BSD licensing. So, it is even more true today that BSD-like licensing in actuality has little to do with freedom and more to do with technological research without regard to the sustained openness that made studying that code possible.

    Freedom must be preserved and encouraged in order to exist! It is not a spontaneous choice that can be made after neglecting its preservation. Once freedom is gone, once official mechanisms are in place to restrict you, you can't simply make a choice to be free again. When I think of the FSF, I believe they understand freedom as many others have realized throughout history...

    "You can only protect your liberties in this world by protecting the other man's freedom. You can only be free if I am free." - Clarence Darrow

    "None are so hopelessly enslaved as those who falsely believe they are free." -Goethe

    "Liberty without learning is always in peril and learning without liberty is always in vain." - John F. Kennedy

    ...while the FSF would probably characterize false freedom as this:

    "After I asked him what he meant, he replied that freedom consisted of the unimpeded right to get rich, to use his ability, no matter what the cost to others, to win advancement." - Norman Thomas

    The more we are tempted by money to deprive others of freedom, the less freedom we all have in the end, and the less it's worth living in such a society even if you're rich. Don't worry about people crying about loss of profitability, etc. History has always shown that there will always be clever people that will find some way to make money, whether people are free or in chains.