Merge branch 'master' of https://github.com/dopefishh/tt2015

[tt2015.git] / 2approach.tex

diff --git a/2approach.tex b/2approach.tex
index c982a86..98aa460 100644 (file)
--- a/2approach.tex
+++ b/2approach.tex
@@ -47,11 +47,8 @@ to the SUT.
        to send and receive data it needs to be \emph{fault tolerant}. The SUT
        needs to properly handle errors in received data or complete unavailability
        of the underlying channel. 
-       \item \textbf{Security}\\  
-       \emph{Confidentiality} is an important aspect for the SUT. Received data
-       should only be delivered to the program to which it is addressed.
 \end{itemize}
-This leaves three categories which are not relevant the SUT. Below we will
+This leaves four categories which are not relevant the SUT. Below we will
 shortly discuss per category why these are not relevant. \emph{Maintainability}
 is an important aspect of any software system, however for the SUT it is not a
 core aspect, as it is first and foremost of importance that the implementation
@@ -59,7 +56,9 @@ is correct, furthermore TCP does not change often. \emph{Usability} isn't a
 core aspect either, as the SUT is not used directly by humans, but is a service
 which is addressed when another program needs it. \emph{Portability} isn't
 either as the SUT is installed on a system once and intended to work on that
-system.
+system. \emph{Security} isn't a feauture of the SUT either, systems using the
+SUT can add their own security mechanisms on top of it.  
+
 
 \subsubsection{Quality in use}
 Quality in use is dived into five subcategories. Below we will discuss the 
@@ -159,8 +158,23 @@ parameters:
 \end{enumerate}
 
 \subsubsection{Test environment and automatization}
-All the tools we are going to use together with the SUT gives us the following
-collection of software.
+\label{section:testenv}
+%%%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 error behaviour custom iptables output policies have to be 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)
+%%%target      prot    opt     source  destination
+%%%ACCEPT      tcp     --      anywhere        anywhere        tcp flags:PSH/PSH
+%%%DROP        tcp     --      anywhere        anywhere        tcp flags:RST/RST
+%%%\end{lstlisting}
+%%%All the tools we are going to use together with the SUT gives us the following
+%%%collection of software.
 
 \begin{enumerate}
        \item Windows, used as a host OS.