www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/server/staging/proprietary proprietary.html


From: Therese Godefroy
Subject: www/server/staging/proprietary proprietary.html
Date: Tue, 2 Oct 2018 16:35:10 -0400 (EDT)

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 18/10/02 16:35:10

Modified files:
        server/staging/proprietary: proprietary.html 

Log message:
        Reformat the toc; add explanations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/proprietary/proprietary.html?cvsroot=www&r1=1.2&r2=1.3

Patches:
Index: proprietary.html
===================================================================
RCS file: /webcvs/www/www/server/staging/proprietary/proprietary.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- proprietary.html    23 Sep 2018 21:05:07 -0000      1.2
+++ proprietary.html    2 Oct 2018 20:35:09 -0000       1.3
@@ -1,4 +1,4 @@
-<!--#include virtual="/server/header.html" -->
+<!--#include virtual="/server/html5-header.html" -->
 <!-- Parent-Version: 1.84 -->
 <!-- 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -12,19 +12,28 @@
 div.companies { float: right; margin-bottom: .5em; }
 div.malfunctions { max-width: 27em; }
 <!--
-.button { float: left; margin: 0 .5em; }
+.button { float: left; margin: .5em; }
 .button a { display: inline-block; }
+
+div.toc ol { margin-bottom: 0; }
+div.toc ul li { list-style: none; margin-right: 1em; }
+div.toc ol li { margin: .5em 1em 0; }
 div.toc h3 {
-   text-align: left;
    font-size: 1.2em;
-   padding: 0 .83em;
-   margin: .5em 1.5% 1em;
-}
-div.toc li { list-style: none; margin-bottom: 1em; }
-div.toc p { margin: 0 3%; }
-div.toc { margin-top: 1em; }
 
---></style>
+   padding: .8em .83em 0;
+   margin: 0 1.5% 1em;
+}
+.toc h3 span { font-weight: normal; }
+.list { padding-bottom: .5em; }
+.toc .left, .toc .left .list { float: left; }
+.toc .right, .toc .right .list { float: right; }
+div.toc .right h3,
+ div.toc .right ul {text-align: right; }
+-->
+.toc .left {  width: 55%; }
+.toc .right { width: 45%; }
+</style>
 <!--#include virtual="/server/banner.html" -->
 <h2>Proprietary Software Is Often Malware</h2>
 
@@ -55,56 +64,88 @@
 it is standard practice.  Modern proprietary software is typically
 a way to be had.</p>
 
-<p>As of September, 2018, the files in this directory list over 350
-instances of malicious functionalities, but there are surely thousands
-more we don't know about.</p>
+<p>As of September, 2018, the pages in this directory list nearly 350
+instances of malicious functionalities (with close to 400 references to
+back them up), but there are surely thousands more we don't know about.</p>
 
 <div class="toc" id="TOC">
-<div class="companies">
-<h3>Company or type of product</h3>
-<ul>
- <li><a href="/proprietary/malware-adobe.html">Adobe Malware</a></li>
- <li><a href="/proprietary/malware-apple.html">Apple Malware</a></li>
- <li><a href="/proprietary/malware-amazon.html">Amazon Malware</a></li>
- <li><a href="/proprietary/malware-google.html">Google Malware</a></li>
- <li><a href="/proprietary/malware-microsoft.html">Microsoft Malware</a></li>
- <li><a href="/proprietary/malware-appliances.html">Malware in 
appliances</a></li>
- <li><a href="/proprietary/malware-cars.html">Malware in cars</a></li>
- <li><a href="/proprietary/malware-games.html">Malware in games</a></li>
- <li><a href="/proprietary/malware-mobiles.html">Malware in mobile 
devices</a></li>
- <li><a href="/proprietary/malware-webpages.html">Malware in webpages</a></li>
-</ul>
-</div>
-
-<div class="malfunctions">
-<h3>Type&nbsp;of&nbsp;malware</h3>
+<div class="left">
+<div class="list">
+<h3>Injustices</h3>
 <ul>
- <li><a href="/proprietary/proprietary-back-doors.html">Back doors</a></li>
  <li><a href="/proprietary/proprietary-censorship.html">Censorship</a></li>
  <li><a href="/proprietary/proprietary-coverups.html">Coverups</a></li>
  <li><a href="/proprietary/proprietary-deception.html">Deception</a></li>
- <li><a href="/proprietary/proprietary-drm.html">Digital restrictions
-    management</a>&nbsp;(1)</li>
  <li><a 
href="/proprietary/proprietary-incompatibility.html">Incompatibility</a></li>
  <li><a href="/proprietary/proprietary-insecurity.html">Insecurity</a></li>
  <li><a href="/proprietary/proprietary-interference.html">Interference</a></li>
- <li><a href="/proprietary/proprietary-jails.html">Jails</a>&nbsp;(2)</li>
  <li><a href="/proprietary/proprietary-sabotage.html">Sabotage</a></li>
- <li><a 
href="/proprietary/proprietary-subscriptions.html">Subscriptions</a></li>
  <li><a href="/proprietary/proprietary-surveillance.html">Surveillance</a></li>
- <li><a href="/proprietary/proprietary-tethers.html">Tethers</a>&nbsp;(3)</li>
- <li><a href="/proprietary/proprietary-tyrants.html">Tyrants</a>&nbsp;(4)</li>
- <li><a href="/proprietary/potential-malware.html">Potential Malware</a></li>
 </ul>
 </div>
