1- \title {Smashing the Stack For Fun and Learning}
1+ \title {Lab: Smashing the Stack For Fun and Learning}
22\subtitle {A lab on arbitrary code execution in a locked down system}
33
44\author {%
@@ -35,10 +35,9 @@ \subsection{Aim}
3535
3636The next section covers what you must read before you understand this
3737assignment and how to do the work.
38- Section \ref {sec:tasks } covers the work to be done, i.e.~how you should learn
39- this.
40- Section \ref {sec:exam } covers how it will be examined, i.e.~how you show that
41- you have fulfilled the intended learning outcomes given above.
38+ \Cref {sec:tasks } covers the work to be done, i.e.~how you should learn this.
39+ \Cref {sec:exam } covers how it will be examined, i.e.~how you show that you have
40+ fulfilled the intended learning outcomes given above.
4241
4342
4443\section {Theory }
@@ -49,7 +48,7 @@ \section{Theory}
4948\section {Assignment }
5049\label {sec:tasks }
5150This assignment will use the scenario of a buffer overrun bug found in Sun's
52- Solaris 8 and 9 \cite {passwdbug }.
51+ Solaris 8 and 9~ \cite {passwdbug }.
5352The scenario is a vulnerability in the passwd(1) program which allows for
5453arbitrary code execution.
5554We will use a much simplified version of the passwd(1) utility, the source code
@@ -97,7 +96,7 @@ \subsubsection*{Acknowledgements}
9796\url {https://github.com/dbosk/stacksmashlab/}.
9897
9998
100- \printbibliography
99+ \printbibliography {}
101100
102101
103102\appendix
0 commit comments