summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode/Report')
-rw-r--r--notFinishedCode/Report/test.aux4
-rw-r--r--notFinishedCode/Report/test.log36
-rw-r--r--notFinishedCode/Report/test.pdfbin1043275 -> 1037745 bytes
-rw-r--r--notFinishedCode/Report/test.tex25
-rw-r--r--notFinishedCode/Report/test.tex.backup20
-rw-r--r--notFinishedCode/Report/test.tex~27
-rw-r--r--notFinishedCode/Report/test.toc2
7 files changed, 63 insertions, 51 deletions
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index 04c796f..d305bc2 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -6,10 +6,10 @@
\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction and Motivation}{3}}
\citation{network}
\citation{network}
-\citation{python}
\@writefile{toc}{\contentsline {section}{\numberline {2}Requirements}{4}}
\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces }}{4}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Logical and algorithmic requirements}{4}}
+\citation{python}
\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces }}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Software requirements}{5}}
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}Hardware requirements}{6}}
@@ -29,8 +29,8 @@
\citation{wiki}
\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces }}{10}}
\@writefile{lof}{\contentsline {figure}{\numberline {7}{\ignorespaces }}{10}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Ping class}{10}}
\citation{wiki}
-\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Ping class}{11}}
\@writefile{lof}{\contentsline {figure}{\numberline {8}{\ignorespaces }}{11}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.5}Data logging}{11}}
\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces }}{11}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 4ceae69..86d435b 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 21 OCT 2011 12:21
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 21 OCT 2011 12:49
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -326,9 +326,9 @@ File: serialPort.png Graphic file (type png)
<use serialPort.png>
[8 <./dbClass.png (PNG copy)>]
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <9> on input line 175.
+(Font) <9> on input line 176.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <5> on input line 175.
+(Font) <5> on input line 176.
<serverClass.png, id=44, 302.12875pt x 181.67876pt>
File: serverClass.png Graphic file (type png)
@@ -368,23 +368,23 @@ File: sshTunnel.png Graphic file (type png)
<use sshTunnel.png> [16
<./sshTunnel.png (PNG copy)>] [17] [18]
-LaTeX Font Info: Try loading font information for OMS+cmr on input line 457.
+LaTeX Font Info: Try loading font information for OMS+cmr on input line 458.
(/usr/share/texmf-texlive/tex/latex/base/omscmr.fd
File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 457.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 458.
[19] [20] [21]
-LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 529.
+LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 530.
<resultsImage.png, id=99, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
<use resultsImage.png>
[22 <./resultsImage.png (PNG copy)>] [23] [24]
-LaTeX Font Info: Try loading font information for T1+cmtt on input line 559.
+LaTeX Font Info: Try loading font information for T1+cmtt on input line 560.
(/usr/share/texmf-texlive/tex/latex/base/t1cmtt.fd
@@ -392,30 +392,30 @@ File: t1cmtt.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
AED: lastpage setting LastPage [25] (./test.aux) )
Here is how much of TeX's memory you used:
- 4935 strings out of 495061
- 68443 string characters out of 1182621
+ 4933 strings out of 495061
+ 68430 string characters out of 1182621
255280 words of memory out of 3000000
- 8043 multiletter control sequences out of 15000+50000
- 18484 words of font info for 43 fonts, out of 3000000 for 9000
+ 8042 multiletter control sequences out of 15000+50000
+ 17720 words of font info for 42 fonts, out of 3000000 for 9000
28 hyphenation exceptions out of 8191
- 36i,10n,45p,752b,1285s stack positions out of 5000i,500n,10000p,200000b,50000s
+ 36i,11n,45p,731b,1679s stack positions out of 5000i,500n,10000p,200000b,50000s
</home/refik/.texmf-var/font
-s/pk/ljfour/jknappen/ec/ectt1200.600pk> </home/refik/.texmf-var/fonts/pk/ljfour
+s/pk/ljfour/jknappen/ec/ectt1095.600pk> </home/refik/.texmf-var/fonts/pk/ljfour
/jknappen/ec/ecrm0900.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/e
c/ecrm0600.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm0800.
-600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecti1200.600pk> </ho
+600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecti1095.600pk> </ho
me/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecsx1200.600pk> </home/refik/.t
exmf-var/fonts/pk/ljfour/jknappen/ec/ecrm1095.600pk> </home/refik/.texmf-var/fo
nts/pk/ljfour/jknappen/ec/ecsx1095.600pk> </home/refik/.texmf-var/fonts/pk/ljfo
ur/jknappen/ec/ecsx1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen
/ec/ecsl1095.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm120
0.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm1728.600pk></u
-sr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmmi12.pfb></usr/share/te
+sr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmmi10.pfb></usr/share/te
xmf-texlive/fonts/type1/public/amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive
/fonts/type1/public/amsfonts/cm/cmsy9.pfb>
-Output written on test.pdf (25 pages, 1043275 bytes).
+Output written on test.pdf (25 pages, 1037745 bytes).
PDF statistics:
- 676 PDF objects out of 1000 (max. 8388607)
+ 664 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
81 words of extra memory for PDF output out of 10000 (max. 10000000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index bf54729..a4d7f21 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 0f29a39..10453de 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -98,25 +98,26 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mai
% first chapter
\section{Introduction and Motivation} % chapter 1
-\large In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for land-line calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems and infer the results out of our findings.
+In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for land-line calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems and infer the results out of our findings.
Before we had started working on our project, we had to analyze the overall network to come up with test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
\clearpage
\section{Requirements} % chapter 2
-At the start of the project the requirements were not completely known but as the had time passed we redefined our requirements and goals.
-The first and the most important part at the start was to define the key goals of our team project. It was to build a
-test software system which could tell the operator user what is not properly working in our local University telecommunication network.
+At the start of the project the requirements were not completely known but as the time had passed we redefined our requirements and goals.
+The first and the most important part at the start was to identify the key goals of our team project. The basic goal of our team project was to build a
+test software system which could tell an operator user what part of the system is not properly working in our University telecommunication network.
Konrad and Dennis suggested us to look at figure 1 and depending on it to build our test software.
\begin{figure}[ht!]
\centering
\includegraphics[width=140mm]{BigPicture_new1.png}
\caption[]{Overview of the Freiburg University telecommunication network \cite{network}}
\end{figure}
-Our first objective was to see what could we test without having access to the system. We installed various communication programs to see what others have done.
-After gaining access to the communication software we had decided to build most of the test software ourselves. Libraries, which were used,
-were only the ones we could not develop ourself because of the time-span of our team project.
+Our first attempt was to see what could we test without having access to the system. We installed numerous communication programs to see what others have done.
+After gaining access to the communication software, we had decided to build most of the test software ourselves. Libraries, which were used,
+were only the ones we could not develop ourselves because of the time-span of our team project.
\subsection{Logical and algorithmic requirements}
-\par Another requirement was to draw a use case diagram and a simple test case diagram so that we could better identify all the problems we had to deal but also to easier follow the development of our test software.
+Despite the software and hardware requirements, the logic in our problem may be considered as the most important part.
+Controlling the software and hardware in a specific manner was one of the requirements in our team project. Moreover, we were required to draw a use case diagram and a simple test case diagram so that we could better understand all the problems we had to deal with but also to easier follow the development of our test software.
\begin{figure}[ht!]
\centering
\includegraphics[width=100mm]{activity_diagram.png}
@@ -320,7 +321,7 @@ of receiving corresponding message. Otherwise it enters the exit state and then
\section{Security and safety of the system}
-\large Safety and security of the software plays a major role in our project.
+Safety and security of the software plays a major role in our project.
It is of vital importance that only as few as possible people have access to our test system since the resulting data could be exploited to plan an attack
(e.g. assume the University alarm system uses the SIP gateway to connect to the outside world and to alarm the police, if one knows that the SIP gateway is not working properly, a burglar could plan to rob the University building just at that moment.) Therefore the choice to go Open Source is justified due to the fact that one should know how every single detail of the system works.
All the time, while we were working on the project, we were made aware of this issue by Denis and Konrad.
@@ -410,14 +411,14 @@ openssl rsa -in server.key -out server.key.insecure
mv server.key server.key.secure
mv server.key.insecure server.key
\end{lstlisting}
-\par The generated files are very sensitive, since they are our keys. After these steps were completed, we had generated 4 files (\emph{server.crt}, \emph{server.csr}, \emph{server.key} and \emph{server.key.secure}). Now we need to enable the SSL engine on the Apache web server.
+\par The generated files are very sensitive, since they are our keys. After these steps were completed, we had generated 4 files: \emph{server.crt}, \emph{server.csr}, \emph{server.key} and \\ \emph{server.key.secure}. Now we need to enable the SSL engine on the Apache web server.
We coppied \emph{server.key} and \emph{server.crt} into \emph{/etc/appache2/ssl}.
\begin{lstlisting}
refik@ubuntu:/etc/apache2$ sudo mkdir ssl
cp server.key /etc/apache2/ssl
cp server.crt /etc/apache2/ssl
\end{lstlisting}
-\par Then we enabled SSL by typing in \emph{a2enmod ssl}, ``it is simply a general purpose utility to establish a symlink between a module in \emph{/etc/apache2/mods-available} to \emph{/etc/apache2/mods-enabled} (or give a message to the effect that a given module does not exist or that it is already symlinked for loading)'' \cite{https}.
+\par Then we enabled SSL by typing in \emph{a2enmod ssl}, ``it is simply a general purpose utility to establish a symlink between a module in \emph{/etc/apache2/mods-available} to \\ \emph{/etc/apache2/mods-enabled} (or give a message to the effect that a given module does not exist or that it is already symlinked for loading)'' \cite{https}.
\begin{lstlisting}
refik@ubuntu:/etc/apache2/ssl$ sudo a2enmod ssl
Enabling module ssl.
@@ -497,7 +498,7 @@ refik@ubuntu:/etc/apache2/sites-available$
\newpage
\section{Web page}
-\large One of the requests of our team project was to build a test system that could be started from the web site.
+One of the requests of our team project was to build a test system that could be started from the web site.
Since we used the Open Source platform to base our project on, it was certain we will use it for the web site as well.
The dynamic parts of the web site were programmed using PHP and JavaScript. The GUI was done using CSS.
The web site opens TCP/IP sessions between itself and the Python test software. Due reasons explained in the section above,
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 0622296..86e04bb 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -103,8 +103,8 @@ Before we had started working on our project, we had to analyze the overall netw
Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
\clearpage
\section{Requirements} % chapter 2
-At the start of the project the requirements were not completely known but as the time passed we redefined our goals.
-The first and the most important part at the start was to define the key goals of our team project. It was to build a
+At the start of the project the requirements were not completely known but as the time had passed we redefined our requirements and goals.
+The first and the most important part at the start was to identify the key goals of our team project. It was to build a
test software system which could tell the operator user what is not properly working in our local University telecommunication network.
Konrad and Dennis suggested us to look at figure 1 and depending on it to build our test software.
\begin{figure}[ht!]
@@ -114,17 +114,27 @@ Konrad and Dennis suggested us to look at figure 1 and depending on it to build
\end{figure}
Our first objective was to see what could we test without having access to the system. We installed various communication programs to see what others have done.
After gaining access to the communication software we had decided to build most of the test software ourselves. Libraries, which were used,
-were only the ones we could not develop ourself because of the time-span of our team project.
+were only the ones we could not develop ourselves because of the time-span of our team project.
+\subsection{Logical and algorithmic requirements}
+\par Assuming that the requirement was to draw a use case diagram and a simple test case diagram so that we could better identify all the problems we had to deal but also to easier follow the development of our test software.
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=100mm]{activity_diagram.png}
+ \caption[]{Simple algorithmic overview of a test case}
+\end{figure}
+\subsection{Software requirements}
\par Afterward we had to choose the programming language. Since we had the freedom of choice, between the three suggested programming languages
Java, C++ and Python, we made a joint decision to use Python as the main programming language in our team project. One of the requirements was to finish the team project in time,
therefore our decision to use Python is justified. Using Python we could work faster and integrate our subsystems more effectively \cite{python}.
Our programming language of choice is multi-platform, therefore our test software would be easy portable to other operating systems.
\par Likewise we had to decide how our test software will work. One of the requirements by Dennis and Konrad was to make the software capable of being run from the terminal.
-The next requirement was to make a good looking GUI so that even an operator user without Linux experience could handle the tests.
+The next requirement was to make an appealing GUI so that even an user without advanced Linux experience could handle the software and read out the results.
\par In addition it was required to log all the past test. Later on a machine learning algorithm or some other intelligence could be applied to deduce some error behavior of the system
(e.g. an intelligent algorithm could find that part of the system fail in a combined manner). To accomplish the logging of all the tests we had to use a database system.
We decided to use MySQL since it is open source and well supported. However, one should know that the test results are only stored into the database in case the test was started from the web site.
-\par Another requirement was to draw a use case diagram so that we could better identify
+
+\subsection{Hardware requirements}
+\par Beside the software requirements we had hardware requirements as well.
\newpage
\section{Database design}
At the start our database of choice was MySQL.
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index 06aa99e..40d1033 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -98,25 +98,26 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mai
% first chapter
\section{Introduction and Motivation} % chapter 1
-\large In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for land-line calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems and infer the results out of our findings.
+In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for land-line calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems and infer the results out of our findings.
Before we had started working on our project, we had to analyze the overall network to come up with test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
\clearpage
\section{Requirements} % chapter 2
-At the start of the project the requirements were not completely known but as the had time passed we redefined our requirements and goals.
-The first and the most important part at the start was to define the key goals of our team project. It was to build a
-test software system which could tell the operator user what is not properly working in our local University telecommunication network.
+At the start of the project the requirements were not completely known but as the time had passed we redefined our requirements and goals.
+The first and the most important part at the start was to identify the key goals of our team project. The basic goal of our team project was to build a
+test software system which could tell an operator user what part of the system is not properly working in our University telecommunication network.
Konrad and Dennis suggested us to look at figure 1 and depending on it to build our test software.
\begin{figure}[ht!]
\centering
\includegraphics[width=140mm]{BigPicture_new1.png}
\caption[]{Overview of the Freiburg University telecommunication network \cite{network}}
\end{figure}
-Our first objective was to see what could we test without having access to the system. We installed various communication programs to see what others have done.
-After gaining access to the communication software we had decided to build most of the test software ourselves. Libraries, which were used,
-were only the ones we could not develop ourself because of the time-span of our team project.
+Our first attempt was to see what could we test without having access to the system. We installed numerous communication programs to see what others have done.
+After gaining access to the communication software, we had decided to build most of the test software ourselves. Libraries, which were used,
+were only the ones we could not develop ourselves because of the time-span of our team project.
\subsection{Logical and algorithmic requirements}
-\par Another requirement was to draw a use case diagram and a simple test case diagram so that we could better identify all the problems we had to deal but also to easier follow the development of our test software.
+Despite the software and hardware requirements, the logic in our problem may be considered as the most important part.
+Controlling the software and hardware without any logical requirement was to draw a use case diagram and a simple test case diagram so that we could better identify all the problems we had to deal but also to easier follow the development of our test software.
\begin{figure}[ht!]
\centering
\includegraphics[width=100mm]{activity_diagram.png}
@@ -128,7 +129,7 @@ Java, C++ and Python, we made a joint decision to use Python as the main program
therefore our decision to use Python is justified. Using Python we could work faster and integrate our subsystems more effectively \cite{python}.
Our programming language of choice is multi-platform, therefore our test software would be easy portable to other operating systems.
\par Likewise we had to decide how our test software will work. One of the requirements by Dennis and Konrad was to make the software capable of being run from the terminal.
-The next requirement was to make a good looking GUI so that even an operator user without Linux experience could handle the tests.
+The next requirement was to make an appealing GUI so that even an user without advanced Linux experience could handle the software and read out the results.
\par In addition it was required to log all the past test. Later on a machine learning algorithm or some other intelligence could be applied to deduce some error behavior of the system
(e.g. an intelligent algorithm could find that part of the system fail in a combined manner). To accomplish the logging of all the tests we had to use a database system.
We decided to use MySQL since it is open source and well supported. However, one should know that the test results are only stored into the database in case the test was started from the web site.
@@ -320,7 +321,7 @@ of receiving corresponding message. Otherwise it enters the exit state and then
\section{Security and safety of the system}
-\large Safety and security of the software plays a major role in our project.
+Safety and security of the software plays a major role in our project.
It is of vital importance that only as few as possible people have access to our test system since the resulting data could be exploited to plan an attack
(e.g. assume the University alarm system uses the SIP gateway to connect to the outside world and to alarm the police, if one knows that the SIP gateway is not working properly, a burglar could plan to rob the University building just at that moment.) Therefore the choice to go Open Source is justified due to the fact that one should know how every single detail of the system works.
All the time, while we were working on the project, we were made aware of this issue by Denis and Konrad.
@@ -410,14 +411,14 @@ openssl rsa -in server.key -out server.key.insecure
mv server.key server.key.secure
mv server.key.insecure server.key
\end{lstlisting}
-\par The generated files are very sensitive, since they are our keys. After these steps were completed, we had generated 4 files (\emph{server.crt}, \emph{server.csr}, \emph{server.key} and \emph{server.key.secure}). Now we need to enable the SSL engine on the Apache web server.
+\par The generated files are very sensitive, since they are our keys. After these steps were completed, we had generated 4 files: \emph{server.crt}, \emph{server.csr}, \emph{server.key} and \\ \emph{server.key.secure}. Now we need to enable the SSL engine on the Apache web server.
We coppied \emph{server.key} and \emph{server.crt} into \emph{/etc/appache2/ssl}.
\begin{lstlisting}
refik@ubuntu:/etc/apache2$ sudo mkdir ssl
cp server.key /etc/apache2/ssl
cp server.crt /etc/apache2/ssl
\end{lstlisting}
-\par Then we enabled SSL by typing in \emph{a2enmod ssl}, ``it is simply a general purpose utility to establish a symlink between a module in \emph{/etc/apache2/mods-available} to \emph{/etc/apache2/mods-enabled} (or give a message to the effect that a given module does not exist or that it is already symlinked for loading)'' \cite{https}.
+\par Then we enabled SSL by typing in \emph{a2enmod ssl}, ``it is simply a general purpose utility to establish a symlink between a module in \emph{/etc/apache2/mods-available} to \\ \emph{/etc/apache2/mods-enabled} (or give a message to the effect that a given module does not exist or that it is already symlinked for loading)'' \cite{https}.
\begin{lstlisting}
refik@ubuntu:/etc/apache2/ssl$ sudo a2enmod ssl
Enabling module ssl.
@@ -497,7 +498,7 @@ refik@ubuntu:/etc/apache2/sites-available$
\newpage
\section{Web page}
-\large One of the requests of our team project was to build a test system that could be started from the web site.
+One of the requests of our team project was to build a test system that could be started from the web site.
Since we used the Open Source platform to base our project on, it was certain we will use it for the web site as well.
The dynamic parts of the web site were programmed using PHP and JavaScript. The GUI was done using CSS.
The web site opens TCP/IP sessions between itself and the Python test software. Due reasons explained in the section above,
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index 6764041..af429f9 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -9,7 +9,7 @@
\contentsline {subsection}{\numberline {4.1}Database access}{8}
\contentsline {subsection}{\numberline {4.2}Controlling the cell phones}{8}
\contentsline {subsection}{\numberline {4.3}Client and Server class}{9}
-\contentsline {subsection}{\numberline {4.4}Ping class}{11}
+\contentsline {subsection}{\numberline {4.4}Ping class}{10}
\contentsline {subsection}{\numberline {4.5}Data logging}{11}
\contentsline {subsection}{\numberline {4.6}SSH Class}{11}
\contentsline {section}{\numberline {5}Hardware design}{12}