summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-06 00:41:25 +0200
committerRefik Hadzialic2011-10-06 00:41:25 +0200
commit4b27c9d2c3a9771270469f084f07927aa51e002c (patch)
tree6da8225a181a9f5b2459f5b6b06acaf26d7a1a85 /notFinishedCode/Report/test.tex
parentReport writing in progress! (diff)
downloadgsm-selftest-4b27c9d2c3a9771270469f084f07927aa51e002c.tar.gz
gsm-selftest-4b27c9d2c3a9771270469f084f07927aa51e002c.tar.xz
gsm-selftest-4b27c9d2c3a9771270469f084f07927aa51e002c.zip
Writing report!
Diffstat (limited to 'notFinishedCode/Report/test.tex')
-rw-r--r--notFinishedCode/Report/test.tex12
1 files changed, 10 insertions, 2 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index c4cbed6..5b1fd4b 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -145,8 +145,16 @@ We decided to use asymmetric key cryptography, where each side has two keys (pri
At first we thoought 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 not experts in the field of internet programming either. 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 server side was a BeagleBoard with ARM architecture running on a single chip TI OMAP processor, refer to the picture on figure 1.)
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. Using the SSH Tunneling method we could hide the real port we use for our socket connection on the other hand we could force the socket to accept only local connections (i.e. from the machine where the handler software was running.)
-The first problem we faced was that SSH required a username and password, everytime we created an SSH Tunnel. We could avoid this problem by copying the public key from our server (where our test software runs) to the BeagleBoard \cite{sshTunnel}.
+Denis and Konrad suggested using the SSH Tunneling method.
+
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=120mm]{sshTunnel.png}
+ \caption[]{SSH Tunnel, all the communication inside the tunnel is encrypted }
+\end{figure}
+
+Using the SSH Tunnel port forwading method we could hide the real port we use for our socket connection on the other hand we could force the socket to accept only local connections (i.e. from the machine where the handler software was running.)
+The first problem we faced was that SSH required the username and password everytime we tried to make an SSH Tunnel port forwarding. We could avoid this problem by copying the public key from our server (where our test software runs) to the BeagleBoard \cite{sshTunnel}.
This can be performed by executing the following commands in the terminal shell.
One has to create first the private and public keys on the local machine(i.e. server machine, where the test software runs):