From: Jacob Nevins Date: Tue, 10 Sep 2002 12:30:45 +0000 (+0000) Subject: Note about separate client-server and server-client encryption in SSH-2 X-Git-Tag: 0.53~22 X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=commitdiff_plain;h=3711af9a53b78fccbd6f80bbcce0e8b32b1aec06;p=PuTTY.git Note about separate client-server and server-client encryption in SSH-2 [originally from svn r1949] --- diff --git a/doc/config.but b/doc/config.but index 4a855e0e..c9bf6657 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.37 2002/09/08 13:28:38 simon Exp $ +\versionid $Id: config.but,v 1.38 2002/09/10 12:30:45 jacob Exp $ \C{config} Configuring PuTTY @@ -1693,6 +1693,12 @@ consider substandard. By default, PuTTY supplies a preference order intended to reflect a reasonable preference in terms of security and speed. +In SSH-2, the encryption algorithm is negotiated independently for +each direction of the connection, although PuTTY does not support +separate configuration of the preference orders. As a result you may +get two warnings similar to the one above, possibly with different +encryptions. + Single-DES is not supported natively in the SSH 2 draft protocol standards. One or two server implementations do support it, by a non-standard name. PuTTY can use single-DES to interoperate with