Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

This text was so old (from the earliest drafts) that it was not particularly useful.

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-20 16:23:20 -04:00
parent 2145ca8186
commit 7390b7c0f9
1 changed files with 0 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
gpl-lgpl.tex
View file

@ -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??