-
-<p>(1) Digital restrictions management, or &ldquo;DRM&rdquo;: functionalities
-designed to restrict what users can do with the data in their computers.<br />
-   (2) Jails: systems that impose censorship on application programs.<br />
-   (3) Tethers: functionalities that require permanent (or very frequent)
-connection to a server.<br />
-   (4) Tyrants: systems that reject any operating system not
-&ldquo;authorized&rdquo; by the manufacturer.</p>
+<div class="list">
+<h3>Techniques&nbsp;<span>(1)</span></h3>
+<ul>
+ <li><a href="/proprietary/proprietary-back-doors.html">Back 
doors</a>&nbsp;(2)</li>
+ <li><a href="/proprietary/proprietary-drm.html">DRM</a>&nbsp;(3)</li>
+ <li><a href="/proprietary/proprietary-jails.html">Jails</a>&nbsp;(4)</li>
+ <li><a 
href="/proprietary/proprietary-subscriptions.html">Subscriptions</a></li>
+ <li><a href="/proprietary/proprietary-tethers.html">Tethers</a>&nbsp;(5)</li>
+ <li><a href="/proprietary/proprietary-tyrants.html">Tyrants</a>&nbsp;(6)</li>
+ <li><a href="/proprietary/potential-malware.html">New developments</a></li>
+</ul>
+</div>
+</div>
+<div class="right">
+<div class="list">
+<h3>Companies</h3>
+<ul>
+ <li><a href="/proprietary/malware-adobe.html">Adobe</a></li>
+ <li><a href="/proprietary/malware-amazon.html">Amazon</a></li>
+ <li><a href="/proprietary/malware-apple.html">Apple</a></li>
+ <li><a href="/proprietary/malware-google.html">Google</a></li>
+ <li><a href="/proprietary/malware-microsoft.html">Microsoft</a></li>
+</ul>
+</div> 
+<div class="list">
+<h3>Products</h3>
+<ul>
+ <li><a href="/proprietary/malware-appliances.html">Appliances</a></li>
+ <li><a href="/proprietary/malware-cars.html">Cars</a></li>
+ <li><a href="/proprietary/malware-games.html">Games</a></li>
+ <li><a href="/proprietary/malware-mobiles.html">Mobiles</a></li>
+ <li><a href="/proprietary/malware-webpages.html">Webpages</a></li>
+</ul>
+</div>
+</div>
+<div style="clear:both"></div>
+<hr />
+<ol>
+<li>These are only a few of the techniques that are used to turn proprietary
+software into malware. Each one implies one or more types of injustice. Back
+doors mean insecurity (and surveillance, most often), tethers imply
+surveillance and insecurity, jails and tyrants are instruments of censorship,
+DRM does censorship and/or sabotage, and subscriptions imply interference.
+We don't list each example of malware in all the categories it
+belongs&nbsp;to.</li>
+
+<li><em>Back door:</em>&nbsp; any mechanism that allows modifying files in
+a computer without the user being aware of it and willing to do the
+modification, whether this mechanism is documented or not. 
+
+<li><em>Digital restrictions management, or &ldquo;DRM&rdquo;:</em>&nbsp;
+functionalities designed to restrict what users can do with the data in their
+computers.</li>
+
+<li><em>Jails:</em>&nbsp; systems that impose censorship on application
+programs.</li>
+
+<li><em>Tethers:</em>&nbsp; functionalities that require permanent (or very
+frequent) connection to a server.</li>
+
+<li><em>Tyrants:</em>&nbsp; systems that reject any operating system not
+&ldquo;authorized&rdquo; by the manufacturer.</li>
+</ol>
 </div>
 
 <p>Users of proprietary software are defenseless against these forms
@@ -117,7 +158,29 @@
 
 <h3 id="latest">Latest additions</h3>
 
-<ul>
+<ul class="blurbs">
+<!-- INSERT latest -->
+  <li id="M201809260">
+    <p>Honeywell's &ldquo;smart&rdquo; thermostats communicate
+    only through the company's server. They have
+    all the nasty characteristics of such devices: <a
+    
href="https://www.businessinsider.com/honeywell-iot-thermostats-server-outage-2018-9";>
+    surveillance, and danger of sabotage</a> (of a specific user, or of
+    all users at once), as well as the risk of an outage (which is what
+    just happened).</p>
+
+    <p>In addition, setting the desired temperature requires running
+    nonfree software. With an old-fashioned thermostat, you can do it
+    using controls right on the thermostat.</p>
+  </li>
+
+  <li id="M201809240">
+    <p>Researchers have discovered how to <a
+    
href="http://news.rub.de/english/press-releases/2018-09-24-it-security-secret-messages-alexa-and-co";>
+    hide voice commands in other audio</a>, so that people cannot hear
+    them, but Alexa and Siri can.</p>
+  </li>
+
   <li id="M201809140">
     <p>Android has a <a
     
href="https://www.theverge.com/platform/amp/2018/9/14/17861150/google-battery-saver-android-9-pie-remote-settings-change";>
@@ -203,7 +266,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2018/09/23 21:05:07 $
+$Date: 2018/10/02 20:35:09 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]