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

Label section and link it up to other mentions of DRM

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-20 09:27:02 -04:00
parent ed8fb5a938
commit 0be18ce192
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
gpl-lgpl.tex
View file

@ -514,7 +514,7 @@ available to subjugate users. For example:
\item Digital Restrictions Management (usually called \defn{DRM}) is often \item Digital Restrictions Management (usually called \defn{DRM}) is often
used to impose technological restrictions on users' ability to exercise used to impose technological restrictions on users' ability to exercise
software freedom that they might otherwise be granted\footnote{See software freedom that they might otherwise be granted\footnote{See
\S~\ref{GPLv3s3} for more information on how GPL deals with this issue.}. \S~\ref{GPLv3-drm} for more information on how GPL deals with this issue.}.
The simplest (and perhaps oldest) form of DRM, of course, is separating The simplest (and perhaps oldest) form of DRM, of course, is separating
software source code (read by humans), from their compiled binaries (read software source code (read by humans), from their compiled binaries (read
only by computers). Furthermore, only by computers). Furthermore,
@ -2575,6 +2575,7 @@ way --- through its automatic licensing provision found in GPLv3\~S10 (which
is discussed in more detail in \S\~ref{GPLv3s10} of this tutorial). is discussed in more detail in \S\~ref{GPLv3s10} of this tutorial).
\section{GPLv3's views on DRM and Device Lock-Down} \section{GPLv3's views on DRM and Device Lock-Down}
\label{GPLv3-drm}
The issues of DRM, device lock-down and encryption key disclosure were the The issues of DRM, device lock-down and encryption key disclosure were the
most hotly debated during the GPLv3 process. FSF's views on this were sadly most hotly debated during the GPLv3 process. FSF's views on this were sadly