1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-25 01:02:24 +00:00

Update documentation for 0.68.

Several places in the docs were labelled for review because they need
to change when 0.68's feature set comes in - no SSH-2 to SSH-1
fallback any more, but on the other hand, Unix Pageant now exists.
This commit is contained in:
Simon Tatham 2017-02-11 07:08:53 +00:00
parent 4b372b0877
commit 00bcf6ecbc
2 changed files with 8 additions and 10 deletions

View File

@ -69,11 +69,11 @@ change the \q{SSH protocol version} setting (see \k{config-ssh-prot}),
or use the \c{-1} command-line option; in any case, you should not
treat the resulting connection as secure.
You might start seeing this message with new versions of PuTTY
\#{XXX-REVIEW-BEFORE-RELEASE: (from 0.XX onwards)}
where you didn't before, because it used to be possible to configure
PuTTY to automatically fall back from SSH-2 to SSH-1. This is no
longer supported, to prevent the possibility of a downgrade attack.
You might start seeing this message with new versions of PuTTY (from
0.68 onwards) where you didn't before, because it used to be possible
to configure PuTTY to automatically fall back from SSH-2 to SSH-1.
This is no longer supported, to prevent the possibility of a downgrade
attack.
\H{errors-cipher-warning} \q{The first cipher supported by the server is
... below the configured warning threshold}

View File

@ -66,9 +66,8 @@ Yes. SSH-1 support has always been available in PuTTY.
However, the SSH-1 protocol has many weaknesses and is no longer
considered secure; you should use SSH-2 instead if at all possible.
\#{XXX-REVIEW-BEFORE-RELEASE:
As of 0.68, PuTTY will no longer fall back to SSH-1 if the server
doesn't appear to support SSH-2; you must explicitly ask for SSH-1. }
doesn't appear to support SSH-2; you must explicitly ask for SSH-1.
\S{faq-localecho}{Question} Does PuTTY support \i{local echo}?
@ -257,10 +256,9 @@ If you look at the source release, you should find a \c{unix}
subdirectory. There are a couple of ways of building it,
including the usual \c{configure}/\c{make}; see the file \c{README}
in the source distribution. This should build you Unix
ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, and also
ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, Pageant, and also
\i\c{pterm} - an \cw{xterm}-type program which supports the same
terminal emulation as PuTTY. \#{XXX-REVIEW-BEFORE-RELEASE:}
We do not yet have a Unix port of Pageant.
terminal emulation as PuTTY.
If you don't have \i{Gtk}, you should still be able to build the
command-line tools.