summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRefik Hadzialic2011-11-03 19:36:10 +0100
committerRefik Hadzialic2011-11-03 19:36:10 +0100
commitd1c1a688d5d6e110d02fbc1c15b26061ef2a1a96 (patch)
treeca6a7a820da519d0573c7c8da1df5d3ec86475ff
parentOne of the last report modifications (diff)
downloadgsm-selftest-d1c1a688d5d6e110d02fbc1c15b26061ef2a1a96.tar.gz
gsm-selftest-d1c1a688d5d6e110d02fbc1c15b26061ef2a1a96.tar.xz
gsm-selftest-d1c1a688d5d6e110d02fbc1c15b26061ef2a1a96.zip
Report modification
-rw-r--r--notFinishedCode/Report/test.log4
-rw-r--r--notFinishedCode/Report/test.pdfbin5056724 -> 5056740 bytes
-rw-r--r--notFinishedCode/Report/test.tex8
-rw-r--r--notFinishedCode/Report/test.tex~6
4 files changed, 9 insertions, 9 deletions
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 5c779d7..412e4f8 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) 3 NOV 2011 17:32
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 3 NOV 2011 19:35
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -633,7 +633,7 @@ en/ec/ecsx1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecsl1
texmf-texlive/fonts/type1/public/amsfonts/cm/cmmi10.pfb></usr/share/texmf-texli
ve/fonts/type1/public/amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive/fonts/ty
pe1/public/amsfonts/cm/cmsy9.pfb>
-Output written on test.pdf (50 pages, 5056724 bytes).
+Output written on test.pdf (50 pages, 5056740 bytes).
PDF statistics:
1654 PDF objects out of 1728 (max. 8388607)
418 named destinations out of 1000 (max. 500000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index e3cebef..9e49dda 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 a432aaa..9582d9c 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -128,7 +128,7 @@ Gradually we implemented a bit-by-bit of the final software. In the following ch
This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software.
Certainly, we had a lot of fun while working on the project due the fact that we lost one team member.
We would like to thank the whole department for the free coffee and their support, especially
-Konrad Maier, Dennis Wehrle and Richard M. Zahoransky, without their support this project would not
+Konrad Meier, Dennis Wehrle and Richard M. Zahoransky, without their support this project would not
end up this way.
\clearpage
\section{Requirements} % chapter 2
@@ -563,13 +563,13 @@ pan: elapsed time 0 seconds
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.
+All the time, while we were working on the project, we were made aware of this issue by Dennis and Konrad.
We decided to use asymmetric key cryptography, where each side has two keys (private and public). In the next sections we will explain in more details how we applied the methods.
\subsection{Encryption of the communication channels}
At first we thought to encrypt the data before sending them but since none of us was an expert on encryption standards the idea was rejected. Alongside the fact that none of us had been an expert in the field of cryptography, we were neither experts in the field of Internet programming. One could find maybe a way to disable our server software with various hacking methods (e.g.
trying to open the port until the system runs out of memory and in our case the system which we used on the handler side was a BeagleBoard with ARM architecture running on a single chip TI OMAP processor, refer to the picture in figure).
We had to eliminate even the slightest possible threat in return for spending more time for debugging the test software system. Despite we were aware of all these facts, we had to choose one of the plenty implemented encryption standards on Linux.
-Denis and Konrad suggested using the SSH Tunneling method.
+Dennis and Konrad suggested using the SSH Tunneling method.
\begin{figure}[ht!]
\centering
@@ -628,7 +628,7 @@ Securing the communication channels without making certain the web site is safe
We decided to use the \emph{https} protocol instead of the \emph{http} since a person in the middle
could sniff our data (e.g. a person is connected with his/her smart-phone over an unprotected wireless network) \cite{https}.
At the same time the web site should be accessible only by the authorized personel. Our first approach to this
-problem was to build an PHP page with \emph{MD5} hashed passwords, however we got a suggestion by Konrad and Denis to
+problem was to build an PHP page with \emph{MD5} hashed passwords, however we got a suggestion by Konrad and Dennis to
use a safer encryption method implemented in the Apache web server software, \emph{.htaccess}. By using
these two techniques we protected the web site of some vulnerabilities known to us. If the web site
will be only accessed from our local university network, we can additionally add an IP filter mask as well.
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index eea101c..a432aaa 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -1267,14 +1267,14 @@ do is just type the command for starting the test software in the folder where i
in mind there are two dashes before \emph{option}).
\begin{figure}[ht!]
\centering
- \includegraphics[width=120mm]{terminalCommand.png}
+ \includegraphics[width=100mm]{terminalCommand.png}
\caption[]{Test software terminal options}
\end{figure}
You can perform the tests manually by typing what you want to test or by choosing one of the predefined tests. For example, you
want to test manually does the SIP work with the University telephone network, you would type the following: \emph{./gsmselftest.py --db sip unisip}.
\begin{figure}[ht!]
\centering
- \includegraphics[width=120mm]{resultterminal.png}
+ \includegraphics[width=100mm]{resultterminal.png}
\caption[]{Example results from the terminal screen}
\end{figure}
After the tests have been performed the results will be displayed. Green result text means the test was performed successfully and red result
@@ -1286,7 +1286,7 @@ manual configuration. One should keep in mind that the terminal test software ca
additional command \emph{-X}\footnote{For example: ssh -X username@address}.
\begin{figure}[htb]
\centering
- \includegraphics[width=120mm]{devconf.png}
+ \includegraphics[width=100mm]{devconf.png}
\caption[]{Test software device configuration from terminal screen}
\end{figure}