Minor stylistic updates, clarifies instruction, brings v1.0

Makefile

@@ -1,12 +1,9 @@
-FILES= 			drm.tex aims.tex literature.tex drm.bib
-
-USE_LATEXMK= 	yes
-USE_BIBLATEX= 	yes
-
 .PHONY: all
 all: drm.pdf
 
-drm.pdf: ${FILES} llncs
+SRC=	drm.tex aims.tex literature.tex drm.bib
+
+drm.pdf: ${SRC} llncs
 
 .PHONY: clean
 clean: clean-drm

drm-content.tex

@@ -1,4 +1,4 @@
-\title{Trusted Computing}
+\title{Lab: Trusted Computing}
 \subtitle{Execution in a system controlled by the adversary}
 \author{%
   Daniel Bosk
@@ -19,12 +19,12 @@ \section{Introduction}
 A possible solution to this problem is to introduce a hardware module as 
 support.
 One such module is the \ac{TPM}, which was introduced in a cooperation between 
-Microsoft, Intel, IBM, HP, and Compaq \cite{Anderson2008sea}.
+Microsoft, Intel, IBM, HP, and Compaq~\cite{Anderson2008sea}.
 Their purpose for that was to support \ac{DRM}.
 A newer development in this area is the UEFI secure boot, functionality 
 utilized by the latest versions of Microsoft Windows, where the hardware 
 refuses to boot the operating system if it is not cryptographically signed by 
-a given key \cite{WinUEFIboot}.
+a given key~\cite{WinUEFIboot}.
 This way they can guarantee that the boot loader is not modified, the boot 
 loader can further verify the rest of the operating system.
 Since the operating system is guaranteed to be unmodified, correct operation 
@@ -47,10 +47,9 @@ \subsection{Aim}
 
 The next section covers what you must read before you understand this 
 assignment and how to do the work.
-Section \ref{sec:tasks} covers the work to be done, i.e.~how you should learn 
-this.
-Section \ref{sec:exam} covers how it will be examined, i.e.~how you show that 
-you have fulfilled the intended learning outcomes given above.
+\Cref{sec:tasks} covers the work to be done, i.e.~how you should learn this.
+\Cref{sec:exam} covers how it will be examined, i.e.~how you show that you have 
+fulfilled the intended learning outcomes given above.
 
 
 \section{Theory}
@@ -62,12 +61,15 @@ \section{Assignment}
 \label{sec:tasks}
 There is a program with a very simple \ac{DRM} found in URL
 \begin{center}
-  \url{https://github.com/dbosk/drmlab/releases/download/legacy/cpager-drm}.
+  \url{https://github.com/OpenSecEd/drmlab/releases/download/v1.0/cpager-drm}.
 \end{center}
 It is an ELF 64-bit LSB executable (x86-64, dynamically linked, stripped) for 
 a GNU/Linux system.
-(This same program happens to have its source code published under 
-a BSD-license without any \ac{DRM} on the same server.)
+You can find the instruction for how to you the program (without \ac{DRM}) in 
+Sect.~4.1 (specifically List.~1 and 2) of the document at URL\@:
+\begin{center}
+  \url{https://github.com/dbosk/opsys/releases/download/v1.0/labs-paging.pdf}.
+\end{center}
 The first part of this assignment is to break that \ac{DRM}.
 This will be solved together during a full-class hackathon in the computer lab.
 There will be a projector with the code for all to see, then we will rotate who 
@@ -104,4 +106,4 @@ \subsubsection*{Acknowledgements}
 \url{https://github.com/dbosk/drmlab/}.
 
 
-\printbibliography
+\printbibliography{}

drm.tex

@@ -4,7 +4,8 @@
 \usepackage[swedish,english]{babel}
 \usepackage[hyphens]{url}
 \usepackage{hyperref}
-\usepackage[natbib,style=alphabetic,maxbibnames=99,backend=bibtexu]{biblatex}
+\usepackage{cleveref}
+\usepackage[natbib,style=numeric-comp,maxbibnames=99]{biblatex}
 \addbibresource{drm.bib}
 
 \usepackage{acronym}

literature.tex

@@ -1,8 +1,8 @@
 For this assignment you should first read
-Chap.~3--5, 16, 18, and 22 in \citetitle{Anderson2008sea} 
-\cite{Anderson2008sea}.
-Then you should read Chap.~10, 14--15 in \citetitle{Gollmann2011cs} 
-\cite{Gollmann2011cs}.
+Chap.~3--5, 16, 18, and 22 in 
+\citetitle{Anderson2008sea}~\cite{Anderson2008sea}.
+Then you should read Chap.~10, 14--15 in 
+\citetitle{Gollmann2011cs}~\cite{Gollmann2011cs}.
 
 After reading the material given above you need to know about programming in 
 assembler, specifically x86-64 assembler and some tools.