\end{minipage}
\begin{minipage}[b]{0.5\linewidth}
\center
+ Pacher, Christoph \\
+ Palfrader, Peter \\
Pichler, Patrick \\
Petukhova, Anna (Logo) \\
-P\"oschl, Ulrich \\
+Pöschl, Ulrich \\
San, Berg \\
Schreck, Thomas \\
Seidl, Eva (PDF layout) \\
-Wagner, Sebastian (``sebix'') \\
+Wagner, Sebastian («sebix») \\
+ Zangerl, Alexander \\
\end{minipage}
\vline{}
\posttitle{\par\end{flushleft}\vskip 0.5em}
\preauthor{\begin{flushleft}
- \large \lineskip 0.5em \color{intersectgreen}}
-
+ \large \lineskip 0.5em
+ \color{intersectgreen}}
+ %\vskip 0.5em
\author{Wolfgang Breyha, David Durvaux, Tobias Dussa, L. Aaron
Kaplan, Florian Mendel, Christian Mock, Manuel Koschuch, Adi
- Kriegisch, Ulrich P\"oschl, Ramin Sabet, Berg San, Ralf Schlatterbeck,
+ Kriegisch, Ulrich Pöschl, Ramin Sabet, Berg San, Ralf Schlatterbeck,
Thomas Schreck, Aaron Zauner, Pepi Zawodsky}
%\institute{
%FH Campus Wien
% This list is based on : http://en.wikipedia.org/wiki/Relational_database_management_system#Market_share
%% ----------------------------------------------------------------------
-\subsubsection{Oracle}
-\begin{description}
-\item[Tested with Version:] not tested
+\subsection{Oracle}
+%\subsubsection{Tested with Version}
+\todo{not tested yet}
-\item[References:] (German)
-{\small \url{http://www.telekom.com/static/-/155996/7/technische-sicherheitsanforderungen-si}}
+\subsubsection{References}
+\begin{itemize}
+ \item Technical safety requirements by \emph{Deutsche Telekom AG} (German). Please read section 17.12 or pages 129 and following (Req 396 and Req 397) about SSL and ciphersuites \url{http://www.telekom.com/static/-/155996/7/technische-sicherheitsanforderungen-si}
+\end{itemize}
-Please read the following pages about SSL and ciphersuites:\\
-p. 129 -Req 396 and Req 397 \\
-
-\end{description}
%% ----------------------------------------------------------------------
- \subsection{SQL Server}
-\subsubsection{SQL Server}
-
-
+\todo{write this}
%% ----------------------------------------------------------------------
It basically uses Diffie-Hellman, AES and SHA1. Communicating over an insecure instant messaging network, OTR can be used for end to end encryption.
-There are no specific configurations required but the protocol itself is worth to be mentioned.
+There are no specific configurations required but the protocol itself is worth being mentioned.
+
-\subsubsection{IRC}
+%%----------------------------------------------------------------------
+\subsection{Charybdis}
- \todo{Quick draft -- to complete / review / validate}
-
- There are numerous implementations of IRC servers. In this section, we choose \emph{Charybdis} which serve as basis for \emph{ircd-seven}\footnote{https://dev.freenode.net/redmine/projects/ircd-seven}, developed and used by freenode. Freenode is actually the biggest IRC network\footnote{http://irc.netsplit.de/networks/top10.php}. \emph{Charybdis} is being part of the \emph{Debian} \& \emph{Ubuntu} distributions.
-There are numerous implementations of IRC servers. In this section, we choose {\it Charybdis} which serves as basis for {\it ircd-seven}\footnote{https://dev.freenode.net/redmine/projects/ircd-seven}, developed and used by freenode. Freenode is actually the biggest IRC network\footnote{http://irc.netsplit.de/networks/top10.php}. {\it Charybdis} is part of the {\it Debian} \& {\it Ubuntu} distributions.
++There are numerous implementations of IRC servers. In this section, we choose \emph{Charybdis} which serves as basis for \emph{ircd-seven}\footnote{https://dev.freenode.net/redmine/projects/ircd-seven}, developed and used by freenode. Freenode is actually the biggest IRC network\footnote{http://irc.netsplit.de/networks/top10.php}. \emph{Charybdis} is part of the \emph{Debian} \& \emph{Ubuntu} distributions.
-\begin{lstlisting}[breaklines]
+\begin{lstlisting}
/* Extensions */
# Some modules
#loadmodule "extensions/chm_sslonly_compat.so";
Client and server have to use compatible configurations, otherwise they can't communicate.
The \verb|cipher| and \verb|auth| directives have to be identical.
- \todo{FIXME: we should use the CIPHERSTRINGB macro here}
-\begin{lstlisting}[breaklines]
-tls-cipher @@@CIPHERSTRINGB@@@
+\begin{lstlisting}
- tls-cipher DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-CAMELLIA256-SHA:DHE-RSA-AES256-SHA:DHE-RSA-CAMELLIA128-SHA:DHE-RSA-AES128-SHA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA
++tls-cipher %*CIPHERSTRINGB*)
cipher AES-256-CBC
auth SHA384
git.bettercrypto.org / ach-master.git / commitdiff