Slashdot Mirror


RMS on Proposed GPLv3 changes

H4x0r Jim Duggan writes "Last Saturday - the first day of FOSDEM, Richard Stallman gave what seems to have been his first public talk about the draft GPLv3. Ciaran O'Riordan of Free Software Foundation Europe was there and, after recording with his digital camera, has published a transcript of RMS's GPLv3 talk. O'Riordan previously made a transcript of the January 16th first presentation on the GPLv3 which consists of 70 minutes of Eben Moglen, with 20 minutes worth of interruptions from Stallman."

222 comments

  1. A request by Raul654 · · Score: 1

    For those of us who don't feel like wading a 100 page discussion transcript in legalese, can someone link to a concise summary of the changes being made?

    --


    To make laws that man cannot, and will not obey, serves to bring all law into contempt.
    --E.C. Stanton
    1. Re:A request by stinerman · · Score: 1

      TFA is only the Stallman excerpts. It shouldn't take more than a few minutes to read.

    2. Re:A request by Tackhead · · Score: 3, Funny
      > For those of us who don't feel like wading a 100 page discussion transcript in legalese, can someone link to a concise summary of the changes being made?

      "Please stop calling it the GPLv3. It's GNU/PLv3!"

      /sorry RMS, I couldn't resist.

    3. Re:A request by ari_j · · Score: 1

      Actually, it's not. GPL stands for General Public License, not GNU Public License. But GNU/GPLv3 would be fine. :)

    4. Re:A request by Anonymous Coward · · Score: 0

      The GPL will be turned into something like the Microsoft Shared Source license.

      Better stay with BSD/MIT-license if you want your code to be free.

    5. Re:A request by squiggleslash · · Score: 2, Informative
      There's a few updates. Other than clarifications (for example, over GPLing something you have an exclusive or semi-exclusive patent license for that you can't transfer to licencees), the major changes I saw are:

      1. A manufacturer who takes GPL'd code, signs it, and then sells hardware that only runs code signed with their key, which they don't redistribute, is in violation of the license. This is relatively narrowly defined, despite Torvalds throwing a hissy fit about this part of the license a few weeks ago, thinking it outlawed all forms of DRM (it doesn't.)

      2. The license isn't automatically revoked upon it being breached. Instead the copyright holders have to give the breacher 30 days notice to allow them back into compliance.

      3. To make it more compatable with similar licenses, there's a whole bunch of optional terms and conditions that can be added. For example, you can say "If you sue us for patent infringement, you can't use any patents our code relies upon that we own, effectively ending your ability to use our software." The notable feature is that this is an optional condition.

      HTH. Anyone notice anything else that was major (ie not a clarification of something we largely knew anyway?)

      --
      You are not alone. This is not normal. None of this is normal.
    6. Re:A request by Golias · · Score: 1

      Still, the summary should at least give you some idea whether he's "fer it" or "agin it." Sheesh!

      --

      Information wants to be anthropomorphized.

    7. Re:A request by LordNightwalker · · Score: 2, Informative

      We recorded all the speeches this year and the movies can be found here. Not everything is up yet, and they're still working on ogg/theora versions, and the filenames may not be too descriptive if you weren't there, but whatever... I already sent some feedback and those issues will probably be fixed soon.

      Disclaimer: I was but a humble volunteer; don't spam me with any questions 'coz this is about all I know about the movies. ;)

      --
      Install windows on my workstation? You crazy? Got any idea how much I paid for the damn thing?
    8. Re:A request by Anonymous Coward · · Score: 0

      Any chance we could get a "-1: obligatory bad joke" mod button?

    9. Re:A request by Gaewyn+L+Knight · · Score: 1

      Umm... he wrote it so... um.... yeah that would be 'Fer' it :}

      --
      Telcos have alot of dark fibre in the States. Most people assume that's optical fibre...but it's actually moral fibre.
    10. Re:A request by shotfeel · · Score: 1

      For those of us who don't feel like wading a 100 page discussion transcript in legalese, can someone link to a concise summary of the changes being made?

      We're talking RMS here. I believe 100 pages is considered a concise summary.

    11. Re:A request by Anonymous Coward · · Score: 0

      It's an EXCELLENT joke.

      It should downright be modded insightful, because it's so true.

    12. Re:A request by Golias · · Score: 1

      Umm... he wrote it so... um....

      Another detail which ought to be in the summary, yes?

      --

      Information wants to be anthropomorphized.

    13. Re:A request by Jerry · · Score: 1

      FUDing again?

      How free is the BSD code when it is trapped inside a Microsoft or Apple's proprietary binary?

      Can you add their improvements to your original code and released the improved versin under the BSD? Of course not, and you know it.

      The biggest freedom the BSD license grants is the freedom of proprietary software houses to exploit the work of BSD coders without the necessity of returning anything back to the community except a restrictive EULA and an IP patent.

      I'll take the GPL any day, even v3.

      --

      Running with Linux for over 20 years!

    14. Re:A request by Phrogger · · Score: 1

      Actually, I call it the 3PL. :-)

    15. Re:A request by ichimunki · · Score: 1

      Uh, yes. And maybe we should point out that the sky is blue, as well... in case someone wanders in and is confused about this issue.

      --
      I do not have a signature
    16. Re:A request by AeroIllini · · Score: 2, Interesting

      To make it more compatable with similar licenses, there's a whole bunch of optional terms and conditions that can be added. For example, you can say "If you sue us for patent infringement, you can't use any patents our code relies upon that we own, effectively ending your ability to use our software." The notable feature is that this is an optional condition.

      Wait, what?

      Didn't RMS blow a gasket a few weeks ago, talking about how Creative Commons sucks eggs because it includes optional clauses?

      How is this different? Now, instead of GPLv3, we have GPLv3-with-patent-restrictions, and GPLv3-with-attribution, and GPLv3-with-different-disclaimer-of-liability, and...

      Either RMS likes customizing licensing, or he doesn't. He's being a hypocritical here.

      --
      For security, the MD5 hash of this message and sig is 09f911029d74e35bd84156c5635688c0.
    17. Re:A request by JazzCrazed · · Score: 1

      Haha, RMS and the FSF's doings are obviously not common knowledge, as much as I would like the contrary to be so.

    18. Re:A request by Golias · · Score: 1

      So you think everybody who reads slashdot has been keeping track of what Richard Stallman has been doing for the last few years?

      YMBNH.

      --

      Information wants to be anthropomorphized.

    19. Re:A request by JazzCrazed · · Score: 1

      I don't think it was just that multiple options existed that had him annoyed, but that certain of those options, if used, make the CC incompatible with the FSF's tenets. What I got from that interview was that he liked many parts of the CC, and disagreed with many parts as well, but because the multiple variations are being umbrella'ed underneath a single name, he can't safely suggest that people use CC as an alternative to the GPL. More a critique on semantics than anything else.

      Even in the quote that was put in your linked /. summary shows that it's a certain few of the options that are available - not simply that it can be customized - that make it contrary to his (and the FSF's) beliefs.

    20. Re:A request by ray-auch · · Score: 1


      1. A manufacturer who takes GPL'd code, signs it, and then sells hardware that only runs code signed with their key, which they don't redistribute, is in violation of the license. This is relatively narrowly defined, despite Torvalds throwing a hissy fit about this part of the license a few weeks ago, thinking it outlawed all forms of DRM (it doesn't.)


      Perhaps, for those who haven't read it, you could quote the clause which refers to "hardware", or "manufacturer" or that the software distributer also has to be the hardware manufacturer to have to release signing keys.

      Or maybe you can explain how you think it is "narrowly defined" in this way when the words "hardware" and "manufacturer" are not present anywhere in the (draft) license (a document you should perhaps read, or at least grep, before commenting on).

    21. Re:A request by squiggleslash · · Score: 1
      Rather than attack my summary without giving relevent reasons, perhaps you'd like to give an example of a situation that's outlawed by the license that my summary would have outrageously mislead people into thinking was valid.

      Summaries don't always include exactly the same wording as what they summarize, otherwise they wouldn't be summaries. Go boil your head.

      --
      You are not alone. This is not normal. None of this is normal.
    22. Re:A request by TheRaven64 · · Score: 1
      How free is the BSD code when it is trapped inside a Microsoft or Apple's proprietary binary?

      Exactly as free as it what when it was released. You can still download the original, modify it, and release it (or not). Just because Microsoft or Apple don't release their changes doesn't make the BSD code any less free.

      If software freedom is valuable to you, then the BSD-licensed version of the software will be more valuable to you than the closed version, even if the closed version has a few more features.

      If you believe that the Open Source development process is superior to closed development, then the BSD-licensed version will be technically superior as well as Free.

      If you believe that Free Software is not intrinsically valuable and that Open Source development is inferior to closed development, then the BSD license is not for you. Mind you, the GPL probably isn't either...

      --
      I am TheRaven on Soylent News
    23. Re:A request by ray-auch · · Score: 1

      I attacked your summary because it was misleading and gave the reasons why. You claimed that the clause was "narrowly defined" and that its effect was to ban a manufacturer that sells hardware and ships signed gpl software [...etc...]. Both statements may be accurate on their own, but taken together they are an entirely misleading, because the remit of the GPL clause is much wider than hardware mfr. that also ships software.

      Example:

          The drink drive laws are narrowly defined.
          It is illegal to drive after drinking ten pints of lager.

      Entirely correct statements, but totally misleading summary of the law (implies driving after five pints would be ok).

      For GPL examples, see for instance:

      http://yro.slashdot.org/comments.pl?sid=178766&cid =14817632

      (and parent / children).

      http://yro.slashdot.org/comments.pl?sid=178766&cid =14821945

      and probably numerous other comments on this topic.

    24. Re:A request by Jherek+Carnelian · · Score: 1

      Didn't RMS blow a gasket a few weeks ago, talking about how Creative Commons sucks eggs because it includes optional clauses?

      No he did not.

      His complaint had nothing to do with "optional clauses."
      It was all about entirely different licenses being grouped under a single name.

    25. Re:A request by zobier · · Score: 1
      Actually, I call it the 3PL. :-)
      That sounds like thripple, I'm not sure that has the best association.
      --
      Me lost me cookie at the disco.
    26. Re:A request by Anonymous Coward · · Score: 0

      Who the FUCK do you think wrote GPL3? Bill Gates? For the umpteenth time, someone proved that idiocy and a low UID are not mutually exclusive. Thank you!

    27. Re:A request by Golias · · Score: 1

      Who the FUCK do you think wrote GPL3?

      Could be anybody, for all I would know. I tend to prefer the BSD license anyway. Most (not all) people know that Stallman came up with the first one. That doesn't mean that everybody knows he's still the one maintaining it. Were I writing the summary, I probably would have bothered to include that info. It's just good journalism.

      --

      Information wants to be anthropomorphized.

    28. Re:A request by ichimunki · · Score: 1

      Were I writing the summary, I probably would have bothered to include that info. It's just good journalism.

      Who must be new here? You want good journalism, this ain't the place to find it. For my money, if you aren't paying enough attention to the FSF/GPL3/Stallman to know the background here, I don't think the summary should have to explain this all to you in detail. That's why you should RTFA.

      --
      I do not have a signature
    29. Re:A request by jZnat · · Score: 1

      How about calling it the FOK? Oh wait, that seems kinda dirty...

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
  2. RMS Interruptions by merc · · Score: 1

    O'Riordan previously made a transcript of the January 16th first presentation on the GPLv3 which consists of 70 minutes of Eben Moglen, with 20 minutes worth of interruptions from Stallman.

    Is that meant to sound like a bad thing? I hope not, if you're touching the GPL, I'd hope it's progenitor would interrupt you if you make a potential error ;-)

    --
    It's true no man is an island, but if you take a bunch of dead guys and tie 'em together, they make a good raft.
    1. Re:RMS Interruptions by Anonymous Coward · · Score: 0

      Yes, but 17 of those 20 minutes were Stallman shouting "GNU/Linux" after every mention of Linux.

    2. Re:RMS Interruptions by Anonymous Coward · · Score: 0

      Yes, but 17 of those 20 minutes were Stallman shouting "GNU/Linux" after every mention of Linux.

      You mean: ...after every mention of GNU/Linux.

    3. Re:RMS Interruptions by Anonymous Coward · · Score: 0

      I think he meant GNU/Stallman.

    4. Re:RMS Interruptions by Anonymous Coward · · Score: 0

      GNU/I GNU/think GNU/he GNU/meant GNU/GNU/Stallman

  3. RMS likes to talk doesn't he. by jellomizer · · Score: 1

    Is it just me or does it seem like RMS created a new verion of the GPL because people stopped listening to him about the old one.
    It seems to me that RMS views are no longer connected with where Open Source should go, and will just lead Open Source to be too socially libral for wide use.

    I disagree with RMS so my Mod points will negitivly reflect it.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:RMS likes to talk doesn't he. by Anonymous Coward · · Score: 0

      It's just you.

    2. Re:RMS likes to talk doesn't he. by timster · · Score: 2

      I'm sorry, but saying that RMS is no longer connected with Open Source is like saying that Hillary Clinton is no longer a Republican.

      --
      I have seen the future, and it is inconvenient.
    3. Re:RMS likes to talk doesn't he. by Tweekster · · Score: 1

      but why is your opinion of where OSS should go (i dont know how it "can go" anywhere but that is besides the point) is anymore valid than RMS.... he has done a lot, people will listen to his opinions, you are a poster on a forum, why would anyone take your opinions at face value when you havent backed them up

      --
      The phrase "more better" is acceptable English. suck it grammar Nazis
    4. Re:RMS likes to talk doesn't he. by Dunbal · · Score: 1

      but why is your opinion of where OSS should go ... anymore valid than RMS....

            Surely the only valid opinion is that of the Flying Spaghetti Monster, which is why you must pray to Him every day.

      --
      Seven puppies were harmed during the making of this post.
    5. Re:RMS likes to talk doesn't he. by jellomizer · · Score: 1

      It isn't nessarly. But with the blind followers of RMS really scare me. I feel RMS is a force of lack of compramize which will lead to more problems in the future. But it feels like he Jams every one of his views in the GNU license, which makes it more and more inflexible. I tend to follow the notion that it is up to the developer to decide what license to use. And using Licenses like the GPL, BSD, LGPL, etc... are tools like choosing a library. It saves you time in writting a good legal license agreement. RMS stance GPL or Nothing and all the people who follow him on that really scare me.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:RMS likes to talk doesn't he. by Penguinoflight · · Score: 1

      RMS is still pushing forward, and there are a lot of people who are happy with the state of open source now. The thing is, with the competition (from a legal standpoint) of DRM, trusted computing, and etc, the GPL must make changes to counter these new ideas.

      Some people are afraid that the changes in gpl3 will keep people from embracing open source, but it is essential to have a licence that will be of use in the years to come.

      RMS has liberal views, but at this point he's the only one addressing the problem. Btw... RMS isn't that popular around here, you're more likely to get modded down for incorrect spelling.

      --
      "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
      1 John 4:14
    7. Re:RMS likes to talk doesn't he. by srmq · · Score: 1

      Yes, it is just you. Others prefer to read the rationale of the changes before saying nonsense.

    8. Re:RMS likes to talk doesn't he. by bwthomas · · Score: 1

      ... by which he means to say (i believe) that Richard Stallman, founder of the Free Software Foundation and author of the GPL, was never connected to "Open Source" by anything but the licenses he has authored. Those who lump open source and free software together and then comment on the idealogy as though it's one homogenous crowd are making a logical error.

      references:

      open source: http://en.wikipedia.org/wiki/Open_source_software
      free software: http://en.wikipedia.org/wiki/Free_software

    9. Re:RMS likes to talk doesn't he. by Short+Circuit · · Score: 1

      Translation: RMS believes in Free Software. ESR believes in Open Source.

    10. Re:RMS likes to talk doesn't he. by JohnFluxx · · Score: 1, Redundant

      Wait you're complaning that his license reflects his views?!?! SHOCK HORROR!

      You whole post is nonsense.

      * You don't like blind followers of X (well who says they do like blind followers of anything?)
      * RMS lacks compramize(sic) - So he sticks to his principles.
      * He puts his views in his license... duh
      * "I tend to follow the notion that it is up to the developer to decide which license to use" - duh again - who said that we should force someone who writes new code to chose a particular license?

      Did you make a single useful point at all?

    11. Re:RMS likes to talk doesn't he. by bwthomas · · Score: 1

      keep in mind that the GPL really is just a template and that you can add or subtract clauses as you like. Many software packages do this, yielding licenses that are GPL compatible but either allow more permissive use or restrict certain uses.

      The GPL is not, and never has been, a boilerplate that you must either accept or reject.

    12. Re:RMS likes to talk doesn't he. by stinerman · · Score: 1

      Well, first RMS was never associated with "Open Source", but "Free Software" (which, as I'm sure you know, have different aims, but similar outcomes).

      As far as GPL v3 being too socially liberal, if people do not like the license they will not use it. Furthermore, most people can still use GPL v2. Its not like RMS will somehow revoke the GPL v2 license. There is nothing to stop you from releasing the Jellomizer Public License and creating terms exactly as you'd want them. Many people might not like your terms, many might, but simply releasing a new license won't do anything to the adoption of free/open source software.

    13. Re:RMS likes to talk doesn't he. by crawling_chaos · · Score: 1

      Classically, liberals have great respect for property rights. I think it would be far more accurate to describe RMS' positions as socialist or communitarian, with a fair amout of anarchism thrown in. Not that that makes his views necessarily wrong, it only describes them more accurately.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    14. Re:RMS likes to talk doesn't he. by caffeination · · Score: 1

      I'll say. RMS zealotry is the main thing that I hate about Linux (which I use exclusively, for what it's worth). Every time he makes a noise, I go and check up on FreeBSD's hardware compatibility.
      The GPL is lame in my opinion too. If it's open source, why should it limit how one can use that source? Such a thing seems as unrealistic to me as the proprietary lock-in method, or trying to Manage peoples' Digital Rights.

    15. Re:RMS likes to talk doesn't he. by Jacek+Poplawski · · Score: 1

      I'm sorry, but saying that RMS is no longer connected with Open Source is like saying

      He never was. He was always against it. RMS is connected to Free Software, not to Open Source.

    16. Re:RMS likes to talk doesn't he. by Anonymous Coward · · Score: 0

      How dare you spread such slander. RMS has been the center of progress for OSS since the beginning. We are not "socially libral" in our ways and Stallman our leader, with faith in the people, inspired us to build up the FSM that we love.

    17. Re:RMS likes to talk doesn't he. by smittyoneeach · · Score: 1
      The thing is, with the competition (from a legal standpoint) of DRM, trusted computing, and etc, the GPL must make changes to counter these new ideas.
      Some people are afraid that the changes in gpl3 will keep people from embracing open source, but it is essential to have a licence that will be of use in the years to come.
      RMS has liberal views, but at this point he's the only one addressing the problem.
      True. Binary drivers are a huge problem, as well, most acutely in the wireless and video subsystems. Ultimately, software is better when it's like chess, rather than poker.
      GPL3 is relatively unrevolutionary WRT GPL2. http://lwn.net/ has good coverage. GPL3 pretty much refines 2.
      I don't see why one would have to be liberal to agree with the GPL itself. I've always thought of it as essentially saying that software knowledge is like academic knowledge. Then there is the point where we step off the paper and into an ideology, asserting that
      !GPL == unethical
      Now we've crossed the political Rubicon, so to speak.
      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    18. Re:RMS likes to talk doesn't he. by pinky0x51 · · Score: 1
      >Classically, liberals have great respect for property rights.

      As far as i know RMS, i would say that he has a great respect for property rights too. But software like music, novels, etc. aren't property! They are works for which society gives in some cases some monopoly rights (copyright, patent law, trademark,..). But society should hand out this monopoly rights only as long as it gain an advantage for everyone (author and society as a whole). This was given at the beginning of copyright. Today copyright is extremely overplayed. It harms the society more than it offers advantages and it harms most artist and authors too. Today there is no balance at all, it harms the majority for the advantage of few (mostly publishers).

      At the beginning of copyright the society had good arguments to give away these exclusive rights, it was a win for everyone. Today society would have good arguments to reorganize this exclusive rights, but the few which still profit from this rights at the expense of the rest of the society have too much power.

      This has absolutely nothing to do with property rights.

      --
      Support Free Software! Join FSFE's Fellowship: http://fellowship.fsfe.org
    19. Re:RMS likes to talk doesn't he. by rpdillon · · Score: 1

      I wouldn't describe myself as a blind RMS follower (who would?), though I do agree with him.

      I see where you're coming from with respect to the GPL (many people express the idea you mentioned by saying the GPL is "viral"). I understand this, and don't think the GPL is always appropriate.

      However, if the developer's goal is to ensure that his or her software will always be available to the public in a human readable form (i.e. source code), then the GPL is what you're looking for. This can be useful in several scenarios:

      1) You release MythTV (or the Linux kernel). Someone else modifies it, puts in spyware, and re-releases it with a modicum of new features to entice people to download, saying things like "Based on MythTV!" or "Based on Linux!". You now have a problem, since a product that is largely your code is now on the market, but it's users cannot verify that it isn't doing "evil" things.

      2) You establish a community of companies that are providing competing products. They decide on certain core functionality that has become a commodity, but other features are the differentiators in the market. They choose to GPL the commodity code, reserving their seperate "feature rich" code internally. This forces changes made to the commodity code to be released back into the community pool by the members of the group. If they do not, then there are actual possible legal ramifications. With other licenses (MIT, BSD) this would not be the case.

      3) You wish your program to have a chance for growth even in your absence. With GPL'd code, projects' maintainers can come and go, but the project is free for any motivated person to pick up and work with. This is useful for the project, since it ensures that even dead projects can be resurrected if they are deemed useful, but it is also useful for younger developers, since it provides them with vast bodies of source code to learn from. Other licenses may offer source code, but none guarantee it in the absence of the code's original author the way the GPL does.

      This last is a difficult point for me to express, but I'm essentially trying to say that if the original author goes bankrupt (for example) and stops maintaining the code, there could occur a case where all surviving developers of that code simply don't wish to have their code be seen by others (these would be the authors of "derivative works"). In this case, the source would effectively be lost to the community.

      All that said, I think there is a place for both MIT/BSD licenses as well as the GPL (as well as, (gasp), proprietary software, on occasion!) I recognize RMS as the zealot he is, but I also believe in a lot of what he believes. Mostly, I believe that the owners of the computers (the users of the code!) should have the option to control their computers and modify the code that runs on them if they choose. This option is only ever made available through a license like the GPL.

    20. Re:RMS likes to talk doesn't he. by Knuckles · · Score: 1
      the GPL really is just a template and that you can add or subtract clauses as you like

      This would be an incredibly stupid practice since it would create an inpenetrabel jungle of licenses. There are so many FOSS licenses already that it's hard to imagine that someone needs something that hasn't been done before or can't be done by licensing under more than one license simultaneously. Fortunately nearly noone actually does this.

      Many software packages do this, yielding licenses that are GPL compatible but either allow more permissive use or restrict certain uses

      They surely can not create licenses that are "GPL compatible but ... restrict certain uses" that way. From GPL, Terms and Conditions, point 6,
      You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
      Therefore combining code under GPL and code under GPL-derived but more restrictive licenses would violate the GPL.
      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    21. Re:RMS likes to talk doesn't he. by samkass · · Score: 1

      In the same sense, it's much like saying that RMS is no longer connected with reality.

      Is something to the effect of "If you use my software, you have to prepend GNU/ to the name of your product" in the license yet?

      --
      E pluribus unum
    22. Re:RMS likes to talk doesn't he. by MarkJenkins · · Score: 1

      If it's open source, why should it limit how one can use that source?

      There are very good reasons. We don't just care about your freedoms, we care about the freedom of every subsequent person who gets a copy.

      Why would you like the power to give another person a copy, but with less freedom and power then you received? Are they less important? Are they less deserving of freedom?

    23. Re:RMS likes to talk doesn't he. by aurelian · · Score: 1
      If it's open source, why should it limit how one can use that source?

      Congratulations: you've identified one of the reasons why 'open source' is not necessarily the same as 'free' - which is what RMS advocates.

    24. Re:RMS likes to talk doesn't he. by vertinox · · Score: 1

      Is it just me or does it seem like RMS created a new verion of the GPL because people stopped listening to him about the old one.

      I don't think so. I'm a more BSD fan than anyone else, but I can see where he is coming from. He is simply trying to make it so GPL can't be used to restrict the rights of others.

      People don't have to use it if they don't want to for things they want to write from scratch, but he is giving the option for authors who want to use a GPL license but don't want their works to be used down the line by someone else for DRM and other freedom restricting type of software.

      No one has to change over to GPL3 if they don't want to. So either do or don't. No need to complain.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    25. Re:RMS likes to talk doesn't he. by Dionysus · · Score: 1

      2) You establish a community of companies that are providing competing products. They decide on certain core functionality that has become a commodity, but other features are the differentiators in the market. They choose to GPL the commodity code, reserving their seperate "feature rich" code internally. This forces changes made to the commodity code to be released back into the community pool by the members of the group. If they do not, then there are actual possible legal ramifications.

      When you GPL your "commodity" code, then all your "feature rich" code also become GPL if you link it in.

      Which is why I personally prefer the Mozilla/Apache license (keep the commodity free, do whatever you want with the linked in libraries). Of course, RMS doesn't believe you as the developer should have a say in what license you choose.

      --
      Je ne parle pas francais.
    26. Re:RMS likes to talk doesn't he. by crawling_chaos · · Score: 1

      Property is what we define it to be. While my definition is much closer to your (and RMS') than to the RIAA's, classic liberals were amongst the biggest proponents of the ideas of copyright and patents, which is where the entire idea of "intellectual property" flows from. One notable exception was Thomas Jefferson, but I have trouble calling a slave-holding rapist a true "liberal."

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    27. Re:RMS likes to talk doesn't he. by Znork · · Score: 1

      Copyrights arent property rights. They are state protected monopoly rights and are in their essense incompatible with a liberal market view. Calling it 'intellectual property' is simply a misnomer intented to cause exactly the kind of confusion you've fallen victim to.

      Intellectual monopoly rights restrict what the owner of a piece of property is allowed to do with that property. The GPL essentially restores those rights to the owner of any copy, and prevents further re-restriction. That fundamentally supports the essense of the free market and competition, and cannot be described as either socialist or communitarian except in their broadest egalitarian aspect.

    28. Re:RMS likes to talk doesn't he. by Skreems · · Score: 1

      That's what the LGPL is for... Conversely, if the common code is a web service, an application hooked into your own through pipes, or something else less tightly coupled than a binary library, the GPL will work just fine.

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    29. Re:RMS likes to talk doesn't he. by codehead78 · · Score: 3, Interesting

      No, RMS does not force anyone to use GPL. But he has tried to leverage someone else's more successful project to give the GPL3 more steam. Linus didn't like it, so RMS tried to subvert his control by saying Linus can't make other Linux developers not use the GPL3.

      But no, he doesn't force anyone.

    30. Re:RMS likes to talk doesn't he. by J.R.+Random · · Score: 1

      After you have written a free program as big and useful as GNU Emacs (to name just one of RMS's contributions) I think more people will pay attention to your ideas of where "open source" should go.

      Stallman has always been concerned about the social and ethical issues of software distribution, market share has never been a significant concern of his. If in five years you want to be using an "open source" OS that in fact has been totally locked down with DRM, then go ahead and follow the "pragmatic" open source route. GNU software will always remain free, as in speech.

    31. Re:RMS likes to talk doesn't he. by JohnFluxx · · Score: 1

      I'm not particularly impressed. Your best example of RMS trying to force people is when he asked Linus to consider GPL3 ?
      Even if he was heavy handed and rude in the way he did it, all you are showing is that he's lacks any grace. He's still not forcing anyway. And btw, Linus lacks grace as well. It's a trait of being geek I think :)

    32. Re:RMS likes to talk doesn't he. by bitspotter · · Score: 1

      "It seems to me that RMS views are no longer connected with where Open Source should go..."

      And where, pray tell, is that? Last time I checked, freedom meant letting people make their own decisions about where to go. By that estimation, "where OS should go" isn't one direction - it's the myriad directions that individuals resolve to go, given their freedom.

      I don't know what you've been reading, but I sure do see a lot of people (eg, Slashdot, and... well YOU) listening to what RMS has to say. How that qualifies as 'no longer connected' I'm not sure.

    33. Re:RMS likes to talk doesn't he. by caffeination · · Score: 1

      This reply goes to everyone who replied to my other post, not just the parent:
      Thanks for your replies. I'd really lost touch with the Free Software movement. I think I'll do my best to ignore RMS from now on (until fairly recently, as in until GPLv3, I could defend free software to the death. It's very nice to be back.)
      I think this little episode has been the effect of traces of zealot in me dying.

    34. Re:RMS likes to talk doesn't he. by Arandir · · Score: 1

      RMS is connected to Free Software, not to Open Source.

      But yet there is not practical difference between the two. It's like trying to point out the differences between the People's Liberation Front of Judea and the Judean People's Liberation Front. None.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    35. Re:RMS likes to talk doesn't he. by irenaeous · · Score: 1

      No. There is a difference, albeit not very great to non-partisan onlookers. Check out gnu.orgs explanation here.

      They also examine some licenses here, some of which are listed as Open Source on opensource.org.

      When I read Linus's criticism's of the DRM issues in V.3, I was inclined to agree with him. I have found him to be reasonable and non-partisan in the past while RMS has always come accross as highly ideological. Ironically, having read TFA, I find RMS's explanations to be enlightening, and believe that Linus has not represented what V.3 is trying to do. I suspect that Linus has been polarized abit due to conflicts with RMS on these issues, causing him to be perhaps a little bit less reasonable and more partisan than is normal for him.

    36. Re:RMS likes to talk doesn't he. by Arandir · · Score: 1

      When you look at the list of licenses they don't approve, you'll see that it's very subjective. The Free Software Definition is wholly irrelevant to whether they consider a license to be Free Software. Rather it is based on a subjective review by RMS. The very first license the FSF excludes from the "Free" category is the original Artistic license, with the reason cited is: "it is too vague". Huh? In short, a license is "Free" if it has the RMS imprimatur and seal of approval. Nothing less.

      That's the real difference between the two: Open Source has objective criteria, Free Software does not. But the actual concepts and ideas behind the two remain identical. These aren't political parties where you must pick one and actively disparage and insult the other.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    37. Re:RMS likes to talk doesn't he. by Anonymous Coward · · Score: 0

      umm, considering that the gpl is the most widely used open source license, i'd think a lot of people were listening to him.

    38. Re:RMS likes to talk doesn't he. by Anonymous Coward · · Score: 0

      Linux is a very nice kernel, you don't need to put GNU/ in front of it. The "Linux" operating system is a different matter.

    39. Re:RMS likes to talk doesn't he. by dbIII · · Score: 1
      I'll say. RMS zealotry is the main thing that I hate about Linux
      RMS didn't write linux, and had far less involvement it the tools used top write linux than most people think.

      He didn't even write emacs, he "invented" it - others wrote a program to act the same way as his macros used in an earlier text editor. He did a lot of good things, like the GPL, early versions of gcc and starting off the hurd - but he has never had much to do with linux apart from the silly LiGnuX renaming thing and the current gnu prefix idea.

    40. Re:RMS likes to talk doesn't he. by dbIII · · Score: 1
      After you have written a free program as big and useful as GNU Emacs
      Look at the history of emacs and you'll see who the authors were. Look at the story about the fork and you'll see that RMS was not the developer of it on either branch even then - he just told someone else to work on a fork of it when he disliked features that would not help the hurd (eg. X windows support). He's done a lot of good things (early versions of gcc and a pile of other applications), but apart from the original text macros in another text editor other people have been the emacs developers. One very good point in RMS's favour is that he stuck to the GPL and didn't try to close down the other branch of emacs, he just grumbled a lot.
    41. Re:RMS likes to talk doesn't he. by byolinux · · Score: 1

      The GNU/ isn't prefix.. it's the name of another thing.

      When you run the Linux kernel, you're typically running the GNU operating system with it. GNU and Linux. GNU with Linux. GNU plus Linux... It's not 'GNU' or 'Linux' or 'GNU Linux' :)

    42. Re:RMS likes to talk doesn't he. by caffeination · · Score: 1

      No no, I don't mean I hate the zealotry code that pops up an anti-Microsoft statement on my shell every 10 seconds, written by RMS. I meant I hate being associated with him just because he has a loud voice and has a knack for providing useful soundbites to journalists.
      The only front man I'd be happy with is Linus, and obviously we don't want him taken away from the kernel. So we're left with something like a power vacuum, and RMS is a nice plump shape to plug such a hole.
      Anyway, see my other reply in this thread. You are will must to be like it.

    43. Re:RMS likes to talk doesn't he. by Thanatopsis · · Score: 1

      "Property is what we define it to be."

      Nope. Property has a strict legal definition. "intellectual property" covers a wide variety of rights and monopolies among them trademark, copyright and patents. Using the term intellectual property is inaccurate at best.

      Nice ad homimen attack on Jeffersion though. It's also absolutely meaningless. Calling Jefferson a rapist because he had sex with his slaves is a cheap shot because you simply don't know. As far as oening slaves, it was pretty common practice among the founding fathers. Perhaps when you write a document as important as the Declaration of Independence, I will take you more seriously.

    44. Re:RMS likes to talk doesn't he. by irenaeous · · Score: 1

      RMS has four philosophical criteria in his definition of free software:

      1. The freedom to run the program, for any purpose (freedom 0).
      2. The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
      3. The freedom to redistribute copies so you can help your neighbor (freedom 2).
      4. The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.

      See The Free Software Definition

      OSI has a more specified, practical, but less philosophical definition that may be found here.

      The chief difference appears to me to be in RMS's "freedom 0". An Open Source license can impose some restrictions on the end user, limited restrictions to be sure, but some restrictions. It may not be a simple matter to apply RMS's criteria -- his definition is not as specific as the OSI one, but it is not purely subjective based on RMS's whim. That in turn means that there is a difference, and the terms are not identical.

      Given, that -- if you read the gnu materials -- RMS is not disparaging to Open Source. He says quite clearly, "... the differences in extension of the category are small: nearly all free software is open source, and nearly all open source software is free."

    45. Re:RMS likes to talk doesn't he. by civilizedINTENSITY · · Score: 1

      I don't think you can fairly say "more successful" project. Linus made an engine, and RMS made a steering system, braking system, signaling system, suspension, etc...

      While it is true that all cars have an engine, all cars better have brakes and steering, too. Linux was never meant to be more than a kernel, whereas the GNU Operating System is an operating system that uses the Linux kernel. Thus, "GNU/Linux". It makes sense.

    46. Re:RMS likes to talk doesn't he. by civilizedINTENSITY · · Score: 1
      I believe you can allow more permissive uses, for the granting of user permissions is what this is all about, but I don't think you can add restrictions so easily, as terms are limited to the kinds of additional requirements. There are limits.
      "When you release a work based on the Program, you may include your own terms covering added parts for which you have, or can give, appropriate copyright permission, as long as those terms clearly permit all the activities that this License permits, or permit usage or relicensing under this License."

      specificly, there is a list of A-E types of terms that are acceptable, including:

      b) "They may state a disclaimer of warranty and liability in terms different from those used in this License."

      c) "prohibit or limit the use for publicity purposes of specified names of contributors, and they may require that certain specified trademarks be used for publicity purposes only in the ways that are fair use under trademark law except with express permission."

      "that the work contain functioning facilities that allow users to immediately obtain copies of its Complete Corresponding Source Code."

    47. Re:RMS likes to talk doesn't he. by NutscrapeSucks · · Score: 1

      They are state protected monopoly rights and are in their essense incompatible with a liberal market view.

      As if Real Estate, corporate securities, or many other forms of property were any different.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    48. Re:RMS likes to talk doesn't he. by jbn-o · · Score: 1

      Of course, RMS doesn't believe you as the developer should have a say in what license you choose.

      Where do you get that idea? The essay "Freedom or Power?" would suggest otherwise, particularly when Stallman and Kuhn acknowledge that copyright holders have the power to choose whatever license they wish. Developers writing derivative works can choose what code they want to base their work on. Thus, it seems to me that developers certainly have a say in what license they choose, whether choosing a license for their own copyrighted work or in making a derivative work.

    49. Re:RMS likes to talk doesn't he. by crawling_chaos · · Score: 1

      Property is what we define it (in the law) to be. Jefferson thought so, which is why he was able to hold blacks in bondage. For all his writings, and yes I do know the draft of the Declaration included the establishment of chattel slavery in America as one of the Throne's crimes, his feet didn't walk the talk.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
  4. More info at gplv3.fsf.org by H4x0r+Jim+Duggan · · Score: 4, Informative

    These transcripts, and other such documents, are collected at the official GPLv3 wiki, on the Reusable texts page. And there's more info about the draft and how to participate in the public consultation at gplv3.fsf.org.

    1. Re:More info at gplv3.fsf.org by mugnyte · · Score: 1


      Summaries of the transcripts, including explanations of the terms and the implications of the ideas, are for sale fo me. This is in accordance with terms of the old and new GPL, although I offer no indemnity against a SCO subpoena. Sorry! ;)

    2. Re:More info at gplv3.fsf.org by Breakfast+Pants · · Score: 1

      Right now the draft's webservices portion is effectively useless. You can wrap your GPLed webservice with another webservice which passes every function call except the one which requests the source. If they fix it by being even more strict, they could easily requiring exposure to DDoS attacks.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    3. Re:More info at gplv3.fsf.org by replicant108 · · Score: 1

      For UK and Irish readers, it's probably worth pointing out that RMS will be discussing the GPLv3 (among other things) at the Foss Means Business conference in Belfast on 16th March.

      Bruce Perens will be there too. It should be an interesting day, I think.

      http://www.foss-means-business.org/

  5. Man-in-the-Middle Signature Attacks against GPL v3 by morgan_greywolf · · Score: 3, Interesting

    What about Man-in-the-Middle attacks? That is, MonopolySoft builds a machine that will only run binaries signed by Red Hat. Red Hat is not required under GPLv3 to give its signature key, but the machine maker is, except, he's decided to verify only against Red Hat's key and he doesn't have Red Hat's private key (just the public key, which is used to validate that the binary came from Red Hat, which is all he needs). So I can still be prevented from modifying my GPL software and running it on my box, right? And no one's violated GPLv3, right? GPLv3 doesn't cover this type of attack at all.

  6. Re:Man-in-the-Middle Signature Attacks against GPL by Bromskloss · · Score: 1

    What about Man-in-the-Middle attacks? That is, MonopolySoft builds a machine that will only run binaries signed by Red Hat. Red Hat is not required under GPLv3 to give its signature key, but the machine maker is, except, he's decided to verify only against Red Hat's key and he doesn't have Red Hat's private key (just the public key, which is used to validate that the binary came from Red Hat, which is all he needs). So I can still be prevented from modifying my GPL software and running it on my box, right? And no one's violated GPLv3, right? GPLv3 doesn't cover this type of attack at all.

    Come again please?

    --
    Swedish plasma phys. PhD student; MSc EE; knows maths, programming, electronics; finance interest; seeks opportunities
  7. On eating chalk by doomy · · Score: 2, Funny

    Richard Stallman: By the way, I don't think we were using any chalk. We were using computers to write things down.

    Eben Moglen: Yes, I was using the chalk after you went home at night. Sometimes I had ...chew it.

    Richard Stallman: Did you eat it?

    Eben Moglen: You see how it is. There was chalk involved, he just wasn't around for it. Yeh, it was curing my indigestion actually.

    --
    ...free your source and the rest would follow...
    1. Re:On eating chalk by AKAImBatman · · Score: 1

      I was convinced that this had to be a joke. But here it is. Go figure.

  8. Come on, man by stinerman · · Score: 1

    I like RMS, his ideas, and his work on GNU, but when he starts spouting off about "Treacherous Computing" and "Digital Restrictions Management" instead of using the traditonally accepted names (trusted computing and digital rights management, respectively), he just marginalizes himself and his positions.

    Yes, I agree that TP and DRM are more apropriately called what Stallman calls them, but your average Joe who wants to learn more about FOSS, GNU, etc. hears this and thinks the guy is just some conspiracy loon. Its the same thing with the "there is no such thing as IP" deal. We understand the phrase "intellectual property" is a far from perfect term to describe what it represents. Going off on some tirade about how IP is an imperfect term doesn't answer the questions that people will have about how the changes in copyright law and software patents impact them and their rights. It only seeks to alienate people.

    1. Re:Come on, man by ArghBlarg · · Score: 1

      But he who controls the terms of discussion, often controls the discussion. RMS is using his alternative acronym expansions to de-construct the euphemisms the big media cartels are planting in everyone's minds.

      Just like how the government wants to call anyone who's a dissident 'unpatriotic', etc. Think about it.

      --
      ERROR 144 - REBOOT ?
    2. Re:Come on, man by aug24 · · Score: 2, Insightful
      Fuck that - why should the bad guys (biased statement, I know) get to name things?

      Why should any of us accept the phrase "Trusted Computing"? It's intended to be doublespeak, we should applaud RMS him for pointing it out.

      J.

      --
      You're only jealous cos the little penguins are talking to me.
    3. Re:Come on, man by stinerman · · Score: 1

      Yeah, I know why he's doing it. I just think he should be a bit more diplomatic about it. Something along the lines of "I don't like X, which I like to call Y, because what it really is about is ..." would be fine.

    4. Re:Come on, man by VP · · Score: 1

      As others are pointing out, George Orwell made it very clear in "1984" how the power of language can be misused to exercise control over the minds of the population. It is important to call things with their real names, so that there is no doubt about the purpose of DRM and TP.

    5. Re:Come on, man by Fezzick · · Score: 1

      The terms "Trusted Computing" and "Digital Rights Management" were coined by the MPAA/RIAA and their agents specifically to be misleading and to put a positive spin on generally consumer unfriendly technologies. It's been proven time and time again that the masses can easily be persuaded by such propaganda. By using the terms "Treacherous Computing" and "Digital Restrictions Management", he shines light on what the big content industry is attempting to do in an effort to counter what threatens his (and many others) core beliefs.

    6. Re:Come on, man by RazzleDazzle · · Score: 1

      Amen.

      Raise your hand if you think the USA PATRIOT ACT is patriotic (for those that live in the USA). I sure don't think it is. Controlling language comes close to controlling individuals. Just look at religion. With out incessant repitition of what is "truth" since childhood most people would never have bought into almost any religion. Yes, there are exceptions to every rule of course. As it applies to this, well if you give something a nice and good and SAFE sounding name and only talk about all of the wonderful things it will bring, then anyone who actually analyzes your "something" and finds and wants to address the flaws or cons can is labeled evil, or a social enemny, or a loon, or a conspiracy nut, etc. Why is that person bashing the PATRIOT ACT?!?! They must be UNpatriotic!!!

      So I agree on the principle that continuing to misguide people by using their given names of disguise is wrong. Maybe we should not even have special names for laws and they should all just be called Statute XYZ or generic names/terms that will help prevent bias from an uninformed people.

      --
      ZERO ZERO ONE ZERO ONE ZERO ONE ONE! Just brushing up for my next big invention: Ethernet over Voice (EoV)
    7. Re:Come on, man by GigsVT · · Score: 1

      Diplomacy??

      The media/software companies don't say "Preventing end-users from using the files they have in the way they want, which we like to call Digital Rights Management...."

      If they are going to throw around buzzwords, you can't call Stallman out for doing the same thing.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    8. Re:Come on, man by geekee · · Score: 1

      "As others are pointing out, George Orwell made it very clear in "1984" how the power of language can be misused to exercise control over the minds of the population. It is important to call things with their real names, so that there is no doubt about the purpose of DRM and TP."

      Yes, Like RMS calling his software "free software". If it's free software, why are there all the restrictions?

      --
      Vote for Pedro
    9. Re:Come on, man by J.R.+Random · · Score: 1

      Weird. You agree with RMS that "Treacherous Computing" and "Digital Restrictions Management" are more accurate terms than market-speak like "[You're not] Trusted Computing" and "[You have no] Digital Rights Managament". But then you object to RMS using these more accurate terms.

    10. Re:Come on, man by Just+Some+Guy · · Score: 1
      Yes, I agree that TP and DRM are more apropriately called what Stallman calls them

      Then use them. Let them be the first definitions that people ever hear, so that when they hear the *AA-coined versions they'll recognize them as doublespeak.

      --
      Dewey, what part of this looks like authorities should be involved?
    11. Re:Come on, man by ArsonSmith · · Score: 1

      They call this a free contry yet I am not allowed to run around killing people. If it's a free contry why am I not free to restrict others freedom?

      The restrictions on free software are there to keep it free.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    12. Re:Come on, man by Anonymous Coward · · Score: 0

      I see where he's coming from. After all, the Patriot Act is more properly called the Bend Over and Take It Act. At least he keeps the same initials.

    13. Re:Come on, man by Arandir · · Score: 1

      Stallman is a far left liberal. Like other far left liberals, he cannot stop himself from renaming things. For example, if you read his blog, you'll see that he cannot say the words "President Bush", but has to say "The Shrub", or "the unelected president", or something like that. He thinks he is being clever, but he ends up looking at stupid as the comment crowd at Democrat Underground.

      If you don't like the names, prefix them with "so-called", or something like that, so that you distance yourself from them. Say "so-called 'Trusted Computing'" instead. Say "so-called 'Digital Rights Management'" instead. Don't use snarky sarcasm, as that only makes you look petty.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    14. Re:Come on, man by westlake · · Score: 1
      But he who controls the terms of discussion, often controls the discussion.

      The problem is, the Geek isn't in control. In the larger world, I have yet to see coinages like "copyleft" and "treacherous computing" gain any traction whatever.

    15. Re:Come on, man by dbIII · · Score: 1
      he just marginalizes himself and his positions
      He's always been there - for instance his opinion that we shouldn't have to use any sort of authentication to use computers, go to conferences etc. I disagree with him and use passwords on computers, but agree with him that a good licence such as the GPL is a good thing, but once again disagree that there can be no licence but his. Listen to him once on each issue (not worth hearing the repeats), consider what he says, and then decide what you think. We don't need a hero to follow blindly.
    16. Re:Come on, man by geekee · · Score: 1

      "They call this a free contry yet I am not allowed to run around killing people. If it's a free contry why am I not free to restrict others freedom?

      If it's free software, why is RMS restricting my freedom to do with it as I please? In a free country you are not allowed to arbitrarily restrict someone's freedom (as killing does). If the software is free, then that implies there are no restrictions. This is not the case for GPLed software. It is the case for public domain software such as BSD.

      --
      Vote for Pedro
    17. Re:Come on, man by Thanatopsis · · Score: 1

      No offense but I read Stallman's Blog and I haven't seen a single reference to the President or call him a "Shrub" so I call Bullshit on you.

    18. Re:Come on, man by Arandir · · Score: 1

      That's his FSF blog, dealing only with FSF and GNU related activities. Go to his homepage instead, and see what kind of person he is outside of the software realm.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    19. Re:Come on, man by ArsonSmith · · Score: 1

      Because if he was worried about what you do with the software it would be called free developers, and not free software. RMS couldn't care less about your freedom, he is worried about the software.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    20. Re:Come on, man by SwashbucklingCowboy · · Score: 1
      > he just marginalizes himself and his positions

      I understand what you're saying, and you should be correct... BUT look at what Republicans have accomplished by doing things like recasting the estate tax as the death tax and I gotta wonder if it's a bad thing for him to do.

  9. Re:Man-in-the-Middle Signature Attacks against GPL by Qzukk · · Score: 2, Insightful

    Then you don't buy MonopolySoft's machine.

    If it is not possible for other machines that run Red Hat code to exist, then it's clear that Red Hat is designing the code for a specific architecture that requires signing, and therefore is required to distribute the key so that you can sign modified binaries yourself.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  10. Re:Man-in-the-Middle Signature Attacks against GPL by phoenix.bam! · · Score: 1

    Wrong.

    The key is a signature. All it does is verify that the file came from somewhere. If Redhat distributes to a third party and the third party wants to modify the software and distribute it they are free to. And you are free to take the modified version and modify it further. No where though are you given the rights to impersonate Redhat. All they need to do is release the source code.

  11. Bias showing by amightywind · · Score: 0, Flamebait

    which consists of 70 minutes of Eben Moglen, with 20 minutes worth of interruptions from Stallman.

    You address Eben Moglen by his full name and then addresses Richard Stallman with much less respect. In my book both men are due some respect. This biasness should have been edited out by the Slashdot priesthood.

    --
    an ill wind that blows no good
    1. Re:Bias showing by EvanED · · Score: 1

      You address Eben Moglen by his full name and then addresses Richard Stallman with much less respect.

      Um, it's called an antecedent. (OK, not exactly, but that's the idea.)

      The summary referred to Stallman before with his full name. There's no reason to repeat it; "Stallman" is sufficient.

    2. Re:Bias showing by Anonymous Coward · · Score: 0

      Stallman's name was already given fully above, this was the first instance of Moglen's name .. Standard practice is to only list someones full name one time, thereafter using the last to refer to the person.

    3. Re:Bias showing by Brunellus · · Score: 3, Funny

      you have neglected to address Richard M. Stallman with the proper respect. Don't you know you must now say Richard M. Stallman, Peace be upon Him, or, in abbreviated form, RMS(PBUH)

    4. Re:Bias showing by omeg · · Score: 2, Informative

      Nonsense. RMS's name has already been mentioned a few times in the summary, and it's thus not necessary to give his full name again. The author might also have concluded that RMS is most likely more well-known than Eben Moglen, and that he could, for that reason, leave out his full name at that point.

      Seems to me like you're either very paranoid or just made a really bad joke.

    5. Re:Bias showing by eobanb · · Score: 3, Informative

      Wrong. Just about every manual of style and usage says that the first time you mention someone's name in a news piece, you use their full name, and after that, their last name only (or use Mr/Mrs/Ms/Dr/etc).

      Nothing to see here, move along.

      --

      Take off every sig. For great justice.

    6. Re:Bias showing by Anonymous Coward · · Score: 0

      You address Eben Moglen by his full name and then addresses Richard Stallman with much less respect. In my book both men are due some respect. This biasness should have been edited out by the Slashdot priesthood.

      Or perhaps they are just following standard journalistic practices, such as referring to a person by their last name after their full name has been used once.

    7. Re:Bias showing by SpaghettiPattern · · Score: 1

      >>which consists of 70 minutes of Eben Moglen, with 20 minutes worth of interruptions from Stallman.

      >You address Eben Moglen by his full name and then addresses Richard Stallman with much less respect.

      Although I agree on respecting people, I must say that apart from that, full name followed by surname only sounds better.

      PS: Also, the word RESPECT is nowadays often abused by small-minded bums that interpret it as "You surrender to me. Absolutely. No tedious questions asked. Onece, you might become almost just as cool as I am. And don't make jokes about my slang 'cause I'll waste you. That's a good fella." That deteriorates the word in modern language.

      --

      I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
    8. Re:Bias showing by Anonymous Coward · · Score: 0

      Insightful?

      Slashdot moderation at its finest.

    9. Re:Bias showing by TeknoHog · · Score: 1

      It's GNU/RMS, you insensitive clod!-)

      --
      Escher was the first MC and Giger invented the HR department.
    10. Re:Bias showing by Anonymous Coward · · Score: 1, Funny

      Doh! It's GNU/RMS(PBUH) of course.

    11. Re:Bias showing by asuffield · · Score: 1

      Don't you know you must now say Richard M. Stallman, Peace be upon Him,

      And you have to make the gesture of the holy beard.

    12. Re:Bias showing by the+Atomic+Rabbit · · Score: 1

      I wasn't aware that RMS is dead...

    13. Re:Bias showing by swdunlop · · Score: 1

      Wrong again. The grandparent comment is an obvious complaint that Mr. Stallman is mentioned far too many times on Slashdot.

    14. Re:Bias showing by Cyno · · Score: 1

      But let's not forget those manuals of style and usage are based on general usage of the language. If the way the language is widely used changes these manuals may need to be updated. Language and style are dynamic and change over time as the generations wear them down, toss out the tired old traditional forms and replace them with more modern and efficient constructs, B. Usually we see strict style and usage rules dissolve or get replaced by more free form and free thinking ideas. This is essentially the kids telling their parents to sit down and STFU, because they have learned the empiror wears no clothes. Sometimes this takes decades, but I think the rate at which this great awakening is happening is increasing. *G*

      ^_^

  12. Re:Man-in-the-Middle Signature Attacks against GPL by i23098 · · Score: 1

    What about Man-in-the-Middle attacks? That is, MonopolySoft builds a machine that will only run binaries signed by Red Hat. Red Hat is not required under GPLv3 to give its signature key, but the machine maker is, except, he's decided to verify only against Red Hat's key and he doesn't have Red Hat's private key (just the public key, which is used to validate that the binary came from Red Hat, which is all he needs). So I can still be prevented from modifying my GPL software and running it on my box, right? And no one's violated GPLv3, right? GPLv3 doesn't cover this type of attack at all.

    What attack?!?!? If you run the software on MonopolySoft machine that is GPL you can change the software to allow other binaries...

    The issue would came only if the MonopolySoft machine run only software that was signed by them. It the software is GPL then under v3 they must also provide the keys (I guess) so that people can run modified versions of the software...

  13. This is a good question: he's thinking about it by H4x0r+Jim+Duggan · · Score: 1

    This question was asked in the Q&A session after Richard's presentation. Richard answered that he will consult a lawyer, and he will do everything possible to fix this, and if you have suggestions they are welcome - and in the end he might fail to find a solution within the GPLv3 to this problem.

    1. Re:This is a good question: he's thinking about it by 0xABADC0DA · · Score: 3, Interesting

      Summary:

      1) Red Hat creates a binary linux distro based on GPLv3.
      2) Dell makes hardware that only runs *specific, known binaries*.
      3) You buy machine and compile linux from source, but it won't run.

      How does GPL v3 help?

      Dell can't distribute RH linux without making it possible for you to run your compiled version (whether the actual hardware that only loads the signed binaries is theirs or not), since they also have to accept GPLv3 in order to distribute software that is licensed with GPLv3.

      What's the loophole?

      Dell could just ship blank machines that you have to load yourself, that only run Red Hat. Dell may not even have agreed to GPLv3 for anything (by running completely commercial , bsd-like, or GPL-2 software).

      What's the solution?

      The GPLv3 can include a clause that if you accept the license you cannot distribute *any* product that prevents a user from using any of their own modified GPL-covered software. This means for Dell to ship a computer that only runs Red Hat Linux, they have to use *no* GPL3 software of any kind in their entire company. That's about the best you could do, legally, and even still it may not be enforceable.

      Personally I don't care how far-reaching the GPLv3 is. The idea that Dell could take my work and actively use it to take away people's rights is so wrong that there's pretty much nothing the license could do that would be worse. I'll be releasing my code as GPLv3 as soon as it comes out.

    2. Re:This is a good question: he's thinking about it by Anonymous Coward · · Score: 0

      "Dell can't distribute RH linux without making it possible for you to run your compiled version (whether the actual hardware that only loads the signed binaries is theirs or not), since they also have to accept GPLv3 in order to distribute software that is licensed with GPLv3.
      "

      If Dell hasn't modified Red Hat's software, it's not their problem.

    3. Re:This is a good question: he's thinking about it by Anonymous Coward · · Score: 0

      Nobody can redistribute copyright works without permission, so if Dell does not accept the GPL they cannot redistribute the software. Nothing else gives them the right to do so. It doesn't matter if they modify the original or not.

    4. Re:This is a good question: he's thinking about it by marcosdumay · · Score: 1

      That may be the most insightfull poster on the thread. You should post your solution to FSF.

    5. Re:This is a good question: he's thinking about it by Cyno · · Score: 1

      I like how you used Dell in your example. One can only hope some Dell board member or investor reads comments like this and thinks how their actions, and the actions of any business that behaves like them, raises expectations in our community that they will attempt to exploit our intellectual property. Not only do we believe they can't be trusted, we expect them to be unethical. I think that's the perfect message to give them.

      And I agree, GPLv3 for me too.

    6. Re:This is a good question: he's thinking about it by xmda · · Score: 1

      Personally I don't care how far-reaching the GPLv3 is. The idea that Dell could take my work and actively use it to take away people's rights is so wrong that there's pretty much nothing the license could do that would be worse. I'll be releasing my code as GPLv3 as soon as it comes out.

      Amen.

  14. Language is a virus from outer space... by C10H14N2 · · Score: 1

    "...That's why I'd rather hear your name than see your face"
    --Laurie Anderson, respect to Wm. Burroughs

    He may alienate people on the topic in question, but if he succeeds in waking them up to the importance of recognizing this kind of language, he's succeeded in something, IMHO, far more important.

  15. Fundamental flaw by ajs · · Score: 1
    The fundamental flaw in his statements comes early on, and the flaw in the GPL and the rest of his thoughts on it follow. Here it is:
    "DRM is an example of a malicious feature"
    DRM is not a malicious feature any more than CD writers are a malicious feature (though the RIAA might claim they are in much the same way Stallman wants to claim that DRM is). The reality is that DRM is a tool, and it's not the tool that's malicious, but some of its potential uses. We should be pushing hard, as a community that commands the attention of some of the most important IT groups in the world, to make sure that DRM can be used wisely as well as foolishly. I honestly don't care if Windows won't let you play a song without putting a quarter in your floppy drive. What I care about is that there are valid alternatives; that shipping a general purpose box that only allows one OS to be run on it is seen as anti-competitive, no matter what boogeyman we use to scare Congress (or whatever your local law-making body is called).

    On the other hand, I don't see why we should begrudge someone shipping a GPLed game on the XBox/360 or a GPLed version of an open format document reader on a phone. Personally, I'll take the software and modify it to run on platforms that I want to use, but the folks who want to run the DRM-platform versions shouldn't be left in the cold.
    1. Re:Fundamental flaw by j00bar · · Score: 1

      I think RMS ends up agreeing with you. DRM is kewl with *you* have the keys to your own computer to regulate it's function. It's bad with somebody else has the keys to restrict your freedom. In that the DRM clauses of GPLv3 only prohibit the latter, I think it's a good compromise.

      -jag

      --
      When all you have is a hammer, everybody looks like a Messiah.
    2. Re:Fundamental flaw by Anonymous Coward · · Score: 0

      It is a malicious feature when every known version of DRM violates the rights of at least one party in the transaction (most often the consumer). Every consumer has the right to fair use and the right of first sale (among other things). Violation of rights is a malicious act hence DRM = malware.

    3. Re:Fundamental flaw by Anonymous Coward · · Score: 0

      [blockquote]The reality is that DRM is a tool, and it's not the tool that's malicious[/blockquote]

      ah ah, incorrect. as the riaa and mpaa (and the judge in the napster case) say;if the tool is used for infringing use only, or a majority of infringing use, then the tool is malicious. napster and grokster both fell pray to this.

      drm does nothing but prevent rights. and it uses your own resources to do so. its doing something you do not want it to (malicious) aka malware.

    4. Re:Fundamental flaw by Anonymous Coward · · Score: 0

      DRM means control of what applications you can run. This is in fundamental conflict with the GPL v2 -- it just didn't specify it explicitly and that is a problem with stuff like Trusted Computing nearly here. The GPL v3 does specify it explicitly.

      90% of the problems here come from the fact that when people hear the term "DRM", they immediately think "music and video". DRM is about controlling applications and preventing untrusted applications from running and accessing data... you do not get to decide what your application does and does not do, you can't even recompile it with no changes. Stallman and the FSF doesn't really give a flying fuck about people file sharing the latest boy band drivel... he wants to ensure that you always have the ability to modify the code you are using. His position has never changed.

      Stallman and the FSF have cut right to the point of the argument, while you and most of the rest of the snipers, are still pissing around arguing about trivia and the MPAA, RIAA. I'm hoping the discussion over the GPL v3 will flush out more of you clueless drones who still don't understand what DRM really means and give you a much needed education.

    5. Re:Fundamental flaw by ajs · · Score: 1

      No, I'm not sure that I agree with that at all. It's like the old welded hood argument for Open Source, but turned around. We're saying that we won't let you run our software on a system with the hood welded shut instead of telling people that they can run it there, and letting them make the call.

      It's not as if people won't write software for these platforms, but now software written for other platforms under the GPLv3 won't be used by such people. That means that there is a strong market pressure to select non-GPLv3 software because it leaves your options open later and lets you interoperate across all platforms (regardless of how you manage your keys). This is a huge win for the BSDs which try to avoid GPLed software in the first place, but it probably means that any remaining GNU software that the BSDs use and which is re-licensed under the GPLv3 will have to be forked or re-implemented by the BSDs. This kind of colateral damage is unacceptable to me, and I will likely start running the forked/re-implemented software on my Linux systems as well, so that I can contribute to an effort which values the "open" part of "open source".

    6. Re:Fundamental flaw by Kjella · · Score: 1

      I honestly don't care if Windows won't let you play a song without putting a quarter in your floppy drive. What I care about is that there are valid alternatives; that shipping a general purpose box that only allows one OS to be run

      Do you care that you won't be able to use your box for media at all? That you won't be able to read any website using TCPA to "secure their copyrights" (which may mean the literal text on the webpage)? That you might not be able to connect to the Internet wuth a residential connection, because it requires Trusted Connect? That you can't read any Word document using TCPA "rights management"? That you won't be able to read any e-mail using TCPA "rights management"?

      If Microsoft succeeds in introducing TCPA everywhere, there won't be an alternative worth running. It will be so vastly inferior in capability, interoperability and usability from the onset, it wouldn't matter how good it was. I'm certain they will keep Mac around to show off their "non-monopoly" status, as long as Macs play by TCPA rules and take away our rights at the same pace Windows does. If you've been paying attention it doesn't seem like Apple has any problems with DRM (they want iTMS as loose as possible to increase sales, but they'll gladly lock down their own box with the latest in DRM).

      --
      Live today, because you never know what tomorrow brings
    7. Re:Fundamental flaw by Xtifr · · Score: 1

      > We're saying that we won't let you run our software on a system with the hood welded shut

      No. The GPL only covers distribution, not personal use. If you can get the software installed, then you can use it all you want, but you can't redistribute the software to others unless you also provide the ability to get the software (including modified versions) installed. This is fully in the spirit of the GPLv2. The whole point is, and always has been, that the users should have the ability to fix bugs/add features on their own. People who aren't willing to accept that are (as they always have been) welcome to try to negotiate other terms with the copyright holders.

      I suspect that your assessment of how much impact this will have on the market for GPL'd software is seriously overblown, but if you prefer BSD software, that's fine by me. I'm a big fan of BSD myself.

    8. Re:Fundamental flaw by Bananas · · Score: 1
      The reality is that DRM is a tool, and it's not the tool that's malicious, but some of its potential uses.

      Tell me what non-malicious use this tool can be used for? I understand that you're separating the tool from the decision of the tool-user (same arguement used by gun control critics, "guns don't kill, the person who pulls the trigger does") but it neatly sidesteps what the tool can and can't be used for. In the case of guns, this is a tool specifically designed to create a devistating, damaging impact from a lump of lead and/or copper at a specific point in space. Leaves little to the imagination, doesn't it? The same can be said of DRM; it is a tool specifically designed to control exactly what program can run on a given piece of hardware and/or control the flow of data on the same piece of hardware. Guns can be used for hunting (a use that is recognized as valid by a majority of people) or for murder (a use that is considered invalid by a vast majority of people). DRM can be used to secure information (a use that many would consider valid) or to directly control what you can or can't do with your computer (a use that many would consider invasive, unethical, and in some cases, immoral). There's just one last piece to this arguement: in the case of a gun, the owner of the tool uses the tool to affect a 3rd party (who is the recipient recieving the bullet), and the person pulling the trigger is (hopefully) the gun owner (i.e. the tool owner is using the tool). In the case of DRM, this is reversed; the owner of the computer is the recipient of the tool's effect, and a 3rd party decides on wheather or not they "pull the trigger". If you "own" your computer, then why does someone else have the right to determine what you can and can't do with it? Thus, it becomes an issue not of protecting copyright interests or preventing software piracy, but one of incredible vendor control. Want to use a software package that competes with a package that is also owned by Microsoft? Too bad. Microsoft can stop you from running that program. Your choice will be one choice - and that choice might not be what you want.

      I honestly don't care if Windows won't let you play a song without putting a quarter in your floppy drive. What I care about is that there are valid alternatives; that shipping a general purpose box that only allows one OS to be run on it is seen as anti-competitive, no matter what boogeyman we use to scare Congress (or whatever your local law-making body is called).

      You will care if the music is your legal posession and you have already paid for it. Now, a 3rd party could charge you over and over and over again for the "privledge" of listening to "your" music. This is already happening with printed material, which, ironically, was predicted by Stallman himself. He clearly understands the danger it presents not just to you the consumer/buyer/owner, but to society at large.

      There will be no valid alternatives, unless you can afford to mask your own chips, fab your own motherboards, etc. As far as shipping a single-use box goes, it is not illegal; and we certainly can't claim monopoly action, can we? (Double-jeopardy rules apply now that the manufacturer of Windows has already been found a monopolist). Frankly, the whole point of TPM was to provide Microsoft a means of complete control.

    9. Re:Fundamental flaw by ajs · · Score: 1

      "No. The GPL only covers distribution, not personal use. If you can get the software installed, then you can use it all you want"

      Ah, but there's the rub! If I go to the hardware vendor, get myself a key and port gcc (if there is eventually a gcc with GPLv3 licensing terms) to it, then I CANNOT give my version to anyone else! That's just silly, and yet unless I am allowed to release that key (which I probably am not allowed to do under my agreement with the hardware company), I can't give you a working compiler binary.

      No, I'm sorry. I'll just stick with free software, thanks.

    10. Re:Fundamental flaw by Anonymous Coward · · Score: 0
      No, I'm sorry. I'll just stick with free software, thanks.
      No such luck for the rest of us without keys...
    11. Re:Fundamental flaw by geekee · · Score: 1

      "f Microsoft succeeds in introducing TCPA everywhere, there won't be an alternative worth running. "

      nonsense. There's no reason that Red Hat can't introduce a version of a Linux distro that is locked down using the TCP hardware. It will be trustworthy because you can't modify the code and expect the hardware to work. Therefore the recording industry and the movie industry will be satisified. However, the recording industry/movie industry cannot trust people not to tamper with gplv3 code, as is their right, they will refuse to sell you content that runs using gplv3 code. No one is taking away your rights. They are offering you a product under a set of conditions. If you think they are taking away your rights, then you must come to the same conclusion about gpl taking away your rights, because RMS uses the same laws to restrict use of his code.

      --
      Vote for Pedro
  16. Re:Bias showing - depends on point of view by deeLo57 · · Score: 0

    What if it was out of convince and notoriety like "Madonna" or "Sting" certainly you don't believe people are being disrespectful to Madonna when they mention only her first name in the same sentence as Britney Spears, do you? Who's bias do you think is shown by the way you phrase your own question?

  17. Even worse by Anonymous Coward · · Score: 0

    Is the GPP trying to say RMS gois around with a 50 calibre magnum and FORCES people at gunpoint to use the GPL?

    Man, he must get a lot of air miles....

  18. Well said. by Anonymous Coward · · Score: 0

    I was worried about the unnecessarily critical tone of that too. Stallman gets a pretty bad rap, considering he singlehandedly started a revolution that most of us /. people now reap the benefits of.

  19. MOD PARENT UP by Darkforge · · Score: 1
    This question was asked in the Q&A session after Richard's presentation. Richard answered that he will consult a lawyer, and he will do everything possible to fix this, and if you have suggestions they are welcome - and in the end he might fail to find a solution within the GPLv3 to this problem.
    This is the primary issue preventing Linus from accepting GPL3. Linus writes:
    Notice how the current GPLv3 draft pretty clearly says that Red Hat would have to distribute their private keys so that anybody sign their own versions of the modules they recompile, in order to re-create their own versions of the signed binaries that Red Hat creates. That's INSANE.
    The FSF has in turn claimed that Linus has "misread" the license, but it's not at all obvious to me that he has. The GPL3 states:
    Complete Corresponding Source Code also includes any encryption or authorization codes necessary to install and/or execute the source code of the work, perhaps modified by you, in the recommended or principal context of use[...].
    If DRM'd hardware is the "recommended or principal context of use", then you apparently do have to distribute your private key. If non-DRM'd hardware is the principal context, but the software happens to be used on a DRM'd machine, then you get the Man-in-the-middle attack that the grandparent complains about. The FSF really needs to go back and think about this more carefully.
    --

    When I moderate, I only use "-1, Overrated". That way, I never get meta-moderated!

    1. Re:MOD PARENT UP by squiggleslash · · Score: 1
      No, in the situation you describe, RedHat (who probably wouldn't do this anyway - I add this in case anyone reads this thinking "My god! RedHat's going to try to violate the GPL!") has to rethink the situation more clearly.

      If RedHat (or whomsever) is signing its binaries purely so they will run on specific machines that have been locked to those distributions (the only case in which the keys are relevant, remember the wording "in the recommended or principal context of use"), in such a way that users of those machines cannot compile their own versions, then RedHat is violating the principle (and probably the letter) of GPLv2 and definitely the letter of GPLv3. It is absolutely right that under those circumstances, RedHat either not sign the distribution (and not produce a version for DRM'd computers), or they distribute keys allowing others to do so.

      This is about using DRM to bypass the GPL completely. And remember, the current clause 3 of GPL2 (the clause that mandates source code disclosure) reads, in part:

      The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
      It isn't at all clear to me right now that refusing to distribute a key that's necessary to compile code in order to make it run on a specific device is compatible with the above terms and conditions. Clearly without the key, you do not have a viable, let alone "preferred", form for making modifications.

      In any case, the clause in GPLv3 clarifies this and removes this loophole. There will be those that will throw a tantrum. Nothing, of course, prevents Torvalds, if he's so gung-ho about allowing manufacturers to lock their hardware to specific operating systems from specific suppliers, from adding a postscript to the license to relieve licensees from that duty. He hasn't with GPLv2, and if he so believes that that's a great thing to do, then he probably should.

      If DRM'd hardware is the "recommended or principal context of use", then you apparently do have to distribute your private key. If non-DRM'd hardware is the principal context, but the software happens to be used on a DRM'd machine, then you get the Man-in-the-middle attack that the grandparent complains about.
      And nobody considers it a bug, with the possible exception of Torvalds, that if DRM'd hardware is the "recommended or principle context of use", that you have to distribute a private key. That's not a bug, that's a feature.

      The GGP's comment about MitM attacks really only highlights the difficulty of putting together a license that catches every violation. What this, at least, does is make it obviously difficult for a hardware manufacturer to distribute GPLv3'd software with hardware that prevents that software from being changed. It doesn't make it impossible, but then, if they want it to be impossible, they can burn the entire thing into a ROM on an integrated chip. Putting up barriers though isn't a bad thing even if, for a minority, there are still benefits to be had from hopping over them.

      --
      You are not alone. This is not normal. None of this is normal.
    2. Re:MOD PARENT UP by Fujisawa+Sensei · · Score: 1
      If RedHat (or whomsever) is signing its binaries purely so they will run on specific machines that have been locked to those distributions (the only case in which the keys are relevant, remember the wording "in the recommended or principal context of use"), in such a way that users of those machines cannot compile their own versions, then RedHat is violating the principle (and probably the letter) of GPLv2 and definitely the letter of GPLv3. It is absolutely right that under those circumstances, RedHat either not sign the distribution (and not produce a version for DRM'd computers), or they distribute keys allowing others to do so.

      Signing binaries does not can can not restrict the binaries to only run on a specific machine. If what you're doing with the binaries restricts what machine the software can run on, that is a different matter.

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    3. Re:MOD PARENT UP by ray-auch · · Score: 1

      If DRM'd hardware is the "recommended or principal context of use", then you apparently do have to distribute your private key.


      It is worse than that, context of use says nothing about limiting to hardware - ie. it could be software - and nothing about DRM - it could be (say) a trusted software update application.

      In fact, in general terms, the "recommended or principal context of use" for a signed binary can only be a context in which a signed (with the right key) binary will behave differently to an unsigned one. That is the entire reason for signing the binary in the first place.

      The goal is very clear, as the recipient of a GPLv3 binary I must also be able to get the source and rebuild it (possibly modified) such that its "functioning in all circumstances is identical" to the one I received. That means if it is signed, either I have to be able to give it the same signature (ie. they have to send the key), or that signature is not checked or acted on.

      Now, if the binary was a redhat auto-update package that means either redhat has to send out their key, or the auto-update process (the context) must not treat redhat signed packages any differently to unsigned ones.

      There is no third option of "but you can change your system to trust your key" (as some say) - because that merely changes your particular context, not the "recommended or principal", your update will not be treated the same on other machines. Nor would be ok if the code would still install / run unsigned if the user clicked to approve it in some way - because now the functioning is not identical.

      The FSF has in turn claimed that Linus has "misread" the license,

      Yes, but in other places they are quoted as saying that:


      GPLv3 would not require Linux developers to publish the private keys that they use to sign Linux source versions to show they are authentic.


      Which is in fact fully consistent with Linus, because the GPLv3 bans / subverts binary signing. The FSF are specific about source signing being OK, and silent about binary - because actually binary signing is not OK by GPLv3.

      I don't think this clause can be "fixed" because the fault is fundamental -
      the GPL as a copyright on a piece of software (note, it is not a EULA) cannot control the context in which that software runs. It cannot affect what it, eg. TIVO hardware, does with a signed (or not) binary. The only thing the GPL can do to affect that is ban (or subvert) the signing of the binary in the first place.

      It is inevitable that banning the signing technology bans the good uses as well as the "bad", because the uses are outside the scope of GPL.
    4. Re:MOD PARENT UP by honkycat · · Score: 1

      If Redhat is signing their code so that it can be identified as originating from them, I can design my own "DRM" hardware that will only run binaries that have that signature. Now you cannot build your own versions and run them without Redhat's private key. Who is responsible for ensuring that you can build your own version? Redhat was not knowingly involved in this "DRM" implementation at all so it's unreasonable to ask them for their private key. I am not distributing GPL software at all, so its requirements certainly can't apply to me.

      This seems like a serious problem.

    5. Re:MOD PARENT UP by Anonymous Coward · · Score: 0

      From that quote it looks like Linus *has* misread it. If you *need* Red Hat's private key in order to install GPLv3 software that they have distributed, then yes, they must release it. Duh.

    6. Re:MOD PARENT UP by Anonymous Coward · · Score: 0

      No it's not, this is only a problem when:
      - the entity signing the software and the entity selling the hardware are not the same
      - the entity selling the hardware sells it without the software (if they include the software they're in violation of the licence) as they can't release the necessary keys.

      So anybody hardware company doing this would be completely at the mercy of Redhat (or whoever controls the key that signed the hardware), if that person/company decides to revoke the key, or starts using a new key for the next distro-release all their customers are screwed.
      -> I really can't see any big company trying this, let alone surving long if they do, it makes no economic sense whatsoever

  20. Re:Man-in-the-Middle Signature Attacks against GPL by Kjella · · Score: 1

    Since 4 out of 5 replies don't understand what you're trying to say, let me try to make it clearer.

    Bromskloss (750445) didn't understand it at all.
    Qzukk (229616) doesn't understand that the software could run on other hardware, but the hardware can not run other software.
    phoenix.bam! (642635) doesn't understand that the modified binary won't run.
    i23098 (723616)
    ainst GPL (Score:1)
    by i23098 (723616) doesn't understand that "MonopolySoft" doesn't *have* the key, nor to they distribute software.

    Basicly, you create two companies, "HardCorp" and "SoftCorp" which makes hardware and software, respectively. SoftCorp creates and signs software. HardCorp produces hardware which will only run SoftCorp-signed binaries. Then you make a third company to actually sell them, like a webshop with two products. SoftCorp will refuse to release their key since in theory they haven't limited you to any specific hardware - HardCorp did. Even if they use special hardware which means you won't find another machine to run it on without major modification, you don't technically require the signing key. This would be sort of like finding OS X-compatible hardware before the x86 switch. HardCorp doesn't have the key, nor do they distribute software. That way neither company falls under the GPLv3, yet you sell a hardware/software combo that is locked by DRM and where changing the binary means it won't run, and getting the software to work on anything else is impractical at best.

    --
    Live today, because you never know what tomorrow brings
  21. Re:Man-in-the-Middle Signature Attacks against GPL by Fujisawa+Sensei · · Score: 1

    The point of the key is to guarentee the that the code came from Red Hat, and giving away that key is idiotic. Giving away that key will let any wanker say that his code has been signed and certifies by Redhat.

    If you choose to run a machine that only runs signed binaries, that's your problem, not the GPL.

    In trying to protect itself, the FSF is going to shoot itself in the foot and remove the leg.

    --
    If someone is passing you on the right, you are an asshole for driving in the wrong lane.
  22. Bill? Is that you? by PetriBORG · · Score: 2, Informative
    Is it just me or does it seem like RMS created a new verion of the GPL because people stopped listening to him about the old one. It seems to me that RMS views are no longer connected with where Open Source should go, and will just lead Open Source to be too socially libral for wide use. OSS socially libral? We're all a bunch of commies is that it?

    The GPL3 is trying to address a great number of current problems with the GPL2 including things like use of web-scripts, patents, and other holes. It has nothing to do with th lime-light or some BS like that.

    The GPL functions the only possible way it could, by forcing the source code be given away for free. That is the entire goal of the GPL and it does it wonderfully. Patents threaten the GPL because someone could in thoery give away the source code with some patent hiden in and then turn around and try and charge you for making use of that source code.

    --
    Pete/Petri "damn, my chainsaw is clogged with 1's and 0's again." --clyde
  23. Re:Man-in-the-Middle Signature Attacks against GPL by Anonymous Coward · · Score: 0

    Well, you're closest. You've described how to get around having to give out the private key.

    The OP is incorrect in that there is no way to force SoftCorp to hand out their private keys. They're complying with the GPLv3 just by handing out the source. It's HardCorp that made it so that you can't run the software without SoftCorp's keys.

    So what'll happen is that HardCorp therefore can't distribute the software that SoftCorp creates, since the GPLv3 states that if you can't meet the license agreement you can't distribute the software at all. (And they can't, 'cause they don't have the key.)

    But there's no reason SoftCorp can't continue to release their signed binaries - after all, they aren't requiring you to use HardCorp's hardware. And HardCorp has no legal reason to remove the restriction that you can only use SoftCorp's software on their machine - they're not distributing SoftCorp's software, so they're not under the GPLv3.

    Presto: vendor lockin with the GPLv3, no private keys made public required.

    The only way RMS can get away with his little DRM hissy-fit is to do exactly what Mr. Torvalds thinks he already has: require everyone using the GPLv3 to hand out all their private keys. Gee - maybe Torvalds really does know what he's talking about...

  24. Re:Man-in-the-Middle Signature Attacks against GPL by MarkJenkins · · Score: 1

    Actually, MonopolySoft has violated the license. The problem for them is that they put themselves in a position where they could not possibly come into compliance. After the copyright holder complains, and after the 60 days are up, MonoplySoft will have to recall their product from the market. If they fail to do so the copyright holder can sue them.

  25. Re:O RLY? by vertinox · · Score: 1

    I like RMS, his ideas, and his work on GNU, but when he starts spouting off about "Treacherous Computing" and "Digital Restrictions Management" instead of using the traditonally accepted names (trusted computing and digital rights management, respectively), he just marginalizes himself and his positions.

    Traditionally accepted names? What is this tradition you speak of?

    I don't think we were talking about DRM back in the 1800's. Heck I didn't hear about DRM until the late 1990's and then I don't think society came up with it.

    But seriously, what he says is basically true. Trusted computing and Digital Rights Managment are phrases created to bias wording in someones favor (say the coporations). He is simply pointing out his bias.

    We do it every day:

    Insurgent or Freedom Fighter
    Revolutionary or Patriot
    Theft or Copyright Infringment

    Many phrases in the Englsih language mean the same thing, but each phrase has a different connotation that has a bias.

    There is nothing wrong of him to do so and I don't think he is marginalizing anyone. I would have to agree that DRM could mean Digital Restrictions Managment. It is obviously restricting me from doing what I want with content on my computer. I am of course not stating that this is right or wrong or that I agree or disagree with DRM, but it is obviously restricting use on my computer.

    --
    "I am the king of the Romans, and am superior to rules of grammar!"
    -Sigismund, Holy Roman Emperor (1368-1437)
  26. RMS was not interrupting at the GPLv3 launch. by Anonymous Coward · · Score: 0

    [...] with 20 minutes worth of interruptions from Stallman

    It's a difficult case to make that the author of the GPL is "interrupt[ing]" someone about his work when the speaker asks for comments from the author and shares the presentation with the author. Perhaps you could write a summary of the story and leave your projections for the comments so they can be appropriately moderated down.

    —J.B. Nicholson-Owens (jbn@forestfield.org)

  27. You don't understand well enough to criticize. by Anonymous Coward · · Score: 0

    Is it just me or does it seem like RMS created a new verion[sic] of the GPL because people stopped listening to him about the old one.

    Since most Free Software is licensed under the GPL, including the most famous programs this community has, I'd say it's just your misperception.

    It seems to me that RMS views are no longer connected with where Open Source should go, and will just lead Open Source to be too socially libral[sic] for wide use.

    You probably don't understand the GPL or RMS well enough to have an informed perspective on the matter.

    I disagree with RMS so my Mod points will negitivly[sic] reflect it.

    Your short post reveals multiple misunderstandings including citing the wrong movement—Open Source—which RMS takes pains to show why he's not now nor has he ever been a member of the Open Source movement. I would also add that the GPL is not properly called an "Open Source" license except in the most narrow way: it happens to qualify as an OSI-approved license. In more important ways, the GPL is the preeminent Free Software license; here are a couple reasons:

    • The GNU GPL was written by Stallman and the FSF years before the Open Source Initiative (which started the Open Source movement) existed.
    • The GNU GPL is a strong copylefted license, written to preserve precisely what the Open Source movement doesn't want to talk about—software freedom (the essay I pointed to clearly illustrates how the Open Source movement eschews software freedom).
  28. Re:Man-in-the-Middle Signature Attacks against GPL by marcosdumay · · Score: 1

    You got almost all right. But the WebShop can't sell both the hardware and software, because it must distribute the SoftCorp's keys.

    That means that it is hard to get a sucessfull lock-in this way. Lots of companies won't be able to do so. But this protection against DRM isn't absolute, the same way that DRM isn't also absolute (even in hardware).

  29. I want my DRM! by WillAffleckUW · · Score: 1

    Look at that coder, trying to use GPL
    He's got the source code, and he pubs for free
    Look at that coder, he wants the money
    So he imposes DRM on me

    Don't want to hack my microwave oven
    Don't want the audio to make an MP3
    Just want to pay out and be sued forever
    Give me DRM and let me be a slave!

    [chorus]
    I want my - I want my - I want my DRM!
    I want my - I want my - I want my DRM!

    We got to move these cross-licensed patents
    We got to ship these digitial HDTVs
    It's hard work slaving for the big boss
    But we don't care cause we're employees

    [chorus]

    Apologies to Sting.

    --
    -- Tigger warning: This post may contain tiggers! --
    1. Re:I want my DRM! by Anonymous Coward · · Score: 0

      Sting?
      Isn't "Money for Nothing" by Dire Straits?
      from the "Brothers in Arms" album.

    2. Re:I want my DRM! by WillAffleckUW · · Score: 1

      Sting is the singer of the chorus of the Dire Straights song.

      It's an obscure musical reference.

      That said, it sounds like I'll just have to go back to hooking up my speakers and putting a high-end microphone in front of them again, if we let DRM do what it says it will do.

      But ... once it's ripped to MP3, it's pretty easy to transfer it digitally, if it's music, but code is another thing. Even though MP3 is a German licensed technology.

      --
      -- Tigger warning: This post may contain tiggers! --
  30. Tradition doesn't define what's ethical. by jbn-o · · Score: 1

    All of these terms are new. There is no more "tradition" behind the monopolist's nomenclature than there is behind RMS' user-centric nomenclature. Nor should "tradition" define what is right and proper for a society. Did it ever occur to you that an "average Joe who wants to learn more about FOSS, GNU, etc." might want the ethical take on the matter that RMS presents and that it is the dog-eat-dog business-speak which alienates people? Since when did the business language become unquestioningly correct and any alternative become de facto offensive? Finally, if RMS were answering your question to your face, I'm sure he'd point out that what he's focusing on is his movement, the Free Software movement, not Open Source. Hence the term "FOSS" doesn't apply—that term is used for people who don't want to make the distinction between the movements or take a side, but he definately does take a side.

  31. Re:Man-in-the-Middle Signature Attacks against GPL by Chuckstar · · Score: 1

    But in this example, MonopolySoft only manufactures hardware. Red Hat is the software distributor.

  32. How many lines of code does the FSF produce... by Anonymous Coward · · Score: 0

    ...versus how many lines of legalese and press releases?

  33. Re:Man-in-the-Middle Signature Attacks against GPL by MarkJenkins · · Score: 1

    Ahh, I assumed that MonopolySoft was including the copy of Red Hat with the machine, making them the key software distributor in this case.

    A highly unrealistic scenario has been contrived here. The parties involved can go right ahead, such an absurd device will enjoy little success. The license does not need to be modified to prevent this (nothing probably can), and the anti-DRM clauses need not be scraped under the view that this little pore hole makes them useless.

    If some third party wants to sell the convenience of a combined machine-software combination, they will be out of luck.

    This situation is far removed from the Tivoesque situations the new changes are meant to deal with.

  34. not enough by hawk · · Score: 1

    no, you ingrates, that's *not* enough. It's not "3", but "GNU/3". And don't even get me started on the letters . . .

    hawk

  35. Re:Man-in-the-Middle Signature Attacks against GPL by JahToasted · · Score: 1
    Why not? Webshop can just sell them as two separate products. The GPLv3 isn't violated until the customer actually installs the software onto the computer, at which point the its still legal since its personal use. Its not up to Webshop to try to guess what softawre the customer will install on his hardware.

    Its no different from selling DVD burners and blank DVDs. it could be used for illegal things (and often is), but its not up to Webshop to prevent people from doing illegal things with the stuff they buy.

    And what happens if SoftCorp releases their software for free? people could buy their hardware from HardCorp and download their software from SoftCorp.

  36. Re:Man-in-the-Middle Signature Attacks against GPL by drew · · Score: 1

    That way neither company falls under the GPLv3, yet you sell a hardware/software combo that is locked by DRM

    I don't really think this situation is even a minor threat. The thing is that "you" can't legally sell the hardware/software combo- no one can. Just because SoftCorp doesn't make the keys available, doesn't mean that anyone else who gets the source from them is relieved of that responsibility. If you distribute SoftCorp's software, you are under all of the same obligations they are. If you were to distribute their software bundled together with hardware that only works with digitally signed binaries, you are still obligated to provide the signing key, even though you don't have it. Hence, you have no ability to legally distribute said combo.

    Essentially this man-in-the-middle attack is only possible with a hardware and software combination which must always be sold independently of each other and where the eventual end user must perform the actual installation himself. It's a complete non-starter...

    --
    If I don't put anything here, will anyone recognize me anymore?
  37. Re:Man-in-the-Middle Signature Attacks against GPL by marcosdumay · · Score: 1

    GPL triger on the moment that you pass some GPLed software to another person. That means that if WebStore sells the program, it must agree to the GPL, so it can't sell the piece of hardware.

    The only way to put the two (hardware and software) toghether without violating the GPL is by the end user doing so.

  38. You can't fight Trusted Computing with a License by codehead78 · · Score: 1

    Trusted Computing is coming, so how is making the GPL completely incompatible going to help anything? If people buy into this idea, Open Source will just get squashed. The idea that being able to use Open Source on your hardware can be used as a bartering chip in this fight is laughable. If this comes to pass, Ballmer should put posters of RMS up in his office, buy him a new car, a new suit, and a locked down machine that only runs Windows.

    This fight can only be fought with wallets. Consumers have to know what they are buying, and why they don't want a crippled machine. Is that more difficult that adding a few paragraphs to a document? Of course. But it is not in the interest of Dell, Gateway, or Apple to sell crippled computer. They need to know that doing so will lose them money. Hardware vendors should be fighting the Content providers pushing for this, not the FSF.

  39. Is Stallman's software patents talk published? by H4x0r+Jim+Duggan · · Score: 1

    A camera crew filmed Stallman's opening keynote about software patents, but I can't see it on that page. Is it there (under a name I failed to guess)? Or will it be available at a later time? (if so, in the same place?)

    Thanks.

    1. Re:Is Stallman's software patents talk published? by LordNightwalker · · Score: 1

      Hmm, I see something with Stallman talking, titled "GPL"... It's this one.

      If you run Linux, start downloading it with wget, and when you get a couple hundred KB, watch the file with mplayer while it's rolling in... This way you can check out if it's the one you need, and stop the wget process + delete the file if it isn't.

      --
      Install windows on my workstation? You crazy? Got any idea how much I paid for the damn thing?
  40. Re:You can't fight Trusted Computing with a Licens by 0xABADC0DA · · Score: 1

    This fight can only be fought with wallets.

    Completely wrong. This fight cannot be won with wallets, because the difference between DRM and non-DRM hardware can be as simple as not loading a key into the DRM thus disabling it. So every dollar you spend on non-DRM hardware also supports DRM-hardware. It's the same hardware.

    Unless you think anti-DRM purchasers are going to be more than half the market, they are perpetually being marginalized by the faster-growing market of DRM-enabled hardware. And even if they are that large, they are still buying hardware with disabled DRM in it. Average Joe is going to see a $50 rebate on the system up-front to activate the DRM and then end up spending $50 on music or "reactivations" of his movies he could have had for free.

    You don't go into this with the hardware you want, you go with the hardware you have. That hardware *already* has DRM on it, waiting to be activated. Instead you fight fire with fire: they take away your hardware and you respond by taking away their software. Then you sit back, wait, and watch the whole damn dumb-show play out. Then you win because software is more valuable.

  41. Re:You can't fight Trusted Computing with a Licens by codehead78 · · Score: 1

    You had me until "Then you win because software is more valuable" because Open Source is only an alternative to other software that will play nice with DRM. Closed source softeware is also valuable, in fact you could argue that it is more valuable to Dell and Gateway. Actually, no need to argue, it IS more valuable to hardware vendors.

    1: Don't bring a knife to a gun fight.
    2: Don't put the knife to your own neck.

    The GPL3 says, stay open or else. The message that needs to be sent is, stay open, that's what your customers want.

    The only advantage they have is that they think people won't care or won't notice.

  42. Re:Man-in-the-Middle Signature Attacks against GPL by Fujisawa+Sensei · · Score: 1

    This is not an attack.

    MonopolySoft is not violating the GPL. They are not preventing you from building the software, they are not preventing you from distributing the software. They are restricting which software you are allowed to run on the machine, which is etirely different.

    In short you're SOL, and should have not purchased that box.

    RMS is subverting the spirit of his own GPL, by not just placing restrictions on distribution, but restrictions on usage and modification of GPL software.

    --
    If someone is passing you on the right, you are an asshole for driving in the wrong lane.
  43. They don't work & this is why by Anonymous Coward · · Score: 0

    Basically, if you cannot uphold the terms of the GPL, you cannot distribute a GPL-covered work at all.

    Even if it's not your fault.

    That said, if I'm missing something here, feel free to submit comments or fixes to them. GPLv3 is a draft, and this sort of thing is exactly what they have comments for--to fix any oversights before they publish a final version.

  44. RMS won't endorse CC because of people like YOU! by Anonymous Coward · · Score: 0

    > Either RMS likes customizing licensing, or he doesn't. He's being a hypocritical here.

    He doesn't hate all CC licenses, he refused to endorse them all because some are free and some are non-free. He likes the free ones and dislikes the non-free ones. He feared that any statement from him would be taken as an endorsement of all of them, including the non-free ones. Instead, Slashdot ran a story about him "attacking" the licenses by refusing to endorse them, and people got this crazy idea that he disliked all CC licenses, even the free ones.

    He probably does disagree with lumping them all together, though, so as to obfuscate the differences between the free and non-free CC licenses. After all, that silly obfuscation he was complaining about was the root of yet another long Slashdot rant that had absolutly nothing to do with the article. Naturally, absolutely no one here demonstrated that they had so much as skimmed the thing.

    Lastly, to ignore someone's reasons for believing things in accusing them of hypocricy is nothing but character assassination. It is not reasonable, it is not logical, and it is not kind. Please do not engage in such things.

  45. Re:O RLY? by QuantumG · · Score: 1

    What's worse is that assholes refer to just about everything as DRM. It's a catch all term. Product Activation? DRM. CD Check? DRM. Gotta download a codec to play a movie? DRM. Hell, I've heard people refer to the restrictions on what you can do with objects in a MMORPG as DRM. It's as non-specific as Intellectual Property, and worse than IP it presupposes that creator of the file to which the "rights" are attached actually has any right to have those "rights" enforced on my machine.

    --
    How we know is more important than what we know.
  46. Re:Man-in-the-Middle Signature Attacks against GPL by Spit · · Score: 1

    Why should the vendor decide what's worthwhile to run? The real solution is to have embedded crypto-signing where the vendor signs their software, then the user may verify the signature before signing the binary with their own key. This way the binary is verified, and only verified binaries are allowed.

    --
    POKE 36879,8
  47. IBM ? by Quiberon · · Score: 1

    IBM doesn't ship personal computers any more, just like it doesn't ship typewriters, or card punches. It moves on, to shipping supercomputers-on-a-chip for Microsoft, Sony, and Nintendo to put in their games consoles. However, the IBMers need to use personal computers, to get on with IBM's business ('Support the commercial clients in their businesses'); and the IBMers need a huge amount of freedom to be able to do that effectively. So the IBMers are likely to need the 'free' computers, just the way RMS would like them.

  48. Re:Man-in-the-Middle Signature Attacks against GPL by Anonymous Coward · · Score: 0

    And if somone can show that the companies are linked they would be in hot water.

  49. Re:Man-in-the-Middle Signature Attacks against GPL by mabhatter654 · · Score: 1
    I get where this is going...
    let's say another software maker generated new program 2000 that only works on Red Hat signed kernels.

    i suppose if it was a software "service" you'd be SOL, but free to move on to another seller.

    I could see a situation where Dell, for instance, gets a lot of "free" ad-ware for accessing media, online accounts, etc to load up on your new red hat install and when you update the kernel all that stuff stops working.
    Red Hat did't violate the GPL by signing their kernels.
    How could you hold Dell responsible if all they did was recompile and repackage???
    Where the parent is heading is if the third party required Dell to tie the keys together before distributing it.. They could get out of giving the keys because Dell distributed the software, and dell or red hat could help you because it's not their software either???

  50. Re:You can't fight Trusted Computing with a Licens by geekee · · Score: 1

    "But it is not in the interest of Dell, Gateway, or Apple to sell crippled computer. They need to know that doing so will lose them money. Hardware vendors should be fighting the Content providers pushing for this, not the FSF."

    Apple sells iPods with DRM because it enables them to sell music online. The recording industry would refuse to allow Apple to sell online music otherwise. A normal consumer considers a computer that won't play their music at all more crippled than one that will play their music with restrictions. So a GPLv3 computer is more crippled than a Mac by a normal consumer's standards So you need to convince the recording industry and the movie industry that DRM is unnnecessary if you don't want crippled computers (crippled by your standards).

    --
    Vote for Pedro
  51. that's just his GPLv3 one, there was one on swpats by H4x0r+Jim+Duggan · · Score: 1

    That's only the recording of his second talk, the one on GPLv3. He also gave the opening keynote where he talked about software patents. There are other recordings of his software patents speech given at other events on the GNU project philosophy audio page, but he software patent talk at FOSDEM was particularly interesting because of his comments about EU democracy at the end. From looking at the names of the files, I don't think any of them contain his software patents speech - which is strange since the camera crew did record it.

  52. Re:that's just his GPLv3 one, there was one on swp by LordNightwalker · · Score: 1

    Very strange indeed; all speeches from saturday should be there in theory. They're still encoding some speeches from sunday, so you won't find them online yet, but they've already posted the valgrind speech given sunday afternoon which should indicate that all speeches from Saturday should be online already.

    The only guy who flatout refused to have his speech filmed was Tomasz Kojm from ClamAV, so you'll never see that one online. Unfortunately, I was one of the volunteers who was forced to undergo it in order to give him his 15 and 5 minutes warning before his speech would end, and given the quality of the speech in question, I certainly understand why he didn't want that one committed to film. ;)

    --
    Install windows on my workstation? You crazy? Got any idea how much I paid for the damn thing?
  53. Stallman's thoughts on CC are in this blog entry: by H4x0r+Jim+Duggan · · Score: 1

    Stallman's thoughts on CC are explained in his blog about being on a panel with a CC lawyer.

  54. Re:Man-in-the-Middle Signature Attacks against GPL by JahToasted · · Score: 1

    Wait a sec, you mean you can't sell a GPLv3 product AND a DRM'd product at the same store? Hell an iPod has DRM, so anyone selling iPods can't sell something with GPLv3? It seems like GPLv3 isn't going to catch on if that's the case.

  55. solution doesn't work by geekee · · Score: 1

    "The GPLv3 can include a clause that if you accept the license you cannot distribute *any* product that prevents a user from using any of their own modified GPL-covered software."

    Del simply does not accept the license, sells you a blank box, and tells you to go to Red Hat to get the software. Since Dell didn't distribute any GPLv3 software, they are not bound by GPLv3.

    --
    Vote for Pedro
    1. Re:solution doesn't work by Reservoir+Penguin · · Score: 1

      Then you didnt't get the idea. Dell frankly won't me able to make and support a machine that will run any (unofficially) approved version of RedHat w/o testing it on their machines sometime during the production cycle. If they dont accept gpl3 they won't be able to have it nowhere near the compnay property.

      --
      US-UK-Israel: The real Axis of Evil
  56. Look at the past to understand the future. by jbn-o · · Score: 1

    Didn't RMS blow a gasket a few weeks ago, talking about how Creative Commons sucks eggs because it includes optional clauses?

    No, RMS pointed out that not all CC licenses confer the same rights onto licensees and that it is a mistake to talk about them simultaneously as if one is just as good as another:

    "Some Creative Commons licenses are free licenses; most permit at least noncommercial verbatim copying. But some, such as the Sampling Licenses and Developing Countries Licenses, don't even permit that, which makes them unacceptable to use for any kind of work. All these licenses have in common is a label, but people regularly mistake that common label for something substantial."

    As a practical matter, this is not much of a problem because so few works are licensed under any of the Sampling licenses (even the one that allows non-commercial verbatim copying) and the Developing Countries Licenses.

    As a matter of principle, I think his objection was fair, proper, and clearly and concisely stated. People who learn what he's talking about can repeat this critique when explaining what CC licenses are, so they won't spread more confusion about the Creative Commons. If it were me interviewing him I'd want to know why he chooses to raise an objection to an organization that is doing good work, broadly speaking? It seems to me that if one's friends are doing generally good work, it is strategically better to clarify one's critique (repeating it often so it's clear), champion their successes, and downplay their flaws until the flaws become a more practical problem down the line.

    How is this different? Now, instead of GPLv3, we have GPLv3-with-patent-restrictions, and GPLv3-with-attribution, and GPLv3-with-different-disclaimer-of-liability, and...

    It's different because he's not complaining about optional clauses (short additions to a license, the bulk of which remains the same and confers the same rights and responsibilities on licensees). The current GPL allows one to add various clauses to give licensees things the unmodified GPL doesn't allow. This version of the GPL has been around for more than a decade. The GPLv2's popularity (the most popular Free Software license) with optional clauses didn't result in different GPLs. The GPLv3 will continue this now time-honored way and apparently successful strategy in licensing.

    Either RMS likes customizing licensing, or he doesn't. He's being a hypocritical here.

    He does, he's not being hypocritical here.

    Your post is not interesting. It is incorrectly moderated.

  57. Re:You can't fight Trusted Computing with a Licens by westlake · · Score: 1
    Consumers have to know what they are buying, and why they don't want a crippled machine.

    The consumer market demands media content from the major providers. You deliver it or you die. Apple understands this. Microsoft understands this.

  58. Tell the full tale and point to the source. by jbn-o · · Score: 1

    The FSF says more about their objection to the original Artistic license than you're repeating. What did they say when you asked them for more specifics about their objections? They aren't an organization to refrain from offering such information about licenses that matter—their objections to the Apple Public Source License are noteworthy. They also point to a revised version of the Artistic license that is a GPL-compatible Free Software license. Perhaps it simply isn't terribly pressing to offer extended commentary about an old version of a license. Also, as a practical measure, so few programs use the first Artistic License relative to other Free Software licenses it really isn't a compelling case to argue about it.

    As for your objection that it is RMS' opinion alone which determines whether a license qualifies as a Free Software license, you would do well to support the point, not just state your opinion on the matter as if its above justification.

  59. Isn't that just so much name-calling? by jbn-o · · Score: 1

    Please do spell out for us how RMS' advocacy for software freedom and the GPL are properly described as "zealotry".

    Also tell us why one should attempt the impossible: to grant all freedoms to all people. In what way is the GPL "unrealistic"? You appear to be complaining that the GPL won't let you do whatever you want with the covered code. Why should the GPL allow proprietary derivatives? That would not be granting a freedom, it would be allowing others to have power over users. Power and freedom are different. Why can't you write your own program to do what you want it to do and then license it as you wish?

    1. Re:Isn't that just so much name-calling? by caffeination · · Score: 1

      read this other reply
      I'd normally have nothing but good to say about free software, it's just that guys like RMS bring up anything negative I can think of. Apart from that, you're the first person I've ever known to say that Richard Stallman isn't a "zealot".

    2. Re:Isn't that just so much name-calling? by jbn-o · · Score: 1

      Apart from that, you're the first person I've ever known to say that Richard Stallman isn't a "zealot".

      Actually, I didn't say he was or wasn't a zealot. I asked you to justify calling him that. And you haven't done so.

      I notice the difference in who is tarred with the term "zealot" and how the norm is defined. Business leaders are not called zealots yet they defend their views on "intellectual property", ownership of code, and control over how you use your computer to unreasonable extremes often lapsing into revisionist history and a profound disagreement from what their own organizations have done. Microsoft's Bill Gates, for instance, told an audience of unquestioning sycophantic students at the University of Illinois at Urbana-Champaign that the GPL was an improper license for software distribution. He said this while Microsoft was doing distributing GPL-covered software in its services for Unix package which includes a number of GNU programs (a package of programs Microsoft had been distributing for some time). The public is ostensibly supposed to take Gates' talk as perfectly reasonable assertions of fact when they are demonstrably false. I contacted the University of Illinois about scheduling a rebuttal talk from someone at the FSF, and they gave me the runaround. In trying to schedule this talk, I learned that Gates had contacted UIUC and the University was apparently only too willing to have him talk.

      RMS' talk is far more correct than incorrect and it is still impressive just how far ahead of the curve he was and is: his objections to software patents preceeded many and only now are we seeing real organized political objection to software patents (but not in the US, in Europe); the events in RMS' dystopic story "The Right to Read" are more within reach now than they ever were, but business proponents of so-called "Digital Rights Management" (itself a revealing term that reframes the debate away from its effect on users and towards asking you to agree with the publisher's desire for more control over users) don't want you to see this future because you might reject it; RMS discussed the problems with the Bitkeeper fiasco when many here were championing licensing power (and confusing that with freedom). The cleverness of the GPL in using copyright law to build a commons for all was ahead of its time and that license played a big part in building a social movement known as the Free Software movement. His arguments are ahead of the curve in that they aren't technocratic, they are framed on an ethical basis. This means that his arguments are far more likely to survive whatever technological changes come about, but a lot of Americans have trouble discussing things in ethical terms because we're taught by businesses to value and internalize business values. I'm sure this only touches on a few instances where RMS was right about important matters concerning our ability to stay free to communicate with each other and build a community of sharing information.

      RMS does things I don't agree with, to be sure. But these points are few in number and of relatively little significance when compared to the things he deserves to be lauded for. I've recently posted on his take on the Creative Commons licenses. However from what I can see, RMS has much wisdom to offer and makes far far fewer missteps than others that /. readers would supplant him with if given the opportunity (like you endorsing Linus Torvalds in another post).

  60. You don't grok what you think you grok. by jbn-o · · Score: 1

    If it's free software, why is RMS restricting my freedom to do with it as I please? In a free country you are not allowed to arbitrarily restrict someone's freedom (as killing does). If the software is free, then that implies there are no restrictions. This is not the case for GPLed software. It is the case for public domain software such as BSD.

    Going in order of what you mention:

    • Freedom doesn't mean "do[ing] with it as I please" because you can't have all possible freedoms. Some freedoms conflict. Society must choose which freedoms to preserve, then restrict other freedoms in order to ensure other freedoms. The GPL is no different; it prohibits proprietary derivatives so that the freedoms of Free Software (running, inspect, sharing, and modifying software at any time for any reason) are maintained for users of the work and its derivatives.
    • The restrictions in the GPL are not arbitrary, they favor the preservation of software freedom above the power to deny others that freedom. The restrictions in law in most countries favor wealthy people and are also not arbitrary.
    • "Public domain" software is not covered by any copyright license. Hence "public domain software such as BSD" makes no sense because it is a contradiction. However, even the new BSD license has restrictions. Works licensed under the new BSD license are not in the public domain.
  61. Re:Man-in-the-Middle Signature Attacks against GPL by jrumney · · Score: 1
    The only way RMS can get away with his little DRM hissy-fit

    When you've finished with your straw man hissy fit, perhaps you'll realise that in the real world, HardCorp will fail. Their entire product range relys on you buying an operating system which you cannot get from the same supplier as the hardware, and installing it yourself, in a world where 99.9% of end users buy their hardware (servers and GNU/Linux Desktops included) with the operating system preinstalled, and the other 0.1% are smart enough to know better than to fall for this scam.

  62. Re:Man-in-the-Middle Signature Attacks against GPL by jrumney · · Score: 1

    MonopolySoft is manufacturing hardware that is dependant on RedHat's GPLed software to work. Even if they are not distributing Red Hat itself, I would not like to put money on them being cleared of violating GPLv3 because of this dependancy which they deliberately introduced.

  63. Re:Man-in-the-Middle Signature Attacks against GPL by Anonymous Coward · · Score: 0

    That's an obvious economic dead alley for MonopolySoft, they'd be making themselves completely dependend on redhat for a critical resource. I really can't see any big company trying this, nor can I see many clients bying this.

  64. Re:Man-in-the-Middle Signature Attacks against GPL by Anonymous Coward · · Score: 0

    No he's not:
    - the incident that got RMS started on the road to Free Software is one where he couldn't fix a
        printer because he didn't have the code
    - what this prevents is the situation where he can't fix the printer because he can't load his fixed
        version of the software

  65. Re:Man-in-the-Middle Signature Attacks against GPL by Chuckstar · · Score: 1

    What in the GPL stops them from doing so? Including a shrinkwrapped copy of Red Hat, for example, would keep them from being considered a propagator under GPLv3, so the license would have no jurisdiction.

  66. Re:Man-in-the-Middle Signature Attacks against GPL by Qzukk · · Score: 1

    The point of the key is to guarentee the that the code came from Red Hat

    Yes, and the license differentiates between the two. In the real world this signature is not required to run the code, therefore you don't need to get the key. You are required to distribute everything necessary to run a locally modified/compiled executable.

    Now if Red Hat distributed some GPL3 software, and it only ran on MonoSoft 15215 processors, and the MonoSoft 15215 only ran signed binaries, then distributing the tools required to sign the binaries is required, because by targeting the 15215 they chose to use a DRM-encumbered platform that required signing to execute software. If they don't like this, their choices were A) don't code for the 15215, or B) don't use GPLv3 code.

    Now, the key doesn't have to be the same key used by Red Hat, they could distribute an alternate key, as long as signing the binary with the alternate key also allows it to run on the 15215 processor.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  67. Torvalds is no Free Software advocate. by jbn-o · · Score: 1

    The only front man I'd be happy with is Linus, and obviously we don't want him taken away from the kernel. So we're left with something like a power vacuum, and RMS is a nice plump shape to plug such a hole.

    If you could drop the name-calling long enough to engage in an adult discussion, you'd see that Linus Torvalds doesn't speak for Free Software because he's opposed to it. He opposed Andrew Tridgell when Tridgell worked on a free program to allow users to pull data from Bitkeeper repositories. The FSF's FAQ entry on "strengthen[ing] Linus Torvalds' role as posterboy for our community" is helpful as well. On top of that, he has changed his position on giving GNU any credit at all. When his kernel was first announced he was ready to give GNU credit for what it is, now Torvalds denies GNU any credit and apparently believes that Linux is an operating system. His self-aggrandizing takes the form of routinely allowing interviewers to come away with that misunderstanding by never taking the time to correct their misstatements.

    You are will must to be like it.

    I don't understand what this sentence means. The grandparent post of this post is quite wrong about RMS' involvement in GNU and authorship of Emacs.

  68. Re:Man-in-the-Middle Signature Attacks against GPL by marcosdumay · · Score: 1

    You are a troll, isn't you? Well, if not, reread the topic and the first message of the thread.

  69. Re:Man-in-the-Middle Signature Attacks against GPL by marcosdumay · · Score: 1

    Ok, sorry for the previous poster. I am a bit tired and didn't think about it so well. To comment that today, you must be genuinely interested.

    If the GPL comes out with the DRM clause, the WebShop won't be able to sell both SoftCorp's software (that is under GPLv3) and HardCorp's computer. That is because HardCorp's computer needs a signed software, and only SoftCorp has the keys.

    If the WebShop sells the software, it must agree to the GPL, so they need to disclosure the keys. Since they don't have the keys, they can't sell the software. I guess that all the confusion comes because, if WebShop didn't sell the hardware, it could sell the software, but all that it is prohibited to sell is the software, never the hardware.

    Also WebShop will be able to sell other DRM hardware, if they don't use SoftCorp's keys.

    The iPod DRM is sompletely unrelated to all that. You don't need any key to make your software run on iPod (you simply can't run your software on it, I guess), and the software is not under GPLv3. So, WebShop will always be able to sell iPods.

  70. Stick with GPLv2? by Lesson+No.+25 · · Score: 1

    For better or worse, if someone or some company doesn't like GPLv3, what's to stop them from releasing their work under GPLv2? (Assuming the answer is "nothing"...) Doesn't that rob the GPLv3 of much of the power RMS is trying to give it?

  71. Aha, here's the video: by H4x0r+Jim+Duggan · · Score: 1

    Another group have now published other videos from FOSDEM 2006 and their collection includes Stallman's software patents speech: http://free-electrons.com/community/videos/confere nces