From c8884d15ea5abe262d48cc76c5714dbf91090a17 Mon Sep 17 00:00:00 2001 From: Paul Fiterau Brostean Date: Sat, 18 Feb 2017 10:29:00 +0100 Subject: [PATCH] Probably final version. Almost 0.30 (0.297). --- learning_results.tex | 2 +- security_definitions.tex | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/learning_results.tex b/learning_results.tex index 068b73d..593c358 100644 --- a/learning_results.tex +++ b/learning_results.tex @@ -11,7 +11,7 @@ We have adapted the setting off timing parameters to each implementation. \begin{figure*} \centering - \includegraphics[scale=0.29]{ssh-server_cropped} + \includegraphics[scale=0.297]{ssh-server_cropped} \caption{Model of the OpenSSH server. {\normalfont States are collected in 3 clusters, indicated by the rectangles, where each cluster corresponds to one of the protocol layers. diff --git a/security_definitions.tex b/security_definitions.tex index 3ccbafd..3854678 100644 --- a/security_definitions.tex +++ b/security_definitions.tex @@ -326,8 +326,8 @@ G ( hasOpenedChannel -> \subsection{Model checking results} -Table~\ref{tab:mcresults} presents model checking results. Crucially, the security properties hold for all three implementations. For BitVise, -as it buffered all responses during rekey (including \textsc{UA\_SUCCESS}) we had to adapt our properties slightly. +Table~\ref{tab:mcresults} presents model checking results. Crucially, the security properties hold for all three implementations. We had to slightly adapt our properties for BitVise +as it buffered all responses during rekey (incl. \textsc{UA\_SUCCESS}). In particular, we used {\dvauth} instead of $out=UA\_SUCCESS$ to suggest successful authentication. %\begin{center}\small -- GitLab