www-commits
[Top][All Lists]
Advanced

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

www/philosophy tivoization.html


From: Ineiev
Subject: www/philosophy tivoization.html
Date: Thu, 23 Mar 2023 08:50:00 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 23/03/23 08:50:00

Modified files:
        philosophy     : tivoization.html 

Log message:
        Validation fix, remove spurious spaces, fix typos.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/tivoization.html?cvsroot=www&r1=1.1&r2=1.2

Patches:
Index: tivoization.html
===================================================================
RCS file: /web/www/www/philosophy/tivoization.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- tivoization.html    23 Mar 2023 10:19:57 -0000      1.1
+++ tivoization.html    23 Mar 2023 12:50:00 -0000      1.2
@@ -9,10 +9,10 @@
   <h2>Tivoization</h2>
   
   <p>There is a paradoxical class of firmware, for which the source code
-    is <a href="https://gnu.org/philosophy/free-sw.html";>free software</a>
+    is <a href="/philosophy/free-sw.html">free software</a>
     because it carries
-    a <a href="https://www.gnu.org/licenses/license-list.html";>free
-      software license,</a> but specific hardware for which these programs
+    a <a href="/licenses/license-list.html">free
+      software license</a>, but specific hardware for which these programs
     are designed renders any binaries produced from that source code
     nonfree in practice. That is because that hardware requires the binary
     to be signed by the hardware manufacturer, either in order to run at
@@ -23,16 +23,16 @@
   <p>While it is still physically possible to replace the released
     binary on the hardware that enforces signatures, it is useless to do
     so, since the hardware would refuse to run it. Therefore, the freedom
-    #1 (one of <a href="https://gnu.org/philosophy/free-sw.html";>the four
+    #1 (one of <a href="/philosophy/free-sw.html">the four
       essential freedoms</a>) is missing, and that binary is not free, even
     though the source code may carry a free software license. Indirectly,
     tivoization affects the other freedoms (to use and to distribute
     modified versions) because any modification of the firmware by
     yourself will result in broken hardware. The binary may qualify as
-    <a href="https://www.gnu.org//philosophy/free-open-overlap.html";> open
-      source,</a> because the term &ldquo;open source&rdquo;
-    <a href="https://www.gnu.org/philosophy/open-source-misses-the-point.html";>
-      is defined in terms of how the source is treated.</a> The publisher or
+    <a href="/philosophy/free-open-overlap.html">open source</a>,
+    because the term &ldquo;open source&rdquo;
+    <a href="/philosophy/open-source-misses-the-point.html">is defined
+    in terms of how the source is treated</a>. The publisher or
     the manufacturer may also advertise this forced signature check as a
     &ldquo;feature&rdquo;.</p>
   
@@ -41,8 +41,8 @@
     protects you and your data. But we should wonder: whom does it
     protect, and from whom? Who is the owner of this lock? Who decides
     what is good or bad software for our own computing? If it is not us,
-    then <a href="https://www.gnu.org/philosophy/loyal-computers.html";>
-      this computer is not loyal.</a></p>
+    then <a href="/philosophy/loyal-computers.html">this computer is not
+    loyal</a>.</p>
   
   <p>The tivoization is a not a security feature, it is a trap for our
     freedoms. It prevents users from upgrading their own hardware or
@@ -53,8 +53,8 @@
   <p>The firmware that drives the hardware at the lowest level also has
     the most control over it. It often contains
     <a href="https://libreboot.org/faq.html#intelme";>backdoors</a> and
-    <a 
href="https://www.gnu.org/proprietary/proprietary-insecurity.html#uefi-rootkit";>
-      vulnerabilities</a> nobody is allowed to fix but the provider trusted by
+    <a 
href="/proprietary/proprietary-insecurity.html#uefi-rootkit">vulnerabilities</a>
+    nobody is allowed to fix but the provider trusted by
     the hardware.</p>
   
   <p>Preventing unsigned or self-signed versions of the firmware to be
@@ -69,17 +69,18 @@
   
   <p>Among the most important additions in the GNU General Public License
     version 3, in 2007, was to prohibit taking a GPLv3-covered program and
-    <a href="https://www.gnu.org/licenses/quick-guide-gplv3.html";>distributing
-      it under tivoization,</a> because it denies users the freedom, in
+    <a href="/licenses/quick-guide-gplv3.html">distributing
+      it under tivoization</a>, because it denies users the freedom, in
     practice, to modify the program and then use the modified version.</p>
   
   <p>As stated by the
-    <a 
href="https://www.gnu.org/distros/free-system-distribution-guidelines.html";>
-      GNU Free System Distribution Guidelines,</a> operating systems which
+    <a href="/distros/free-system-distribution-guidelines.html">GNU Free
+    System Distribution Guidelines</a>, operating systems which
     provide such firmware are not free, whether the upstream source code
     is free or not.</p>
 
 </div> <!-- class="article reduced-width" -->
+</div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
 <div id="footer" role="contentinfo">
 <div class="unprintable">
@@ -136,7 +137,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2023/03/23 10:19:57 $
+$Date: 2023/03/23 12:50:00 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

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