taler-merchant-demos

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

the-root-of-this-problem.html (11165B)


      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 evils" -->
      5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
      6 <title>The Problem Is Software Controlled By Its Developer
      7 - GNU Project - Free Software Foundation</title>
      8 <!--#include virtual="/philosophy/po/the-root-of-this-problem.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>The Problem Is Software Controlled By Its Developer</h2>
     15 
     16 <address class="byline">by Richard Stallman</address>
     17 
     18 <p>
     19 I fully agree with Jonathan Zittrain's conclusion that we should
     20 not abandon general-purpose computers. Alas, I disagree completely
     21 with the path that led him to it. He presents serious security
     22 problems as an intolerable crisis, but I'm not convinced. Then he
     23 forecasts that users will panic in response and stampede toward
     24 restricted computers (which he calls &ldquo;appliances&rdquo;), but there is no
     25 sign of this happening.</p>
     26 
     27 <p>
     28 Zombie machines are a problem, but not a catastrophe. Moreover, far
     29 from panicking, most users ignore the issue. Today, people are indeed
     30 concerned about the danger of phishing (mail and web pages that
     31 solicit personal information for fraud), but using a browsing-only
     32 device instead of a general computer won't protect you from that.</p>
     33 
     34 <p>
     35 Meanwhile, Apple has reported that 25 percent of iPhones have been
     36 unlocked. Surely at least as many users would have preferred an
     37 unlocked iPhone but were afraid to try a forbidden recipe to obtain
     38 it. This refutes the idea that users generally prefer that their
     39 devices be locked.</p>
     40 
     41 <p>
     42 It is true that a general computer lets you run programs designed to
     43 <a href="/proprietary/proprietary.html">spy on you, restrict you, or
     44 even let the developer attack you</a>.  Such programs include KaZaA,
     45 RealPlayer, Adobe Flash Player, Windows Media Player, Microsoft
     46 Windows, and MacOS.  Windows Vista does all three of those things; it
     47 also lets Microsoft change the software without asking, or command it
     48 to permanently cease normal functioning [<a href="#note1">1</a>].</p>
     49 
     50 <p>
     51 But restricted computers are no help, because they present the
     52 same problem for the same reason.</p>
     53 
     54 <p>
     55 The iPhone is designed for remote attack by Apple. When Apple remotely
     56 destroys iPhones that users have unlocked to enable other uses, that
     57 is no better than when Microsoft remotely sabotages Vista. The TiVo is
     58 designed to enforce restrictions on access to the recordings you make,
     59 and reports what you watch. E-book readers such as the Amazon
     60 &ldquo;<a href="/philosophy/why-call-it-the-swindle">Swindle</a>&rdquo;
     61 are designed to stop you from sharing and lending your
     62 books. Features that artificially obstruct use of your data are known
     63 as Digital Restrictions Management (DRM); our protest campaign against
     64 DRM is hosted
     65 at <a href="https://www.defectivebydesign.org/">defectivebydesign.org</a>. (Our
     66 adversaries call DRM &ldquo;Digital Rights Management&rdquo; based on their idea
     67 that restricting you is their right. When you choose a term, you
     68 choose your side.)</p>
     69 
     70 <p>
     71 The nastiest of the common restricted devices are cell phones. They
     72 transmit signals for tracking your whereabouts even when switched
     73 &ldquo;off&rdquo;; the only way to stop this is to take out all the
     74 batteries. Many can also be turned on remotely, for listening,
     75 unbeknownst to you. (The FBI is already taking advantage of this
     76 feature, and the US Commerce Department lists this danger in its
     77 Security Guide.) Cellular phone network companies regularly install
     78 software in users phones, without asking, to impose new usage
     79 restrictions.</p>
     80 
     81 <p>
     82 With a general computer you can escape by rejecting such programs. You
     83 don't have to have KaZaA, RealPlayer, Adobe Flash, Windows Media
     84 Player, Microsoft Windows or MacOS on your computer (I don't). By
     85 contrast, a restricted computer gives you no escape from the software
     86 built into it.</p>
     87 
     88 <p>
     89 The root of this problem, both in general PCs and restricted
     90 computers, is software controlled by its developer. The developer
     91 (typically a corporation) controls what the program does, and prevents
     92 everyone else from changing it. If the developer decides to put in
     93 malicious features, even a master programmer cannot easily remove
     94 them.</p>
     95 
     96 <p>
     97 The remedy is to give the users more control, not less. We must insist
     98 on free/libre software, software that the users are free to change and
     99 redistribute. Free/libre software develops under the control of its
    100 users: if they don't like its features, for whatever reason, they can
    101 change them. If you're not a programmer, you still get the benefit of
    102 control by the users. A programmer can make the improvements you would
    103 like, and publish the changed version. Then you can use it too.</p>
    104 
    105 <p>
    106 With free/libre software, no one has the power to make a malicious
    107 feature stick. Since the source code is available to the users,
    108 millions of programmers are in a position to spot and remove the
    109 malicious feature and release an improved version; surely someone will
    110 do it. Others can then compare the two versions to verify
    111 independently which version treats users right. As a practical fact,
    112 free software is generally free of designed-in malware.</p>
    113 
    114 <p>
    115 Many people do acquire restricted devices, but not for motives of
    116 security. Why do people choose them?</p>
    117 
    118 <p>
    119 Sometimes it is because the restricted devices are physically
    120 smaller. I edit text all day (literally) and I find the keyboard and
    121 screen of a laptop well worth the size and weight. However, people who
    122 use computers differently may prefer something that fits in a
    123 pocket. In the past, these devices have typically been restricted, but
    124 they weren't chosen for that reason.</p>
    125 
    126 <p>
    127 Now they are becoming less restricted. In fact, the OpenMoko cell
    128 phone features a main computer running entirely free/libre software,
    129 including the GNU/Linux operating system normally used on PCs and
    130 servers.</p>
    131 
    132 <p>
    133 A major cause for the purchase of some restricted computers is
    134 financial sleight of hand. Game consoles, and the iPhone, are sold for
    135 an unsustainably low price, and the manufacturers subsequently charge
    136 when you use them. Thus, game developers must pay the game console
    137 manufacturer to distribute a game, and they pass this cost on to the
    138 user. Likewise, AT&amp;T pays Apple when an iPhone is used as a
    139 telephone. The low up-front price misleads customers into thinking
    140 they will save money.</p>
    141 
    142 <p>
    143 If we are concerned about the spread of restricted computers, we
    144 should tackle the issue of the price deception that sells them.
    145 If we are concerned about malware, we should insist on free
    146 software that gives the users control.</p>
    147 <div class="column-limit"></div>
    148 
    149 <h3 class="footnote">Postnote</h3>
    150 
    151 <p>
    152 Zittrain's suggestion to reduce the statute of limitations on software
    153 patent lawsuits is a tiny step in the right direction, but it is much
    154 easier to solve the whole problem. Software patents are an
    155 unnecessary, artificial danger imposed on all software developers and
    156 users in the US. Every program is a combination of many methods and
    157 techniques&mdash;thousands of them in a large program. If patenting these
    158 methods is allowed, then hundreds of those used in a given program are
    159 probably patented. (Avoiding them is not feasible; there may be no
    160 alternatives, or the alternatives may be patented too.) So the
    161 developers of the program face hundreds of potential lawsuits from
    162 parties unknown, and the users can be sued as well.</p>
    163 
    164 <p>
    165 The complete, simple solution is to eliminate patents from the field
    166 of software. Since the patent system is created by statute,
    167 eliminating patents from software will be easy given sufficient
    168 political
    169 will. (See <a href="https://endsoftwarepatents.org">End Software Patents</a>.)</p>
    170 
    171 <h3 class="footnote">Footnote</h3>
    172 <ol>
    173 <li id="note1">Windows Vista initially had a &ldquo;kill switch&rdquo; with
    174 which Microsoft could remotely command the computer to stop
    175 functioning.  Microsoft
    176 subsequently <a href="https://badvista.fsf.org/blog/windows-genuine-disadvantage/">removed
    177 this</a>, ceding to public pressure, but reserved the
    178 &ldquo;right&rdquo; to put it back in.</li>
    179 </ol>
    180 </div>
    181 
    182 </div><!-- for id="content", starts in the include above -->
    183 <!--#include virtual="/server/footer.html" -->
    184 <div id="footer" role="contentinfo">
    185 <div class="unprintable">
    186 
    187 <p>Please send general FSF &amp; GNU inquiries to
    188 <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
    189 There are also <a href="/contact/">other ways to contact</a>
    190 the FSF.  Broken links and other corrections or suggestions can be sent
    191 to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
    192 
    193 <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
    194         replace it with the translation of these two:
    195 
    196         We work hard and do our best to provide accurate, good quality
    197         translations.  However, we are not exempt from imperfection.
    198         Please send your comments and general suggestions in this regard
    199         to <a href="mailto:web-translators@gnu.org">
    200         &lt;web-translators@gnu.org&gt;</a>.</p>
    201 
    202         <p>For information on coordinating and contributing translations of
    203         our web pages, see <a
    204         href="/server/standards/README.translations.html">Translations
    205         README</a>. -->
    206 Please see the <a
    207 href="/server/standards/README.translations.html">Translations
    208 README</a> for information on coordinating and contributing translations
    209 of this article.</p>
    210 </div>
    211 
    212 <!-- Regarding copyright, in general, standalone pages (as opposed to
    213      files generated as part of manuals) on the GNU web server should
    214      be under CC BY-ND 4.0.  Please do NOT change or remove this
    215      without talking with the webmasters or licensing team first.
    216      Please make sure the copyright date is consistent with the
    217      document.  For web pages, it is ok to list just the latest year the
    218      document was modified, or published.
    219      
    220      If you wish to list earlier years, that is ok too.
    221      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
    222      years, as long as each year in the range is in fact a copyrightable
    223      year, i.e., a year in which the document was published (including
    224      being publicly visible on the web or in a revision control system).
    225      
    226      There is more detail about copyright years in the GNU Maintainers
    227      Information document, www.gnu.org/prep/maintain. -->
    228 
    229 <p>Copyright &copy; 2008, 2010, 2014, 2021 Richard Stallman</p>
    230 
    231 <p>This page is licensed under a <a rel="license"
    232 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
    233 Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
    234 
    235 <!--#include virtual="/server/bottom-notes.html" -->
    236 
    237 <p class="unprintable">Updated:
    238 <!-- timestamp start -->
    239 $Date: 2021/10/01 10:55:57 $
    240 <!-- timestamp end -->
    241 </p>
    242 </div>
    243 </div><!-- for class="inner", starts in the banner include -->
    244 </body>
    245 </html>