Home Page
02.22.2007 (previous | next)
DRM, the Content Industries, the FSF, & GPLv3

The music and movie industries are busy looking at Steve Jobs' views on Digital Rights Management, but they shouild spare a glance or two toward the Free Software Foundation.

The word on the street is that a new and final draft of the GPLv3 will be released within the next week or so. While several provisions are still under negotiation (sort of -- it is a democratic process in which one player, the FSF, automatically holds a majority of the votes), one that is not is the FSF's unrelenting hostility to any form of DRM. Its purpose is to ensure that no program licensed under the GPL can be used in connection with any DRM program.

The main target here is, of course, Linux. Now, Linus Torvalds holds the licenses on the kernel of Linux, and he is skeptical about these new provisions. And FSF cannot impose anti-DRM provisions retroactively in any case. But the FSF controls many of the programs that surround the kernel in any serious distribution of Linux, and users need access to these and to future tweaks, which can be placed under GPLv3. So Torvalds' power is limited.

But the FSF's power is also limited. The content industries simply cannot afford to renounce their ability to implement forms of DRM in the future. So it is hard to see how Linux will survive as a viable enterprise operating system if this provision remains in the GPLv3. It seems doubtful that big computing services providers could realistically divide their operations to exclude the use of Linux for content clients while using it for others.

As I read the drafts of GPLv3, for example, I don't see how Google couild use GPL'ed code and at the same time implement its promises to install technology to weed out copyright violations. (If I am wrong on this point, I will take correction -- the GPL (any version) is so opaque that claiming a good grasp of its meaning counts as hubris. The relevant language from the last public draft of GPLv3 is set forth below.)

Similarly, it is hard to see how Sun could carry out its rumored plan to use the GPLv3 to license a Solaris kernel that would be surrounded by FSF software in a Linux-substitute. Server farms stocked with machines that cannot process any DRMed movie, TV, or music content? Get real.

Is it possible that Richard Stallman, chief priest of the FSF, is really Steve Ballmer in disguise, working to make Windows the only operating system for all content-related computing?

* GPLv3 draft language:

3. No Denying Users' Rights through Technical Measures.

Regardless of any other provision of this License, no permission is given for modes of conveying that deny users that run covered works the full exercise of the legal rights granted by this License.

No covered work constitutes part of an effective technological "protection" measure under section 1201 of Title 17 of the United States Code. When you convey a covered work, you waive any legal power to forbid circumvention of technical measures that include use of the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing the legal rights of third parties against the work's users.

posted by James DeLong @ 10:19 AM | Free Culture Movement

Link to this Entry | Printer-Friendly | Email a Comment | Post a Comment(2)


Comments

"Its purpose is to ensure that no program licensed under the GPL can be used in connection with any DRM program."

STRAW HORSE ALERT

No you could write a program under another licensed under a different license, and let it do all the DRM you want it to. RMS just wants to make sure that someone couldn't take actually GPL code and make it secret, the way TIVO has done.

Very simply put all the GPL is trying to do is say: Here's this free code, and you can use it without any restrictions, as long as you don't try to place restrictions on this code, or any works derived from this free code.

Torvalds may well come around to liking GPL 3.0 more and more, after Novell.....

Posted by: enigma foundry at February 23, 2007 2:45 AM

"As I read the drafts of GPLv3, for example, I don't see how Google couild use GPL'ed code and at the same time implement its promises to install technology to weed out copyright violations. "

Such a fundamental misunderstanding highlights the idle speculation in this article. No version of the GPL restricts how the covered work is usage. Indeed, short of distribution the license need not even be accepted.

Posted by: Anon Ymous at March 1, 2007 8:44 PM








 
IPcentral WebLog

Blog Main

IPcentral Blogosphere Archives

Search the Blog

Recent Posts
  - IP and Marginal Cost
- Academics and Copyright
- More on Jammie Thomas from DOJ
- More Studies of Downloading
- Facebook, MySpace, and Network Externalities
- Copyright and the University: An Academic Symposium
- Tyler Cowan on Chinese Movie Piracy
- More WHO Antics--Roger Bate Reports
- Patents, Meds, and the Developing World: Clips & Links
- Jermaine Dupri's Gripe with iTunes
Archives by Month
  - December 2007
- November 2007
- October 2007
- September 2007
  - (see all)
Archives by Subject
  - Academia
- Access: Commons, Fair Use, Orphan Works, Public Domain
- Accounting
- Analog Holes
- Antitrust
- Art
- Aspen
- Big Tent
- Biotech
- Books
- Comments from Readers
- Counterfeit
- Digital Americas
- Digital Europe
- Digital Europe 2006
- DMCA
- DRM & Watermarks, etc.
- Economics, Game Theory & Public Choice
- Enforcement & Remedies
- Free Culture Movement
- Games
- General
- Infrastructure
- International
- Internet: P2P, Search Engines...
- Legislation and Legislators
- Liberty and IP
- Markets: Business, Investment & Innovation
- Media: Video, Music...
- Patents
- Pharma
- Physical Property
- Prices, Terms, and Licensing
- Privacy and Security
- Radio
- Software
- Spectrum & Wireless
- Standards
- Supreme Court
- Tax-Funded IP
- Telecom
- Theft of Service
- Universities
Links
 

Site Feed

  - Atom
- RSS 1.0
- RSS 2.0
We welcome comments by email - look for a link to the author's email address in the byline of each post. Please let us know if we may publish your remarks.


 
Home Page