Commit 7823ec22 authored by Paul Fiterau Brostean's avatar Paul Fiterau Brostean

Consistent Bitvise naming

parent 9de31186
This diff is collapsed.
......@@ -326,7 +326,7 @@ G ( hasOpenedChannel ->
\subsection{Model checking results}
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
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 \textit{out=UA\_SUCCESS} as sign of successful authentication.
......@@ -358,7 +358,7 @@ In particular, we used {\dvauth} instead of \textit{out=UA\_SUCCESS} as sign of
%\end{center}
Properties marked with '*' did not hold because implementations chose to send \textsc{unimpl}, instead of the output suggested by the RFC. As an example,
after successful authentication, both BitVise and OpenSSH respond with \textsc{unimpl} to further authentication requests, instead of being silent, violating
after successful authentication, both Bitvise and OpenSSH respond with \textsc{unimpl} to further authentication requests, instead of being silent, violating
Property~\ref{prop:auth-post-ua}. Whether the alternative behavior adapted is acceptable is up for debate. Definitely the RFC does not suggest it, though the RFC
does leave room for interpretation.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment