nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-04-18 03:28:07 -05:00
Code Issues Projects Releases Wiki Activity

Administrivia: most SSH-2 specs are no longer drafts.

Browse Source 
[originally from svn r6890]
This commit is contained in:
Jacob Nevins 2006-11-08 00:55:13 +00:00
parent 06c7e29607
commit e2215a31f6
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/config.but
View File

@ -2200,7 +2200,7 @@ separate configuration of the preference orders. As a result you may
get two warnings similar to the one above, possibly with different get two warnings similar to the one above, possibly with different
encryptions. encryptions.
Single-DES is not recommended in the SSH-2 draft protocol Single-DES is not recommended in the SSH-2 protocol
standards, but one or two server implementations do support it. standards, but one or two server implementations do support it.
PuTTY can use single-DES to interoperate with PuTTY can use single-DES to interoperate with
these servers if you enable the \q{Enable legacy use of single-DES in these servers if you enable the \q{Enable legacy use of single-DES in
@ -2281,7 +2281,7 @@ These options control how often PuTTY will initiate a repeat key
exchange (\q{rekey}). You can also force a key exchange at any time exchange (\q{rekey}). You can also force a key exchange at any time
from the Special Commands menu (see \k{using-specials}). from the Special Commands menu (see \k{using-specials}).
\# FIXME: do we have any additions to the SSH-2 drafts' advice on \# FIXME: do we have any additions to the SSH-2 specs' advice on
these values? Do we want to enforce any limits? these values? Do we want to enforce any limits?
\b \q{Max minutes before rekey} specifies the amount of time that is \b \q{Max minutes before rekey} specifies the amount of time that is
@ -2886,7 +2886,7 @@ This is an SSH-2-specific bug.
Versions below 3.3 of \i{OpenSSH} require SSH-2 RSA signatures to be Versions below 3.3 of \i{OpenSSH} require SSH-2 RSA signatures to be
padded with zero bytes to the same length as the RSA key modulus. padded with zero bytes to the same length as the RSA key modulus.
The SSH-2 draft specification says that an unpadded signature MUST be The SSH-2 specification says that an unpadded signature MUST be
accepted, so this is a bug. A typical symptom of this problem is accepted, so this is a bug. A typical symptom of this problem is
that PuTTY mysteriously fails RSA authentication once in every few that PuTTY mysteriously fails RSA authentication once in every few
hundred attempts, and falls back to passwords. hundred attempts, and falls back to passwords.