taler-merchant-demos

Python-based Frontends for the Demonstration Web site
Log | Files | Refs | Submodules | README | LICENSE

opposing-drm.html (9808B)


      1 <!--#include virtual="/server/header.html" -->
      2 <!-- Parent-Version: 1.96 -->
      3 <!-- This page is derived from /server/standards/boilerplate.html -->
      4 <!--#set var="TAGS" value="essays cultural drm" -->
      5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
      6 <title>Opposing Digital Rights Mismanagement
      7 - GNU Project - Free Software Foundation</title>
      8 <!--#include virtual="/philosophy/po/opposing-drm.translist" -->
      9 <!--#include virtual="/server/banner.html" -->
     10 <!--#include virtual="/philosophy/ph-breadcrumb.html" -->
     11 <!--GNUN: OUT-OF-DATE NOTICE-->
     12 <!--#include virtual="/server/top-addendum.html" -->
     13 <div class="article reduced-width">
     14 <h2>Opposing Digital Rights Mismanagement<br />
     15 <span style="font-size: .7em">(Or Digital Restrictions Management, as we now call it)</span></h2>
     16 
     17 <address class="byline">by <a href="https://www.stallman.org/">Richard
     18 Stallman</a></address>
     19 
     20 <p>In 1989, in a very different world, I wrote the first version of the GNU
     21 General Public License, a license that gives computer users freedom. The
     22 GNU GPL, of all the free software licenses, is the one that most fully
     23 embodies the values and aims of the free software movement, by ensuring
     24 the four fundamental freedoms for every user. These are freedoms to 0)
     25 run the program as you wish; 1) study the source code and change it to
     26 do what you wish; 2) make and distribute copies, when you wish; 3) and
     27 distribute modified versions, when you wish.
     28 </p>
     29 <p>
     30 Any license that grants these freedoms is a free software license. The
     31 GNU GPL goes further: it protects these freedoms for all users of all
     32 versions of the program by forbidding middlemen from stripping them off.
     33 Most components of the GNU/Linux operating system, including the Linux
     34 component that was made free software in 1992, are licensed under GPL
     35 version 2, released in 1991. Now, with legal advice from Professor Eben
     36 Moglen, I am designing version 3 of the GNU GPL.
     37 </p>
     38 <p>
     39 GPLv3 must cope with threats to freedom that we did not imagine in
     40 1989.  The coming generation of computers, and many products with
     41 increasingly powerful embedded computers, are being turned against us
     42 by their manufacturers before we buy them&mdash;they are designed to
     43 restrict what we can use them to do.
     44 </p>
     45 
     46 <div class="announcement comment" role="complementary"><p>
     47 <a href="https://www.defectivebydesign.org">Join our campaign against DRM</a>.
     48 </p></div>
     49 
     50 <p>
     51 First, there was the TiVo. People may think of it as an appliance to
     52 record TV programs, but it contains a real computer running a GNU/Linux
     53 system. As required by the GPL, you can get the source code for the
     54 system. You can change the code, recompile and install it. But once you
     55 install a changed version, the TiVo won't run at all, because of a
     56 special mechanism designed to sabotage you. Freedom No. 1, the freedom
     57 to change the software to do what you wish, has become a sham.
     58 </p>
     59 <p>
     60 Then came Treacherous Computing, promoted as &ldquo;Trusted
     61 Computing,&rdquo; meaning that companies can &ldquo;trust&rdquo; your
     62 computer to obey them instead of you. It enables network sites to tell
     63 which program you are running; if you change the program, or write
     64 your own, they will refuse to talk to you. Once again, freedom No. 1
     65 becomes a sham.
     66 </p>
     67 <p>
     68 Microsoft has a scheme, originally called Palladium, that enables an
     69 application program to &ldquo;seal&rdquo; data so that no other
     70 program can access it. If Disney distributes movies this way, you'll
     71 be unable to exercise your legal rights of fair use and de minimis
     72 use. If an application records your data this way, it will be the
     73 ultimate in vendor lock-in. This too destroys freedom No. 1; if
     74 modified versions of a program cannot access the same data, you can't
     75 really change the program to do what you wish. Something like
     76 Palladium is planned for a coming version of Windows.
     77 </p>
     78 <p>
     79 AACS, the &ldquo;Advanced Access Content System,&rdquo; promoted by
     80 Disney, IBM, Microsoft, Intel, Sony, and others, aims to restrict use
     81 of HDTV recordings&mdash;and software&mdash;so they can't be used
     82 except as these companies permit. Sony was caught last year installing
     83 a &ldquo;rootkit&rdquo; into millions of people's computers, and not
     84 telling them how to remove it. Sony has learned its lesson: it will
     85 install the &ldquo;rootkit&rdquo; in your computer before you get it,
     86 and you won't be able to remove it.  This plan explicitly requires
     87 devices to be &ldquo;robust&rdquo;&mdash;meaning you cannot change
     88 them. Its implementors will surely want to include GPL-covered
     89 software, trampling freedom No. 1. This scheme should get
     90 &ldquo;AACSed,&rdquo; and <a
     91 href="https://web.archive.org/web/20140217075603/http://bluraysucks.com/">
     92 a boycott of HD DVD and Blu-ray has already been announced</a>.
     93 </p>
     94 <p>
     95 Allowing a few businesses to organize a scheme to deny our freedoms for
     96 their profit is a failure of government, but so far most of the world's
     97 governments, led by the U.S., have acted as paid accomplices rather than
     98 policemen for these schemes. The copyright industry has promulgated its
     99 peculiar ideas of right and wrong so vigorously that some readers may
    100 find it hard to entertain the idea that individual freedom can trump
    101 their profits.
    102 </p>
    103 
    104 <p>Facing these threats to our freedom, what should the free software
    105 community do? Some say we should give in and accept the distribution
    106 of our software in ways that don't allow modified versions to
    107 function, because this will make our software more popular. Some refer
    108 to free software as &ldquo;open source,&rdquo; that being the slogan
    109 of an amoral approach to the matter, which cites powerful and reliable
    110 software as the highest goals.  If we allow companies to use our
    111 software to restrict us, this &ldquo;open source DRM&rdquo; could help
    112 them restrict us more powerfully and reliably.  Those who wield the
    113 power could benefit by sharing and improving the source code of the
    114 software they use to do so. We too could read that source
    115 code&mdash;read it and weep, if we can't make a changed version
    116 run. For the goals of freedom and community&mdash;the goals of the
    117 free software movement&mdash;this concession would amount to failure.
    118 </p>
    119 <p>
    120 We developed the GNU operating system so that we could control our own
    121 computers, and cooperate freely in using them in freedom. To seek
    122 popularity for our software by ceding this freedom would defeat the
    123 purpose; at best, we might flatter our egos. Therefore we have designed
    124 version 3 of the GNU GPL to uphold the user's freedom to modify the
    125 source code and put modified versions to real use.
    126 </p>
    127 <p>
    128 The debate about the GPL v3 is part of a broader debate about DRM versus
    129 your rights. The motive for DRM schemes is to increase profits for those
    130 who impose them, but their profit is a side issue when millions of
    131 people's freedom is at stake; desire for profit, though not wrong in
    132 itself, cannot justify denying the public control over its technology.
    133 Defending freedom means thwarting DRM.
    134 </p>
    135 
    136 <div class="infobox extra" role="complementary">
    137 <p>First published by <cite>BusinessWeek Online</cite>.</p>
    138 </div>
    139 </div>
    140 
    141 </div><!-- for id="content", starts in the include above -->
    142 <!--#include virtual="/server/footer.html" -->
    143 <div id="footer" role="contentinfo">
    144 <div class="unprintable">
    145 
    146 <p>Please send general FSF &amp; GNU inquiries to
    147 <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
    148 There are also <a href="/contact/">other ways to contact</a>
    149 the FSF.  Broken links and other corrections or suggestions can be sent
    150 to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
    151 
    152 <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
    153         replace it with the translation of these two:
    154 
    155         We work hard and do our best to provide accurate, good quality
    156         translations.  However, we are not exempt from imperfection.
    157         Please send your comments and general suggestions in this regard
    158         to <a href="mailto:web-translators@gnu.org">
    159         &lt;web-translators@gnu.org&gt;</a>.</p>
    160 
    161         <p>For information on coordinating and contributing translations of
    162         our web pages, see <a
    163         href="/server/standards/README.translations.html">Translations
    164         README</a>. -->
    165 Please see the <a
    166 href="/server/standards/README.translations.html">Translations
    167 README</a> for information on coordinating and contributing translations
    168 of this article.</p>
    169 </div>
    170 
    171 <!-- Regarding copyright, in general, standalone pages (as opposed to
    172      files generated as part of manuals) on the GNU web server should
    173      be under CC BY-ND 4.0.  Please do NOT change or remove this
    174      without talking with the webmasters or licensing team first.
    175      Please make sure the copyright date is consistent with the
    176      document.  For web pages, it is ok to list just the latest year the
    177      document was modified, or published.
    178      
    179      If you wish to list earlier years, that is ok too.
    180      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
    181      years, as long as each year in the range is in fact a copyrightable
    182      year, i.e., a year in which the document was published (including
    183      being publicly visible on the web or in a revision control system).
    184      
    185      There is more detail about copyright years in the GNU Maintainers
    186      Information document, www.gnu.org/prep/maintain. -->
    187 
    188 <p>Copyright &copy; 2006, 2021 Richard Stallman</p>
    189 
    190 <p>This page is licensed under a <a rel="license"
    191 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
    192 Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
    193 
    194 <!--#include virtual="/server/bottom-notes.html" -->
    195 
    196 <p class="unprintable">Updated:
    197 <!-- timestamp start -->
    198 $Date: 2021/09/19 16:26:24 $
    199 <!-- timestamp end -->
    200 </p>
    201 </div>
    202 </div><!-- for class="inner", starts in the banner include -->
    203 </body>
    204 </html>