Intro: improved explenation why iptables are needed

[tt2015.git] / 1intro.tex

diff --git a/1intro.tex b/1intro.tex
index 76aa5d2..99ade5d 100644 (file)
--- a/1intro.tex
+++ b/1intro.tex
@@ -18,7 +18,10 @@ Java\footnote{\url{http://www.java.com}} TCP driven echo server that executed
 on a virtualized Ubuntu system\footnote{\url{http://www.ubuntu.com}} running on
 the Linux kernel\footnote{\url{http://www.kernel.org}} version $3.13$. To test
 the error behaviour custom iptables output policies have to be
-set~\ref{listing:iptables}.
+set Listing~\ref{listing:iptables}. This is needed because the kernel by default 
+closes all connections from unknown sources and the manually created TCP 
+packets used in testing the implementation are from a source unknown to the 
+kernel.
 
 \begin{lstlisting}[label={listing:iptables},caption={settings iptables}]
 Chain OUTPUT (policy ACCEPT)
@@ -27,4 +30,11 @@ ACCEPT       tcp     --      anywhere        anywhere        tcp flags:PSH/PSH
 DROP   tcp     --      anywhere        anywhere        tcp flags:RST/RST
 \end{lstlisting}
 
+\subsection{Risks}
 %5. Risks
+Risks can be divided into two categories. Project risks and Product risks.
+\begin{itemize}
+       \item\textbf{Project Risks}\\
+       \item\textbf{Product Risks}\\
+\end{itemize}
+