Commit 36a8011c authored by Paul Fiterau Brostean's avatar Paul Fiterau Brostean

Added not yet pushed edits files

parent a1006460
B gci . | Where-Object { $_.Name.EndsWith(".dot") } | ForEach-Object {$s = ($_.Name.Substring(0, ($_.Name.Length - 4)) + ".pdf"); echo $s; dot -Tpng $_.Name -o $s}
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
......@@ -362,7 +362,7 @@ after successful authentication, both BitVise and OpenSSH respond with \textsc{u
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 of the \textsc{unimpl} message.
DropBear is the only implementation that allows rekey in both general states of the protocol. DropBear also satisfies all Transport layer specifications, however,
DropBear is the only implementation that allows rekey in both general states of the protocol. DropBear also satisfies all Transport and Authentication layer specifications, however,
problematically, it violates the property of the Connection layer. Upon receiving \textsc{ch\_close}, it responds by \textsc{ch\_eof} instead of \textsc{ch\_close}, not respecting
Property~\ref{prop:conn-close}. %Moreover, the output \textsc{ua\_success} can be generated multiple times, violating both Properties ~\ref{prop:auth-post-ua-strong} and
%~\ref{prop:auth-post-ua}.
......
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