www/proprietary proprietary-back-doors.html

[Ineiev]

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 19/01/19 04:09:34

Modified files:
        proprietary    : proprietary-back-doors.html 

Log message:
        Reword definition of back door RT #1292410.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-back-doors.html?cvsroot=www&r1=1.81&r2=1.82

Patches:
Index: proprietary-back-doors.html
===================================================================
RCS file: /web/www/www/proprietary/proprietary-back-doors.html,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -b -r1.81 -r1.82
--- proprietary-back-doors.html 5 Jan 2019 11:06:21 -0000       1.81
+++ proprietary-back-doors.html 19 Jan 2019 09:09:34 -0000      1.82
@@ -1,5 +1,5 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.86 -->
+<!-- Parent-Version: 1.87 -->
 <!-- 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                   Please do not edit <ul class="blurbs">!
@@ -22,9 +22,9 @@
 basic injustice</a>. The developers often exercise that power to the
 detriment of the users they ought to serve.</p>
 
-<p>We say a program has a &ldquo;back door&ldquo; when someone who is
-not supposed to be in control of the computer where it is installed
-can send it commands via some other channel.</p>
+<p>A &ldquo;back door&rdquo; in a program is a channel designed
+to send the program commands from someone who is not supposed
+to be in control of the computer where the program is installed.</p>
 
 <p>Here are examples of demonstrated back doors in proprietary software.
 They are sorted out according to what they are known to allow. Back doors
@@ -568,7 +568,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2019/01/05 11:06:21 $
+$Date: 2019/01/19 09:09:34 $
 <!-- timestamp end -->
 </p>
 </div>