summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode/Report')
-rw-r--r--notFinishedCode/Report/sshTunnel.pngbin0 -> 18810 bytes
-rw-r--r--notFinishedCode/Report/test.aux9
-rw-r--r--notFinishedCode/Report/test.log43
-rw-r--r--notFinishedCode/Report/test.pdfbin545721 -> 566026 bytes
-rw-r--r--notFinishedCode/Report/test.tex12
-rw-r--r--notFinishedCode/Report/test.tex~17
-rw-r--r--notFinishedCode/Report/test.toc4
7 files changed, 55 insertions, 30 deletions
diff --git a/notFinishedCode/Report/sshTunnel.png b/notFinishedCode/Report/sshTunnel.png
new file mode 100644
index 0000000..3b8e8ae
--- /dev/null
+++ b/notFinishedCode/Report/sshTunnel.png
Binary files differ
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index af65120..c1d1fa7 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -16,9 +16,10 @@
\citation{sshTunnel}
\@writefile{toc}{\contentsline {section}{\numberline {6}Security and safety of the test system}{8}}
\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Encryption of the communication channels}{8}}
-\@writefile{toc}{\contentsline {section}{\numberline {7}Web page}{10}}
-\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces }}{10}}
-\@writefile{toc}{\contentsline {section}{\numberline {8}Conclusion}{11}}
+\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces }}{9}}
+\@writefile{toc}{\contentsline {section}{\numberline {7}Web page}{11}}
+\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces }}{11}}
+\@writefile{toc}{\contentsline {section}{\numberline {8}Conclusion}{12}}
\bibcite{site1}{1}
\bibcite{sshTunnel}{2}
-\newlabel{LastPage}{{}{12}}
+\newlabel{LastPage}{{}{13}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 9239725..90dee61 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) 5 OCT 2011 16:24
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 5 OCT 2011 18:26
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -311,36 +311,39 @@ File: protocolCommunicationcControllerReceiver.png Graphic file (type png)
File: protocolCommunicationcControllerCaller.png Graphic file (type png)
<use protocolCommunicationcControllerCaller.png> [7 <./protocolCommunicationHan
dler.png (PNG copy)> <./protocolCommunicationcControllerReceiver.png (PNG copy)
-> <./protocolCommunicationcControllerCaller.png (PNG copy)>] [8]
+> <./protocolCommunicationcControllerCaller.png (PNG copy)>]
+<sshTunnel.png, id=37, 696.6025pt x 152.57pt>
+File: sshTunnel.png Graphic file (type png)
+ <use sshTunnel.png> [8]
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <9> on input line 154.
+(Font) <9> on input line 162.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <5> on input line 154.
- [9]
-<resultsImage.png, id=45, 702.625pt x 431.6125pt>
+(Font) <5> on input line 162.
+ [9 <./sshTunnel.png (PNG copy)>] [10] <resultsImage.png, id=49, 702.625pt x 43
+1.6125pt>
File: resultsImage.png Graphic file (type png)
- <use resultsImage.png>
-[10 <./resultsImage.png (PNG copy)>] [11]
-LaTeX Font Info: Try loading font information for T1+cmtt on input line 209.
+
+<use resultsImage.png> [11 <./resultsImage.png (PNG copy)>] [12]
+LaTeX Font Info: Try loading font information for T1+cmtt on input line 217.
(/usr/share/texmf-texlive/tex/latex/base/t1cmtt.fd
File: t1cmtt.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <14.4> on input line 209.
+(Font) <14.4> on input line 217.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <7> on input line 209.
+(Font) <7> on input line 217.
-AED: lastpage setting LastPage [12] (./test.aux) )
+AED: lastpage setting LastPage [13] (./test.aux) )
Here is how much of TeX's memory you used:
- 4858 strings out of 495061
- 67162 string characters out of 1182621
- 254247 words of memory out of 3000000
- 7980 multiletter control sequences out of 15000+50000
+ 4863 strings out of 495061
+ 67246 string characters out of 1182621
+ 248247 words of memory out of 3000000
+ 7984 multiletter control sequences out of 15000+50000
18637 words of font info for 45 fonts, out of 3000000 for 9000
28 hyphenation exceptions out of 8191
- 36i,10n,45p,753b,1088s stack positions out of 5000i,500n,10000p,200000b,50000s
+ 36i,11n,45p,753b,1683s stack positions out of 5000i,500n,10000p,200000b,50000s
</home/refik/.texmf-var/font
s/pk/ljfour/jknappen/ec/ectt1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour
/jknappen/ec/ecti1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/e
@@ -352,9 +355,9 @@ nts/pk/ljfour/jknappen/ec/ecsx1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfo
ur/jknappen/ec/ecsl1095.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen
/ec/ecrm1200.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm172
8.600pk></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmsy9.pfb>
-Output written on test.pdf (12 pages, 545721 bytes).
+Output written on test.pdf (13 pages, 566026 bytes).
PDF statistics:
- 513 PDF objects out of 1000 (max. 8388607)
+ 519 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
- 31 words of extra memory for PDF output out of 10000 (max. 10000000)
+ 36 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 3b1c675..84c5338 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 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):
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index b2924fa..8bf4a2d 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -145,10 +145,19 @@ 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, }
+\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):
+
\begin{lstlisting}
jsmith@local-host$ [Note: You are on local-host here]
@@ -162,7 +171,9 @@ Your public key has been saved in /home/jsmith/.ssh/id_rsa.pub.
The key fingerprint is:
33:b3:fe:af:95:95:18:11:31:d5:de:96:2f:f2:35:f9 jsmith@local-host
\end{lstlisting}
+
Then one needs to copy the public key to the remote machine (BeagleBoard) using ssh-copy-id:
+
\begin{lstlisting}
jsmith@local-host$ ssh-copy-id -i ~/.ssh/id_rsa.pub remote-host
jsmith@remote-host's password:
@@ -172,7 +183,9 @@ Now try logging into the machine, with "ssh 'remote-host'", and check in:
to make sure we haven't added extra keys that you weren't expecting.
\end{lstlisting}
+
After we have created the public and private keys, and coppied the public key on the machine to which we want to connect, we can test if we can make an SSH connection to the remote machine:
+
\begin{lstlisting}
jsmith@local-host$ ssh remote-host
Last login: Sun Nov 16 17:22:33 2008 from 192.168.1.2
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index 057396b..d4e1ba3 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -7,5 +7,5 @@
\contentsline {section}{\numberline {5}Protocol}{7}
\contentsline {section}{\numberline {6}Security and safety of the test system}{8}
\contentsline {subsection}{\numberline {6.1}Encryption of the communication channels}{8}
-\contentsline {section}{\numberline {7}Web page}{10}
-\contentsline {section}{\numberline {8}Conclusion}{11}
+\contentsline {section}{\numberline {7}Web page}{11}
+\contentsline {section}{\numberline {8}Conclusion}{12}