From 7390b7c0f9e667200bb149c57be2a60e62761346 Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Thu, 20 Mar 2014 16:23:20 -0400 Subject: [PATCH] This text was so old (from the earliest drafts) that it was not particularly useful. --- gpl-lgpl.tex | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex index 356d890..85b7787 100644 --- a/gpl-lgpl.tex +++ b/gpl-lgpl.tex @@ -2909,27 +2909,6 @@ limitation or further obligation. % FIXME-LATER: Would be nice to explain much more about interactions between % the various options of GPLv3~\S6(a-e), which might all be in play at once! -% FIXME: update lock-down section to work with more recent drafts - -Though the definition of Complete Corresponding Source Code in the second -paragraph of section 1 is expansive, it is not sufficient to protect users' -freedoms in many circumstances. For example, a GPL'd program, or a modified -version of such a program, might need to be signed with a key or authorized -with a code in order for it to run on a particular machine and function -properly. Similarly, a program that produces digitally-restricted files might -require a decryption code in order to read the output. - -The third paragraph of section 1 addresses this problem by making clear that -Complete Corresponding Source Code includes any such encryption, -authorization, and decryption codes. By requiring the inclusion of this -information whenever the GPL requires distribution of Complete Corresponding -Source Code, we thwart efforts to obstruct the goals of the GPL, and we -ensure that users will remain in control over their own machines. We -recognize an exception where use of the program normally implies that the -user already has the codes. For example, in secure systems a computer owner -might possess any keys needed to run a program, while the distributor of the -program might not have the keys. - % FIXME: installation information??