Slashdot Mirror


RMS Previews GPL3 Terms

An anonymous reader writes "In a recent interview, ESR shocked a lot of people when he said, 'We don't need the GPL anymore.' Federico Biancuzzi contacted RMS, founder of the Free Software Movement and initial developer of the GNU system, to talk about the past, the present, and the future of the GNU GPL. Among other things, they discussed the new clauses of the upcoming GPL version 3."

57 of 312 comments (clear)

  1. Recognizing the need for the GPL... by goldspider · · Score: 2, Insightful

    ...acknoledges the need for copyrights and/or IP laws. RMS is finally being consistent.

    --
    "Ask not what your country can do for you." --John F. Kennedy
    1. Re:Recognizing the need for the GPL... by bersl2 · · Score: 4, Insightful

      Try again.

      Q: If the author of GPL says "copyright infringement is not necessarily wrong," some people could take code covered by GPL and claim that violating GPL terms is "not necessarily wrong."

      A: I've addressed that point in the statement that inspired your question.

      The GPL gets its legal force from copyright law, but that is not a source of moral authority, so none can come from there. Why then is it wrong to violate the GPL? Because that tramples other people's freedom or puts it at risk.

    2. Re:Recognizing the need for the GPL... by rolfwind · · Score: 2, Interesting

      No, it's playing the game and it recognizes the need that you're not in an ideal world and have to protect yourself from those who don't believe in a free exchange of ideas but in software patents, etcetera.

      Put it this way - Linus will not go out and start suing people for infringing his software patents (please don't bring up the trademark issue which was a different matter entirely) - but if someone ever decides to attack the Linux - Linus can hold up his patent portfolio and say "Buddy, are you are sure you wanna do this? Your company has nothing that infringes on mine?"

      Reminds me of Mutual Assured Destruction^_^

      I wonder if RMS has something similiar to Linus in this regards (of a patent portfolio), but the GPL is similiar and a smart strategy. GPL software has to protect itself.

    3. Re:Recognizing the need for the GPL... by harlows_monkeys · · Score: 3, Insightful
      iirc the fsf has said that they consider the GPL to be using copyright against itself and they would be fine with copyright dissapearing altogether

      I find this hard to believe. Can you find a cite?

      The reason I find it hard to believe is that without copyright, everyone would be free to release binary-only versions of any GPL code.

    4. Re:Recognizing the need for the GPL... by bentcd · · Score: 2, Informative

      Violating the GPL is wrong because it attacks the freedom of other people, which is immoral. Pirating music is illegal, but for no good reason, so is not immoral. Therefore, the former gets bashed while the latter is ignored or even encouraged. This is hypocritical only if you subscribe to the world view that "illegal is always wrong and legal is always right", but I expect that many of the posters you refer to do not.

      --
      sigs are hazardous to your health
    5. Re:Recognizing the need for the GPL... by monkeydo · · Score: 2, Informative

      If they hadn't required an NDA, he would have happily fixed the problem, given the fix to anyone who asked, and moved on with his life. However, the NDA and copyright prevented him from doing so.

      Except that an NDA has nothing to do with copyright, it's a private contract. Even if they hadn't required an NDA, he still couldn't redistribute his derivative work without permission of the copyright holder. And if there were no such thing as copyright they would have been more, not less, likely to require an NDA.

      --
      Si vis pacem, para bellum
      The only thing more annoying than a Libertarian is an (un|mis)informed Libertarian
  2. It also appers to mandate s/w features by myc_lykaon · · Score: 3, Insightful
    From TFA:

    What do you mean?

    If you release a program that implements such a command, GPL 3 will require others to keep the command working in their modified versions of the program.

    Isn't it a slippery road to go down when the license mandates a feature-set? It seems to make a mockery of the 'free to modify' mantra. In fact it seems to be 'not free' in that sense.

    1. Re:It also appers to mandate s/w features by albalbo · · Score: 4, Informative

      Nothing in the GPLv3 is remotely decided. People keep throwing ideas out there to see which fly, some may, most won't.

      --
      "Elmo knows where you live!" - The Simpsons
    2. Re:It also appers to mandate s/w features by Chris+Burke · · Score: 4, Informative

      Only one feature. The previous paragraph from TFA:

      Some companies, such as Google, use code covered by GPL to offer their services through the Web. Do you plan to extend GPL 3 copyleft to request code publication in this case too, considering this behavior like a product distribution?

      Running a program in a public server is not distribution; it is public use. We're looking at an approach where programs used in this way will have to include a command for the user to download the source for the version that is running.

      But this will not apply to all GPL-covered programs, only to programs that already contain such a command. Thus, this change would have no effect on existing software, but developers could activate it in the future.


      So the "such a command" phrase in the paragraph you quoted does not mean "any command". It refers to a specific command to allow source download of a web-app. It doesn't say whether this command would have to still exist if you didn't use your modification as a web-app.

      I'm not sure I like that kind of clause, but it is very different than what you said. You statement made me worry that RMS would do something as foolish as mandate an unchanging feature set and interface, but that isn't true.

      --

      The enemies of Democracy are
    3. Re:It also appers to mandate s/w features by Breakfast+Pants · · Score: 2, Insightful

      It also doesn't seem like it will work. You can just expose all your services through two layers: the first layer is powered by modified GPL code, and includes the function for sending out the code. The second layer is just a wrapper that isn't GPLed at all and only passes function calls to the first layer and pipes output back to the user. The catch is this second layer can be made to not pass the "give me the code" function.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
  3. GLAMP? by khasim · · Score: 2, Funny
    Federico Biancuzzi recently contacted RMS, founder of the Free Software Movement and initial developer of the GNU system (the G in "GLAMP"), to talk about the past, the present, and the future of the GNU GPL.
    gDid gI gnot gget gthe gmemo gon gthis? gHow glong ghas git gbeen "GLAMP"?
    1. Re:GLAMP? by ajdlinux · · Score: 2, Informative

      If you acknowledge that the GNU project wrote more of your 'Linux' distro than Linus did, it's GLAMP.

  4. The freedom to confuse by teslatug · · Score: 4, Insightful
    Check out the following quotes:

    Maybe you could talk about the common question that people have: a project under GPL that receives a patch under GPL 3. What happens?

    If the project's current code permits use under "GPL version 2 or later," they can integrate that patch. However, the files where they have merged in the patch will have to say "GPL version 3 or later."

    They also have the option of not using that patch, or asking the contributor to give permission for its use under "GPL version 2 or later."

    If I take a patch under GPL 3 and merge it with a project under "GPL 2 or later," should I write that the new license for the whole project is GPL 3?

    The merged program as a whole can only be used under GPL 3. However, the files you did not change could still carry the license of "GPL 2 or later." You could change them or not, as you wish.


    This new version, and later ones will confuse, fragment, and even make illegal many contributions and/or projects in the future. I think this will prove to be a weak link in Free Software as people try to mix GPL2 with GPL3 projects, and make a mess of things. Whatever benefits there are of GPL v3, they will be overshadowed by this mess it will create.
    1. Re:The freedom to confuse by eobanb · · Score: 3, Funny

      Well see this preview is like a GPL beta. Or unstable. In fact, let's called it something like GPL, the Messy Midget. I suggest you try the stable, though perhaps slightly outdated GPL 2.x tree, last updated in 1991.

      You know maybe we should have some other distributions of the GPL. We could have one called GPLspire, that basically comes with a legal team that you have to pay for each month to ensure that others don't violate your licence. Or how about SlackGPL, that tries to be as much like the Communist Manifesto as possible.

      Burn, karma, burn.

      --Eoban

      --

      Take off every sig. For great justice.

    2. Re:The freedom to confuse by RickHunter · · Score: 3, Insightful

      Nope. Note that this only applies if the patch explicitly says "GPL v3". The normal case is for contributions to be under the same license as the original codebase - in this hypothetical case, GPL v2. Someone submitting code licensed under GPLv3 to a GPLv2 project would be just as unlikely as someone submitting GPL'd code to a BSDL project, or vice-versa.

    3. Re:The freedom to confuse by swillden · · Score: 4, Informative

      Someone submitting code licensed under GPLv3 to a GPLv2 project would be just as unlikely as someone submitting GPL'd code to a BSDL project, or vice-versa.

      I think the more likely "problem" scenario is where a developer on a GPLv2 project wishes to borrow code from a GPLv3 project. However, very few projects are GPLv2... most of them use RMS' recommended language and are therefore best described as GPLv2+, where the '+' means that the code can be released under any later GPL version.

      Let me see if I can enumerate the possible scenarios and describe the effect of each.

      • GPLv2+ borrows from GPLv3+. No problem, but the specific files imported/modified are under GPLv3+, and the project as a whole is distributed under GPLv3+.
      • GPLv2+ borrows from GPLv3. No problem. The result is GPLv3. This might be a bad idea if the GPLv2+ project wishes to be distributable under GPLv4+.
      • GPLv2 borrows from GPLv3 or GPLv3+. Can't do it. One side or the other must provide another license.
      • GPLv3+ borrows from GPLv2+. No problem.
      • GPLv3+ or GPLv3 borrows from GPLv2. Can't do it.
      • GPLv3 borrows from GPLv2. Can't do it.
      • GPLv3 borrows from GPLv2+. I don't think there's a problem here. The recommended RMS language would seem to allow a user to remove the upgradeability.

      That looks bad, but in practice I doubt it will be. Very few projects are GPLv2, and probably even fewer will be GPLv3. The only major project I know of under GPLv2 is the Linux kernel, and it is sufficiently important that it's unlikely to be hampered by the inability to pull in GPLv3[+] code. If a feature is generally desirable in Linux, someone will invest the effort to re-implement it for Linux. In most cases that really has to be done anyway, for technical reasons.

      I think that if GPLv3 adds enough value to be compelling, most projects will end up migrating to it. Those, like Linux, that can't will simply continue onward with GPLv2. They may wish they had the GPLv3, though, if the FSF can find some language that handles the patent issue well.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  5. ESR best forgotten by Lulu+of+the+Lotus-Ea · · Score: 3, Funny

    In a recent interview, Eric Raymond shocked many Free Software developers. Interviewed developers commented "What? Is he still around? Now there is someone you don't think about anymore." Raymond's contentious statements were uniformly viewed as desperate cries for attention by a once notable software developer. A sympathetic developer commented, "I certainly hope ESR gets the professional counciling he so obviously needs; he just needs to learn that you can lead a productive life outside the limelight. I know of a good support group for people like him and Dvorak."

    1. Re:ESR best forgotten by Lulu+of+the+Lotus-Ea · · Score: 2, Informative

      Fetchmail is/was a fairly useful program. And his two famous essays, "Cathedral and Bazaar" and "Homesteading the Noosphere" are reasonably interesting (not entirely accurate, but also not entirely without some reasonable analysis). But 1998 was the last time ESR did ANYTHING even remotely of public interest.

  6. I can't help thinking that by Anonymous Coward · · Score: 3, Interesting

    RMS would've made a great Supreme Court justice, had he gotten his law degree

    1. Re:I can't help thinking that by BrokenHalo · · Score: 2, Funny

      He would probably have also made a good Holy Roman Emperor if he had got around to taking the public service exam. :-)

  7. Section 4 Article 16 by Anonymous Coward · · Score: 3, Funny

    All developers and advocates of GPL software hereby agree to bathe on a minimum of a daily basis. Those developers that face the public further agree that they will brush their teeth priort to any such encounter, no matter how brief!

    I could believe this part, especially coming from RMS. It's no wonder ESR said we didn't need the GPL anymore.

  8. It's 2005, not 1985. by SpaghettiPattern · · Score: 5, Insightful

    It's 2005, not 1985. We've learned a lot in the last 20 years.
    Yeah we learned we need it more than ever before. Just imagine the SCO history without the GPL.

    If you rigorously cling on to values (like GPL and free speech) people think you're a zealot. Until the same people realize they themselves were idiots. GPL is what got Linux this far -and not it's technical superiority over whatever- and it remains needed to prevent doctor evils screwing people over.

    There's also the freedom to refrain from using the GPL and stop whining.

    --

    I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
    1. Re:It's 2005, not 1985. by swillden · · Score: 4, Interesting

      With all due respect, that's completely unproven, and in my opinion, completely untrue.

      I recall an interview with the Linux team at IBM where they said they did not think IBM would have contributed code under a BSD license. It was important to IBM that IBM's competitors not be able to use their code in proprietary products. I'm sure there are plenty of other cases where significant contributions to Linux would not have happened if it were under another license.

      It's hard to say that the GPL was essential to Linux, but I think it's very clear that the GPL has been helpful to Linux development. It has also enabled a major thrust of IBM's counterattack on SCO, which is perhaps not essential, but very pleasant :-)

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  9. Not quoted in context ... by Anonymous Coward · · Score: 2, Interesting

    This is about allowing people who release server software to mandate that any modified server running publicly will have to release the modified source code. That is the command he is talking about, and only that. Id hardly call that a feature set.

    Seems a decent enough idea in this day and age, if everyone starts running thin clients with proprietary code on the servers then the GPL becomes a bit useless.

  10. Already got it by Phantasmo · · Score: 4, Funny

    Just downloaded and installed the beta. Feels much snappier than the last release.

    I'll keep you guys posted.

    --

    The US Army: promoting democracy through unquestioned obedience
  11. Services by Richard_at_work · · Score: 3, Interesting

    At last someone on the GPL 3 team has said something that belays my fears about Services and the GPL version 3. The fear was that they would force you to give users access to GPLed code you use when you provide a service - for example forum software. From the article, they talk about developers including an ability to have the service software offer the sourcecode, and the GPL protecting this particular part of the program but not forcing developers to include it in the first place. While this does stop the fears that you would have to provide the sourcecode for every bit of GPL code you use in your service, it does open the door for limitations on modifications in GPLed programs, similiar to invariant sections in the Gnu Documentation License, and Im not decided if this is a good approach or not.

    1. Re:Services by mark-t · · Score: 4, Insightful
      As I've remarked elsewhere, this is not legally enforceable.

      Copyright only governs COPIES, not the services provided by those copies. If I am not distributing actual copies of the software (even if I may be distributing the service it provides), then copyright doesn't have any legal bearing, and the copyright holder can't legally force me to stop providing the service, even if I'm doing something he doesn't like (he could if I were to ever try to distribute the software as well, however). He is free, however, to politely *ASK* that I comply with his wishes, but it still has no legal weight.

    2. Re:Services by eraserewind · · Score: 2, Informative

      Really? insert software company here is free to ask you for money in return for using their software (with no redistribution). Is that not legally enforceable? The GPL2 is not a usage license, but there is nothing much to prevent a new licence (GPL3) from being one. What right would you have to have and use even one copy of the software without either purchasing the software, or obtaining it under license? I wouldn't consider any license that had such a clause to be particularly free, but I don't see how it could fail to be enforceable.

  12. Incompetent reporter by Anonymous Coward · · Score: 2, Informative

    Federico Biancuzzi is just plainly incompetent on the subject of software licenses. See his old interview to RMS to see how often RMS must clarify basic issues to him, and misuderstands Biancuzzi's dumb questions. I'm not going to read TFA this time.

  13. No by swillden · · Score: 4, Insightful

    Recognizing the need for the GPL acknowledges the need for copyrights and/or IP laws. RMS is finally being consistent.

    RMS has always been very consistent on this point. In his view, copyright is a bad thing because it restricts freedom. He views the GPL as necessary because the bad thing exists, and has always described the GPL as a form of legal judo, fighting the enemy with his own strength.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    1. Re:No by qbwiz · · Score: 2, Insightful

      But the GPL offers more protection to the original author than the lack of copyright laws would. If there were no copyright laws, then you wouldn't have to redistribute the source code and any modifications you made to it. A GPL in that vein would require that any derivative work based on the program would also have the GPL applied, and that the authors of the derivative and original works would allow anyone else to distribute those works (effectively, IANAL, etc).
      The GPL goes above and beyond that, and requires you to redistribute the source code. That is not merely the lack of copyright law.

      --
      Ewige Blumenkraft.
    2. Re:No by Dogtanian · · Score: 3, Insightful

      RMS has always been very consistent on this point. In his view, copyright is a bad thing because it restricts freedom.

      I realise the view is RMS's, and not necessarily yours. However, in a country where everything is permitted, except where it is explicitly prohibited, doesn't every law "restrict freedom" in some manner?

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    3. Re:No by aardvarkjoe · · Score: 2, Interesting
      But then I think copyright is a good thing,
      Yes, but RMS doesn't, and it was his supposed inconsistancy that the person responded to was talking about.

      However, my understanding is that RMS would like to not only get rid of copyright law, but create new laws that would essentially enforce releasing source code along with binaries. If that's the case, then his support of the GPL and opposition to copyright laws is not neccessarily inconsistant.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    4. Re:No by swillden · · Score: 2, Insightful

      However, my understanding is that RMS would like to not only get rid of copyright law, but create new laws that would essentially enforce releasing source code along with binaries.

      Yes, I think that's his position.

      Mine, BTW, is that we should keep copyright law (reigned in a bit), but make publication of source code a prerequisite for obtaining copyright protection. If you don't want to publish your source, you should have that option, but since you are defeating the purpose of copyright (which is to enlarge the public domain), you shouldn't benefit from it. You can always rely on contract and trade secret law to protect your software.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  14. GPL problems show Open Source Movement is by BrentRJones · · Score: 2, Interesting

    fragile. Maybe the GPL needs to be simpler, not more complex.

    --
    Help end the use of Sigs. Tomorrow
  15. Are you trolling? by Anonymous Coward · · Score: 2, Insightful

    Try *reading* the GPL. Its pretty much as simple as could be. It's way simpler than Microsoft's EULAs for example, even though the GPL gives you some freedoms and the EULAs just restrict your rights.

  16. Re:GPL3? by geekster · · Score: 2, Informative

    I'd say around June 1991

  17. Re:GPL3? by Knuckles · · Score: 3, Informative

    Talk about hiding in a cave ;) Version 2 was released in June 1991. Version 1 was released in February 1989.

    --
    "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
  18. ESR, GPL, RMS, GNU! by Anonymous Coward · · Score: 4, Funny

    WTF?

  19. Is questioning trolling? by BrentRJones · · Score: 2, Interesting

    I know the GLP having read it. I question why ver. 3 will actually help keep code freely available.

    --
    Help end the use of Sigs. Tomorrow
  20. GNU is too political. by jellomizer · · Score: 2, Interesting

    The problem with GNU and the proposed GNU 3 is that is is getting more and more political, and more of the politics are getting further away from just Open Source. Things like preventing GNU software to use DRM, and certon rules on pattents. While we can debate these are things are good or evil, as for as I see it shouldn't matter if it is GNU or not, if this keeps on growing, then there will be restrictions on if we use the GNU program for warfare, or in a government that we don't like. Keep the GNU Simple that is the only way to keep GNU goodness, when you keep on adding restrictive clauses it will become more and more evil.

    Yes people will use GNU software the way you didn't want them too. This is part of making a license.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  21. Re:Where GPL ends and propriety can start? by Knuckles · · Score: 3, Interesting
    I would really like to have clarification to my issues...

    Ask the FSF's compliance lab:
    The GPL Compliance Lab maintains resources for Free Software developers and others to learn about licensing. Members of the Free Software community are encouraged to consult with the FSF regarding licensing issues. However, before contacting the FSF please be sure to have reviewed the GPL FAQ before emailing us.

    The Compliance Lab also makes its services available by paid consultation, allowing businesess to access our unique expertise. These consultation services include a software certification program which is explained in detail here.
    And OT, when has the FSF revamped their website? Nifty.

    --
    "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
  22. WTF? GNU was always political! by Anonymous Coward · · Score: 3, Insightful

    GNU was always about the 'Free Software' ideal, NOT Open Source... get it right!

  23. ESR is wrong; per the usual by I_redwolf · · Score: 5, Insightful

    The GPL is an anchor of freedom. It has nothing to do with technical merits of ones software. It has everything to do with making software freely available and open in communal fashion. I'd like to think of the GPL as a digital library of function; with protection for not only the developer but the user. Similar to fountains of knowledge that have existed through out history allowing human-kind to prosper. It should be noted that all communes and libraries of the past that operated as a hub of knowledge have been almost entirely destroyed with few exceptions. I find it hard how one would do this with the digital medium but moving along.

    ESR seemingly doesn't understand that if it was simply about technical merit and time. In another 20 years we'll look back and it'll be a different story. Isn't history one of ESR's strong points? Here is another reason why ESR can't be coined as a forefront in opensource or what we all deem to be some form of movement. His views are totally not inline with freedom and freedom is what this is about. You release under GPL as a form of solidarity? How about in the future you refrain from releasing under the GPL and release under the license that you think is best. Solidarity and cowardness go hand in hand when you're in the minority.

    RMS on the other hand needs to learn that one can't force freedom. You can only protect it and the primary goal should be protection for the user and developer. The external parties should not matter beyond that. If they benefit in fashion from the GPL then one should not prevent that. This doesn't mean that the GPL should never change; I have faith that RMS will learn better to adapt the GPL to current environments as well as forseeing the road ahead.

    None the less my personal views are that RMS is a leader and ESR as a mumbling imbecile and sideliner. As much as people dislike RMS and fight and rally against him. He never sidelines and he never stands in solidarity with a position he disagrees with. He stands firmly in his belief for freedom and provided the framework on which I make my living, how I learned to make my living and how I even enjoy myself every now and then.

    So, unlike the rest of you; after I pickup my girl from the airport i'll have a beer in the name of RMS. Cheers; and thanks.

    1. Re:ESR is wrong; per the usual by Dogtanian · · Score: 3, Insightful

      None the less my personal views are that RMS is a leader and ESR as a mumbling imbecile and sideliner.

      Ever since he started skewing the Jargon File towards his own political beliefs (over-extending the hacker ethic to cover his 'libertarian' views, which if it was ever entirely true- dubious- certainly *doesn't* represent every hacker nowadays), I got the impression that ESR wants to give the *impression* that every hacker and supporter of free software is behind him and his views, as opposed to actually getting them onside. Or- and there may be some truth in this- perhaps he actually believes that he's more representative than he actually is.

      I'm not going to deny his contributions (both in code and support) to the open source movement, but that's more than offset IMHO by his egotism and partisan nature.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  24. Misunderstanding about Apache licenses by pauljlucas · · Score: 5, Interesting
    From TFA:
    We often hear that some 70 percent of web servers use Apache; what we don't hear is that a large fraction of those servers are using a nonfree modified version of Apache, as permitted by the Apache license.
    Those servers could equally well use modified versions of Apache even if Apache were under the GPL. The GPL comes into play only if you distribute your modified versions of Apache. If you keep your changes in-house, the whole issue is moot.
    --
    If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
  25. Re:Of course we don't need GPL by Dogtanian · · Score: 4, Funny

    GPL is not needed, GUNS are enough -and required- to protect the interest of the shareholders^Wprogrammers.

    Eric? Is that you?! Please log in before you post, thanks.

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  26. Re:ESR is right; per the usual by gowen · · Score: 2, Funny

    Eric is right. He doesn't need the GPL because the GPL is for people who actually write code.

    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  27. Re:Where GPL ends and propriety can start? by Homology · · Score: 2, Interesting
    In example if you use only MySQL, which is GPL, as database for you application, MySQL has defined this as linking, so making your own application also GPL.

    Then access your MySQL database over TCP/IP or a socket. No linking involved at all, thus no problem with GPL.

  28. TC is neutral; DRM is evil (IMO) by Xtifr · · Score: 2, Insightful

    Subject basically says it all. The so-called "Trusted Computing Platform" involves nothing more than having public-key encryption implemented in hardware, under the control of the BIOS. It can (in theory) be used for DRM, but can also be used merely to enhance the security of your system. The so-called "vendor key" may not have any practical, non-evil uses, but nobody is forcing you to use it. Personally, I'd like to have a system with TC hardware. (As long as any "remote control" functionality can be disabled, which, I suspect, would be hard NOT to arrange.)

    DRM, on the other hand, is pretty much an unmitigated evil. However, that said, I think the approach taken by the GFDL is the wrong one. I'd prefer to see distribution on DRM-controlled platforms allowed as long as unrestricted versions are available to anyone who gets a DRM'd copy. In other words, I'd like to see DRM treated by documentation licenses more-or-less the way binaries are treated by the GPL.

    1. Re:TC is neutral; DRM is evil (IMO) by Alsee · · Score: 3, Insightful

      Trusted Computing is about as "neutral" as an apple with a cyanide pill inside. Trusted Computing is explicitlydesigned to be secure against the owner.

      Citing the vitimins and nutrients of a poison apple does not make it good or even neutral if they forbid you to have a non-poison apple.

      Trusted Computing would be a good thing is the owner were allowed to know his own keys. However it would no longer be "Trusted". Owners could get all of the benefits of Trusted Comptuing and none of the abuses if you were allowed to know your keys. If for example you were allowed, if you wanted, to get key a printed copy of your PrivEK key when you bought the machine and to get your Root Storage Key encrypted to your PrivEK.

      That would be a nutricious poison-free apple giving the owner ALL of the security and other owner benefits of Trusted COmputing, all of the benefits you say you want.

      can also be used merely to enhance the security of your system

      An apple with a cyanide pill gives you vitamines. That is NOT any sort of argument defending Trusted Computing. It is an argument for an otherwise identical apple without any poison pill. It is an argument against Trusted Computing, an argument for identical hardware where you do know your master key.

      I'd like to have a system with TC hardware. (As long as any "remote control" functionality can be disabled, which, I suspect, would be hard NOT to arrange.

      And the new software Trusted Installation / Trusted Activation will be impossible to install or run at all. The new Trusted files wil be impossible to read. You will be locked out of all of the new Trusted websites... in particular tons of websites will want to use the Trust system to prohibit you from using any sort of pop-up blocker or other ad-blocker. And potentially in a few years under trusted Network Connect... which Microsoft is implementing under the name Network Access Protection.... you may be denied any internet access at all.

      Trusted Computing is all about the anti-owner Trust system. It is all about stuffing a poison pill standard inside every new computer sold. It is all about penalizing anyone who does not have a poison pill apple, andslapping handcuffs on anyone who does eat the poison pill apple. They absolutely REFUSE to permit anyone to buy poison-pill-free apples. They absolutely REFUSE to permit you to buy a compatible computer where you can/do know the master key to control your own computer. If you know your master key then you can avoid being locked-out, if you know your master key then you can avoid vendor lock-in, if you know your master key you can unlock DRM files, if you know your master key then it is not a Trusted Computer.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    2. Re:TC is neutral; DRM is evil (IMO) by Xtifr · · Score: 2, Interesting

      > Citing the vitimins and nutrients of a poison apple does not make it good or even neutral if they forbid you to have a non-poison apple.

      Oh yeah, gotta watch out for "them"! "They" are lurking behind every corner, waiting to pounce and install electrodes in your brain. Soon, "they" will control all your thoughts, and "they" will force you to sit on the couch watching reruns of Friends(tm) and drinking Diet Pepsi(tm).

      > And the new software Trusted Installation / Trusted Activation will be impossible to install or run at all.

      You really think Linus will accept that patch? I'm pretty dubious! On the other hand, he has accepted patches to allow me to control the TCPA chip on my computer, if I were to have one. Which, I admit, strongly piques my curiousity, and is the main reason I want to get one and check it out.

      I admit, if you're running an MS system, then TCPA may look like somewhat of a threat. But then, if you're running an MS system, you have already abdicated ownership and control of "your" system, and I've got no freakin' sympathy for ya.

      > The new Trusted files wil be impossible to read. You will be locked out of all of the new Trusted websites.

      Then, frankly, I'm screwed in any case, since I can't think of any circumstance that would induce me to run a kernel I didn't build myself. But, again frankly, I think you're being just a wee bit paranoid. Not that there's anything wrong with paranoia--some of my best friends, and all that--but I think it looks more and more these days like the balance of power is tipping away from Microsoft.

      In any case, what you're talking about is not TC, though it may be based on TC. I've read the specs, and I stand by my statement that TC is a neutral technology. And like a lot of security-oriented systems, it's not that secure if you have physical acccess to the machine. I kinda hope "they" do try to control all the computers of the world with TC; it'd be kinda fun to see "them" fall flat on their faces. Again. :)

      Remember, you're talking about the same consortium here that tried to prevent us from copying CDs by putting an autorun.bat file on them. They're not that freakin' smart! :)

  29. Re:Question about the GPL by HermanAB · · Score: 2, Interesting

    The GPL doesn't restrict your rights, it grants you rights. Therefore, an open ended version 2 or later clause is OK, since it can only grant you more rights, it cannot take any rights away that you already have.

    --
    Oh well, what the hell...
  30. ESR by paulatz · · Score: 2, Funny

    Does anybody know who is ESR?

    --
    this post contain no useful information, no need to mod it down
  31. ESR is pro-business, at the expense of individuals by Morgaine · · Score: 2, Interesting

    ESR's position against Free Software has always seemed slightly irrational (or at least unjustified) to me, but I always put it down to no more than him trying to get some more limelight for his Open Software efforts. That would be unfortunate, but no biggie.

    But now that he has publicly gone anti-GPL by saying that it is no longer needed, I think that ESR is finally showing his true colours.

    In a world where Free+Open Software ruled the roost (we're not quite there yet), the only people for whom the GPL might no longer be needed are those people who have an army of paid-up lawyers behind them, in other words, the corporations. Everyone else would get screwed by the first well-financed litigious bloodsucker that comes along and markets the software without respecting its authors' desired freedoms.

    So, it's pretty simple: ESR is pro-business, and actively desires individuals to be powerless and trodden underfoot in the corporate rush for profits.

    That's pretty bad, not far off from being "evil". I must say, I didn't really expect that from ESR.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
  32. Trusted Network Connect; DirecTV access cards by tepples · · Score: 2, Informative

    I can't think of any circumstance that would induce me to run a kernel I didn't build myself.

    How about the circumstance in which all kernels except the one approved by your ISP will fail to get an IP address?

    And like a lot of security-oriented systems, it's not that secure if you have physical acccess to the machine.

    Try telling that to anybody who has tried to crack the most recent DirecTV access cards.

  33. Only for large projects, Eric! by PhilHibbs · · Score: 2, Insightful
    People who do what the GPL tries to prevent ... trap themselves unto competing with a small in-house development group against the much larger one in the parent open source project, and failing.
    That's true for large projects like Apache, but if I decide to release some code that I wrote, and nobody notices, but some company decides that it would make a decent product, then I am SOL. The company gets market share before I can attract a developer community to help me bring the product up to 1.0 release standard.