Slashdot Mirror
GPL 3 to Take Hard Line on DRM
sebFlyte writes "ZDNet is reporting that Eben Moglen, the FSF's lead lawyer and the co-authour of GPL3, has explained that DRM is 'fundamentally incompatible' with the aims of the FSF and will be given short shrift in the latest version of the free software licence, which bans the use of 'digital restrictions' in GPL3 governed software. In his words: 'I recognise that that's a highly aggressive position, but it's not an aggression which we thought up. It's a defence related to an aggression which was launched against the people whose rights are our primary concern... We don't want our software used in a way which batters the head of the user to please somebody else. Our goal is the protection of users' rights, not movies' rights.'" We discussed the new GPL on Monday.
I wonder if Sony's DRM screw-up and evidence that GPL'ed code was in their DRM software played any role in this rather firm approach.
I'm conflicted, to be honest.
As a writer, I'd like to be paid for my work. I'd rather not make it easy for people to redistribute my work without compensating me.
As a consumer, I'd like open access to the things I purchase.
Argh!
Shinma
I bet Linus is grateful he didn't put ".. or later" in the Linux copyright. These kind of political doings seems like exactly the thing he'd be against.
Life is Reality
It's good to see someone with some amount of clout taking a stand against unreasonable constraint of fair use rights. I just hope that this becomes a catalyst in a chain reaction of rebellion against DRM, which manages access in the same way that a jail manages freedom (my apologies to the /.er who I took this .sig from - cant recall his/her name).
uR iGn0ranc3, Their Power
So it won't be legal for someone to write a media player for someone else's media content that comes with DRM, and release this media player under GPL3? Sure, other licenses can be used for such things, but now such projects cannot benefit from other aspects of GPL3.
This is assuming Linus even likes the new GPL. As far as I can tell, he's not too sympathetic to RMS's values anyway.
I demand that Red Hat immediately hand over all their private keys!
Wrong. GPLv3 says that you need to provide all keys needed to make the software functional for its intended purpose, not the keys needed to make a bit-for-bit identical package.
Thus, if your piece of software is supposed to be able to read scrambled data, you cannot hide the decryption key -- but, you are free to sign the packages to prove they are untampered binaries produced by you. In the former case, the program wouldn't work, in the latter, it just will trigger a warning from the OS which says the user is about to install unsigned binaries. No one forces the user to heed the warning, and she can disable it if she wants. No functionality is lost.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
Aren't file permissions in *ix and Windows systems a form of DRM? Does the GPLv3 distinguish between DRM that you control (file permissions and such), vs. DRM controlled by others (Hollywood's wet dream)?
Oh, no! You have walked into the slavering fangs of a lurking grue!
I don't get the point... no company in their right mind would write open-source DRM software already, so other than idealistic sentiment, why is this addendum necessary? If the aim is to ensure that no GPL'd code ever makes it into DRM software, isn't this going against the whole notion of the GPL to start with? I thought the free software movement was about increasing the quality of code in the world by cooperation.
------- "From bored to fanboy in 3.8 asian girls" ----------
I know we all hate DRM but a lot of businesses see this as the future, if the GPL instantly cuts DRM out then the OSS community maybe limiting it's growth in the business world. I understand the GPL is a "play nice" style licence, but when you outright ban use of your software to any coompany using DRM you may well turn a lot of important areas away, so in the end you end up as a small time group instead of people who changed the world.
I like muppets.
Broaden the meaning of this question and there is no doubt - the recent explosion of news events regarding DRM, especially the Sony issue, has hardened the opinions of many of us. Perhaps the use of GPL code did not itself have an effect, but the whole mess certainly did
Using plain ol' text since 1968
The planned anti-DRM changes to the GPL are significant because the entertainment industry regularly uses Linux-powered computers in the production process, notably for special effects and animation. In general, movie studios support DRM technology.
It is a bit ironic that the same companies that don't want you to see their movies for free will use software that can be obtained for free to make their movies.
I guess the entertainment industry motto is: "Why pay for it if you don't have to?"
He who knows best knows how little he knows. - Thomas Jefferson
Linus may stick with GPL version 2 for the simple reason that he may wish to equip Linux to be able to implement hardware-based DRM. Linus is pragmatic in the straightforward sense: many Linux users will want access to DRMed material... Hence version 2, not version 3.
Stallman is pragmatic in a more esoteric sense: the GPL version 2 has been increadibly successful. He is pitching the GPL version 3 to maximise freedom, and this blow against DRM will do exactly that. True, free software will have less penetration as a result, but the world will be a freer place for the compromise not being taken.
From a moral angle, this clause allows programmers to restrict how the fruit of their skills is to be exploited, which is naturally within their right, as long as copyright is recognised in law.
Wikileaks, no DNS
If there was one hope for an acceptable DRM solution it was the OS community. Atleast there are still many other good licenses out there that don't ban and entire field of software development.
-Rick
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
First of all, let me state for the record that I loathe DRM.
That said, I'm not sure this is a good idea. What they're saying is that there is absolutely, positively no good use for DRM, and there never will be, in free software.
To me, there's a huge difference between free software and free content, and it seems to me that this stance in GPL3 is essentailly saying that if you want to make the former, you've got to embrace the latter as well. It seems to me that it is forcing developers who would otherwise want to release their software under GPL3 to unnecessarily put restrictions (no DRM) on the content (i.e. the data) that their code may use, and I just can't see that as a good thing. What if Microsoft started programming Word so that you could never save a document that contained profanity? To me, this is pretty much the same thing. It bans the use of digital restrictions on the content? I thought the GPL was about freedom, but now it's imposing some of the very restrictions that it has traditionally railed against!
I've thought for some time that if there were some way for free software to somehow manage to be able to protect DRM'ed content without compromising the freeness of the software code itself, that organizations such as the **AA would be at least a little more willing to work with the community instead of being so hostile. I think that one of the reasons they're so belligerent right now is because even though the open source community is right about a lot of things, they're also generally insistent that the industries give away their content for free. In other words, the two sides are both extremist points of view, with no one willing to meet somewhere in the middle.
This article shows that those who wrote the GPL3 are simply digging in on one of the extremist sides, which will undoubtedly force the content industries to dig in yet further and commit further atrocities to harm consumers. The shame of it is that in the end, it is the users who will suffer. The content is owned by the content industry, after all, and if it is not conducive to them to work within the GPL3, they will simply not work within the GPL3, end of story. That means that all GPL3 software users and developers will forever needlessly be relegated to either continuing to operate within the fringe or living without popular content.
The purpose of the GPL was to prevent lockin not to promote developers.
The idea was born out of the various incompatible UNIX'es which were all proprietary and therefore able to lock people in. Run a Sparc box? Get your OS from Sun. Don't like the OS? Too bad, you can't change it or replace it, etc...
The GPL3 being aggressive against DRM is a sane move I think. As a developer I have a right to license my software as "not for use in Japan" if I wanted. I could just as easily say "not for use with software that uses DRM".
And frankly I don't see anything negative about it. DRM is bullshit anyways, never will protect the producer and only violates the users ability to enjoy the product as they should be able to.
Tom
Someday, I'll have a real sig.
since every drm schemed is eventually going to be hacked, and therefore the protection removed, not only for the ubergeeks but for everyone through file sharing systems. Since current drm imply shady business with the OS (Sony rootkit) and rights restriction (copying music between all the devices you own etc), since DRM has been critized to assume the consumers where outlaws. Then why not make a jump. I'd suggest a DRM system based on a simple RDF file indicating what the user has the right to do with the file... this file is attached to the media content. Sure, it'll be extremely easy to crack, so easy it won't even be fun. Ethic media players would read the file and tell you, this is the 10th time you've read this file. I can't read it anymore you need to buy another lease, or buy the song entirely etc.... Maybe I'm just a dreamer... after all how many sharewares, most of whom where not based on restrictions, just on nag screens after a certain period, where registered? Well maybe it's different for music, I don't know... But after all, the current DRM situation is the same with a little more obfuscation that's it... so why not?
\u262D = \u5350
I have the strong opinion that the word "rights" is being abused significantly by pretty much everyone inside and outside of industry. Rights to education, rights to health care, rights to fair use.
I'm not sure that the word "rights" should be used anymore, the meaning is lost.
To me, rights are something every person is born with -- inherent, God-given, natural, you call it what you want. I believe we are born as human, we have these rights -- American, Afghani, Zimbabwian. I believe the initial U.S. Constitution as very good about naming SOME of the rights that we're born with (no government can tell us what to say, which religion we practice if any, they can not search our body or our house without very specific details laid out to a public witness, they can't quarter troops in our homes, they can't make us testify against ourselves, etc, etc). These rights are the people's, all the people's, and they're not to be abridged by any government. These rights are also ours on our property to modify in respect to others (you have none of these freedoms when you are on my land).
The entire copyright issue is very complex for most people -- many loopholes and priviledges given to some but not others. I don't like unequal rules when they are put in the law. I especially don't like unequal rules that no one can understand with a lawyer. As some know here (and I really don't want to debate it on this forum), I am against copyright in every form -- I believe that once you have a physical item in your hands, you can do with that physical item what you want -- copy it, modify it, call it your own. The physical item is "protected" by inherent property rights as long as the original owner keeps it with him. It is like gold or diamonds. The minute they sell or barter away the physical item, it is now the new owner's item to do with as they please. PHYSICAL property can be protected, but intellectual property is thought, it is action, it is processing, updating and recreating.
Now we get to fair use. First, we the People give government the ability to lay down a monopoly rental to another person or corporation -- copyright. We let them control how we use a specific item, who we use it with, and what we can and can't do. This is a law, with force being used if we ignore it. Then we give "the People" the right to work around this rented monopoly, given some very peculiar reasoning. Copyright was intended to be useful for 7 years (which can be doubled) in order to further the arts -- it was not there to necessarily protect a profit or a demand complete control forever.
This is my big problem with "rights" today -- we can give them up and have to walk a very complicated path, but we also get some parts back in order to try to fix that complicated path but it just ends up being even more complicated.
If you won't agree with me that freedom is better than tyranny, how about you folks who love big government mandate a state-paid lawyer to follow around anyone who wants one, so we can live without the fear of jail or fines?
For those who aren't fond of the changes to the GPL from v.2 to v.3, why not just vet your complaints about v.3 with a structured rebuttal, and then go on developing v.2 software until it's fixed or something better comes along?
Also, there are plenty of "Open-Source" Licences. (MPL, LGPL, BSD, CopyCat, etc.) Is there something the GPL v.3 does that the others (GPL v.2 included) don't do?
-Pope Peter Porker, S.O.W., K.M.K.R., U.G.O.A., F.S.G.S.D.
...you cannot have drm in oss, it just is not possible. if your software can render it, which involves processing the drm (decrypt, etc) then you can remove the drm pretty much just as easily and since the rendering code is there for everyone to see, the is trivial to adjust the app to play to disk.
I'm as much against many of the DRM schemes (and more importantly the way they actually get carried out) as the next person.
That said, I think this is a mistake.
Under GPLv3 can I crate a xen node0 and tie it with hardware DRM so only that hypervisor boots? That's the path to a secure node0?
Could I use DRM type technology to avoid leaking client data I'm required to collect at my place of business?
What people forget is that DRM technology can be used in many ways. To destroy privacy and restrict rights, or to insure privacy and protect rights.
I can think of lots of areas (patents) that the GPL could have been improved / touched-up other than taking the hard DRM line.
I'm reading a bit too much along the lines of "ZOMG no 1 will use teh softwares with GPL3" or "there's politics in my software!".
Here's the dish:
You don't like GPL v3? Don't use it. GPL v2 will still exist. In fact, I'm betting Linux (the kernel) won't ever be available under the GPL v3. I would be happy to use the new GPL since I enjoy such a license. If you don't like the new stuff added in, feel free to use GPL v2 software. More licenses == more choices. I don't see the problem here. BSD and GPL currently co-exist just fine. I'm sure BSD, GPL v2, and GPL v3 will do just the same.
The proposed restriction would affect software for the content encryption only, i.e. the server side of the DRM.
Suppose, someone made a GPL 2 compliant DRMed book reader. The reader comes with the source, so there is no possibility of security through obscurity, the source can be modified and recompiled. In order to read the DRMed content it must be decripted. That means a secret key has to be given to the user, and passed to the reader. The source for the reader is available and can be modified to save the key or the decrypted copy. Consequently, GPL2 is sufficient to make client-side DRM ineffective.
Client-side DRM software, at least in its present form, depends on the closed source software, on obscurity. GPL3 restriction would only affect content creation, the encryption part of the DRM.
Hardware-assisted DRM may be different, but I can't see it right now.
Something we have simply by right of being alive is something we will hold cheaply and assume will always be there, like the air we breathe.
Our rights are not God-given or inherent to ourselves. Nor are they granted to us by the benevolence of our rulers. Our rights were taken from our rulers, by force. Among all our ancestors were rebels and traitors, terrorists and pirates, mutineers and heretics and unionists and blackguards and revolutionaries and blasphemers and barbarians, and it is their struggle that we have to thank for the freedom we enjoy today. They fought against kings and barons, against tycoons and industrialists, against priests and popes, and they set themselves and their descendants free.
When you give up a freedom to the state, or to the establishment, or to the company, you aren't giving up something that is yours to give away that you've had all your life and which you got for nothing. You're giving up something bought by the blood of countless rebels over the centuries. You're betraying the sacrifices made by your ancestors.
A right we think is inalienable we will neglect and soon lose. A right we know was won by our ancestors through hardship and struggle we will defend forcefully.
Real Daleks don't climb stairs - they level the building.
I absolutely hate DRM and believe that the DMCA should be repealed. I also believe there should be laws stating that no one should be able to place digital locks on material that a user has certain rights to which the locks curtail.
However, I really don't know about this change in the GPL. I thought one of the things the GPL wanted to avoid were the extra clauses about what you could and couldn't use the software for. I seem to remember people who would write "free" software with the license almost identical to the GPL but then add things like "No one in the US Military is allowed to use this software." I was under the impression that people who truly wanted Free and Open Source Software to prevail were against these kinds of restrictions...
We always knew Comcast was corrupt, here's the proof: http://tech.slashdot.org/comments.pl?sid=1909890&cid=34545432
To me, rights are something every person is born with -- inherent, God-given, natural, you call it what you want.
The Creator doesn't give anybody any rights. They can't be inalienable because they don't exist. Does the lamb have a right not to be eaten by the lion? The caveman by the bear? The woolly mammoth not to be slain by the caveman? Nope. Quite the contrary. The setup in the natural world is carefully designed or naturally evolved (take your pick) to confer benefit to the strong, the clever, and the ruthless. Everywhere there is competition for scarce resources.
If the whale is to have a right not to be processed by man for food and other products, it can only be because man chooses to confer and protect this right. No deity has ever done so.
The baby born with a heart defect has no right to life conferred by nature or Creator. Without man's interest and intervention, it will die quickly.
If man is to enjoy rights, it can only be because man promulgates and protects these rights.
Knowledge "wants" to be free in a metaphysical sense, but it's not going to happen without the efforts of men to undo the efforts of other men to chain knowledge.
Some of the comments are nonsense like applying this to file permissions. So before you flame the decision, read it. Excerpt from the GPL:
As a free software license, this License intrinsically disfavors technical attempts to restrict users' freedom to copy, modify, and share copyrighted works. Each of its provisions shall be interpreted in light of this specific declaration of the licensor's intent. Regardless of any other provision of this License, no permission is given to distribute covered works that illegally invade users' privacy, nor for modes of distribution that deny users that run covered works the full exercise of the legal rights granted by this License.
In other words: This applies only to DRM that attempts to block copying of copyright material. Not Trusted Computing, not file permissions, not anything else.
Ok?
So.. it has come to this
Well, it's not really a change. In spirit, the GPL has always opposed DRM. DRM, like proprietary software, takes away the control and freedom of choice that an end user should enjoy, and gives it to someone else. The GPL has always stood against the effects of proprietary software, on behalf of programmers and expert users. Now, it stands against those effects on behalf of every computer user too. Companies have an ethical choice when it comes to DRM, and I do hope that the actions of the FSF will serve to highlight this.
You're an immobile computer, remember?
RMS started his crusade long before anyone heard of Microsoft when a printer manufacturer wouldn't give him the source code for a printer driver so he could fix the bugs that were preventing it from working on the computer he was using. RMS is about preventing artificial limits on a computers ability to meet the needs of its users.
Over the years the artificial limits have included the unavailability (hoarding in RMS-speak) of source code and patents. Adding DRM is the next logicial addition.
This is a boring sig
I think it's an issue of enforceability. Freedom is relative given what area of the globe you are in. In the U.S for example we have the right to freely speak against our government, in China that is not a guaranteed right. Therefore by the letter of the law there is nothing that a software license can do about it. Also what's to keep foreign countries from ignoring a U.S. Copyright law or two?
The problem is that a number of companies provide the source code, without actually providing you with enough information to use it.
For example, my TiVo is Linux based, but the hardware has DRM to stop me running binaries I build myself. So even though I have the source, I don't have the freedom to use it.
It's pretty clear that the intent of the GPL was always to make sure users could change and use the software themselves. So this is only strengthening the original intent, by emphasizing that the "and use" part is important.
It's the same concern with DRM on content. A company could sell a media player with DRM and GPL firmware, but the law would prohibit you from modifying the software and using your modified version.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
While I'm against the concrete form choosen in version 3, DRM is a real problem for the GPL, as the DMCA goes against the very spirit of the GPL.
I could use GPLed software and create a DRM program with it. Normally, everybody can modify it, right?
Well, perhaps not : as it is a protection measure, I can try to sue everybody that does modify it under the DMCA, claiming that any modification to my software lessens the protection, and therefor infringes the DMCA (IANAL, so I'm not sure if this could succeed). So, by declaring my software to be a DRM, I could basicly prevent anybody from modifying it.
Worse, not only I, but if it is a general purpose DRM system, any author of content protected by this DRM could sue you if you modify the software.
The DMCA creates a huge mess : normally illegal actions done with software (even if it is modified GPL-software) are, of course, illegal. But with the DMCA, modifying software itself can be illegal, even if no other illegal act is commited (exemple : excercising fair use rights).
So, the GPL would like to say that modifying (and using) GPLed software is never illegal in itself, only if another illegal act is commited.
Why I'm against the form choosen in the GPLv3 : it only adresses the DMCA in it's current form (and even then, I'm not sure, if it will stand up in court), but with a new law, modifying GPLed software can become illegal again. And the licence will always be behind the law.
I have discovered a truly remarkable proof for my post which this sig is too small to contain.
In a society where all are free to keep slaves, the "mean freedom per capita" is likely to be rather less -- especially amongst the poorest members of that society -- that in a society where slavery is forbidden, even although the "freedom" to keep slaves has been infringed across the board.
The GPL is designed to preserve users' freedoms. Closed-source software and obnoxious DRM are basically electronic forms of enslavement. RMS gets this, and says the Four Freedoms of users are more important than the false freedom of developers to dictate terms for the use of their programs. Exactly the way that my freedom to walk down the streets of Britain and know that nobody is carrying a live firearm that could be used against me is more important than some gun nut's freedom to keep lethal weapons just in case civilisation happens to break down. {If and when that ever happens, I know how to make a gun anyway; but it's unlikely enough that I'm not worried about it.}
Je fume. Tu fumes. Nous fûmes!
I think the idea of the DRM-clause is as follows: If someone uses GPL'ed code in DRM'ed product, they are agreeing that the DRM on their product is not a "strong technological protection". What does that mean? It means that they can't use DMCA to sue users who circumvent the DRM. DMCA makes it illegal to circumvent "strong technological protection". If they use GPL'ed code, they are saying that their DRM is not strong, and therefore circumventing that DRM is not against the DMCA.
It's brilliant, really.
Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
There are those who would utterly abolish copyright. To be honest I'm almost in agreement with them. The balance has swung over to absolutely ridiculous extremes.
* Music: Music has existed since the dawn of civilisation. Those who enjoy music enough will continue to produce it whether or not people will pay them handsomely for their efforts. If they no longer make more money in a day than a surgeon in the emergency room makes in a whole year, well, somehow I find it hard to feel sorry for them.
* Software: Some software needs can be met with open source software. More specialist "unsexy" software will again continue to be needed. Whoever needs it enough can enter into a contract with someone to develop it, under as strict a set of safety standards as is necessary for things like aircraft and nuclear reactors if needs be. Isn't the vast majority of all software written for internal use? If this software gives you a critical edge over a competitor it can be protected as a trade secret instead.
* Books: Same as music, even moreso. Anyone with a word processor can potentially be an author, although if you look at the volume of utter drivel on say fanfiction.net it might become a bit hard to sort the wheat from the chaff for a while. Again, better to have geniunely good material float to the top than have the usual pop crap pushed down everyone's throats because it's a lazy man's substitute for taste.
* News: Tricky. "the blogosphere" these days is mostly about juvenile navelgazing, and I personally would certainly not rely on it. Still, if News Corp et all fell into the dust, if something big caught on fire I imagine many people would be giving consistent reports of the fact within minutes online, as opposed to front page articles of who's fucking who in the celebrity world as we usually have (although we wouldn't see quite so many celebrities in the first place; see above).
* Cinema: There are lower barriers to entry these days thanks to powerful commonplace audio/video hardware and the obscene computing power of a medium-sized pile of desktop PC's these days. Still, this could be tricky. You would need some sort of wealthy societies to bankroll massive cinematic productions. You wouldn't get too many projects like Lord of the Rings springing up because a bunch of people down the pub with 1000 of their highly qualified mates decided it might be fun to set up tons of production equipment and render farms down in New Zealand for a laugh...
On balance though I'm having trouble seeing the benefit of copyright other than the fact that it makes a small group of people with an arguably marginal contribution to society disproportionately rich. Considering the recent abuses of the copyright lobby (DMCA and such) we do seem to be making some ridiculous "tradeoffs" as of late.
Unfortunate reality is that DRM is a necessity to many companies. When a studio dumps $100,000,000 into a movie, times 100 movies a year, DRM is going to happen whether us end users like it or not. Total elimination of DRM from a movie studio is not an option; switching from Linux to Windows to keep DRM is an option for them.
... aka GPL3.
As Godel noted, there is an unresolvable issue in every system. As you note, the unresolvable issue in Stallman's GPL3 is the "no DRM anywhere ever" vs. "DRM is a fact of life - cope" vs. "no OSS for you" - pushed to its logical limits, Stallman's ideology makes it untenable in the real world. Getting banned from playing in sandbox A because you play in sandbox B discourages people from playing in B
Can we get a "-1 Wrong" moderation option?
Except users will no longer have the freedom to build DRM software using GPL'd code.
What is the difference between the GPL and the modified BSD license, or the MIT license? Some groups claim that the latter two licenses are more free than the GPL. In one sense, they are correct. The GPL puts certain restrictions on redistribution, whereas the other two licenses put virtually no restrictions.
You are correct that RMS has previously argued that there should be no "anti-suchandsuch" political clauses in the GPL. RMS believes that users should be free to do anything with the software. Thus, your view is correct, but not complete!
In fact, RMS has always stated that users should be free to do anything with the software, except restrict other users' freedom to do anything with the software. That was the whole point of the restrictions in the GPLv2.
When you look at it in this light, you realize that forbidding effective DRM is in fact consistent with the philosophical aims of the GPLv2, because DRM is nothing more than a way of restricting a user's freedom to do whatever he wants with the software. However, this draft of GPLv3 makes this explicit, because DRM-protecting laws like the DMCA have become so dangerous to Free Software.
Furthermore, your basic premise is in fact false. This draft of GPLv3 still allows programmers to write software that encodes or decodes DRM-wrapped file formats. However, this draft of GPLv3 legally defines any such software as not "an effective technological protection measure". These words have a specific legal meaning. The DMCA legally forbids a user from circumventing an effective technological protection measure; as such, if a piece of GPLv2 software implements a DRM-wrapper, it would be illegal under the DMCA to modify the software, even though the GPLv2 otherwise grants you that right. With this draft of the GPLv3, by defining the software legally as not "an effective technological protection measure" the DMCA will never be invoked, and the user is free to excersize his freedom by modifying the software.
The preceding comments reflect the author's personal opinion and are public domain, unless explicitly stated otherwise.
Nothing has changed here. In the past, there would have been an argument in court about this. Now there is no doubt at all. Certain forms of DRM make it impossible for a downstream recipient of the code to legally rebuild a usable version of GPLed software. The DMCA means that the downstream recipient who tries to get around this could be prosecuted for trying to circumvent a technical protection measure. The new formulation in GPLv3 simply clarifies that this is incompatible with the aims of the licence, so if you want to incorporate DRM into someone else's GPLed code, you are acknowledging that your DRM does not constitute a TPM so someone who tries to break it doesn't fall foul of the DMCA. There is a lot of hysteria about this, which is not justified in my opinion. DRM backed by the DMCA was always incompatible with the goals of the GPL. In the past they might have had to go to court to argue that the goals of the licence make it clear that DRM is in violation of licence; after GPLv3 there can be no doubt about this issue and it would not require a trip to court to establish the fact. (I am not a lawyer).
Reality is defined by the maddest person in the room
This is stupid. This impulsive, reactionary move will do nothing but cripple it's usage in any commercial application. Forget about tivo and the millions of titles that have CD-ROM protection through safedisc or macrovision, but this cuts out any possible commercial media delivery to GPL'd software. No iTunes, no DVDs, HD-DVDs, or any of the new wave of on-demand or streaming media. Great idea FSF, why don't you do an encore of punching yourself in the nuts?
People who think they know everything really piss off those of us that actually do.
Basicly, they are saying in GPL v3 that if you release code under GPL v3, you cannot sue someone else for looking at your code and using either the code or the information to read, write, encode, decode, encrypt, decrypt or otherwise work with the data files your code works with.
Meanwhile, a large number of sites, including the popular search engine Google, have been defaced by hackers claiming to come from a team called Micros^H^H^H^H^Hammon.
First, kudo's on your careful quoting, you just don't see that enough on slashdot. Secondly, I guess we're in broad agreement on the key points: total bans against a technology per se is dumb and the GPL v.3 needs to be better worded.
I think though I can imagine non-evil situations where it would be good for even an Administrator to accept 3rd party restrictions on data: for example, a distributed computing project where the 3rd party project mangers wanted to guard against data tampering or duplication. SETI@home solved this problem in other ways, for example by leveraging its huge user base to process blocks multiple times, but you could imagine that DRM might help with that. Or giving researchers limited access to medical data: after an ethics committe approves their project, a research team could be sent a DRM'd copy of $Hospitals complete medical records to data mine, but they can't pass those records on to another unapproved group, except in piecemeal fashion, or perhaps access could be automatically expired at the end of the investigation, reducing the likliehood of a privacy leak.
I guess what I'm trying to say is that even trying to specify non-technical effects and ends might prove horribly difficult and perhaps better suited to other forums, such as legislative efforts, than the GPL.
I think it's also worth noting that at CES, there was a panel of congressmen discussing digital rights issues, all of whom happened to be Republicans, and all of whom seemed to agree the DMCA was flawed, in that it didn't accomodate Fair Use properly, and were thinking about legislative changes, so the GPL v.3 language may end up being moot anyway.
"Just once, I'd like to meet an alien menace that wasn't immune to bullets." -- The Brigadier, Dr. Who