Label section and link it up to other mentions of DRM
This commit is contained in:
parent
ed8fb5a938
commit
0be18ce192
1 changed files with 2 additions and 1 deletions
|
@ -514,7 +514,7 @@ available to subjugate users. For example:
|
|||
\item Digital Restrictions Management (usually called \defn{DRM}) is often
|
||||
used to impose technological restrictions on users' ability to exercise
|
||||
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
|
||||
software source code (read by humans), from their compiled binaries (read
|
||||
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).
|
||||
|
||||
\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
|
||||
most hotly debated during the GPLv3 process. FSF's views on this were sadly
|
||||
|
|
Loading…
Reference in a new issue