From 2d24892b096bdd7cf97e2888b67bab53626af93f Mon Sep 17 00:00:00 2001 From: jacob Date: Tue, 10 Sep 2002 12:30:45 +0000 Subject: [PATCH] Note about separate client-server and server-client encryption in SSH-2 git-svn-id: svn://svn.tartarus.org/sgt/putty@1949 cda61777-01e9-0310-a592-d414129be87e --- doc/config.but | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) 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 -- 2.11.0