1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00

Docs: tweak certified-host-key warning responses.

Mainly to try to clarify that if you're sat at this warning dialog/
prompt, no response you make to it will cause a new CA to be trusted for
signing arbitrary host keys.
This commit is contained in:
Jacob Nevins 2022-10-21 19:57:35 +01:00
parent 5716c638a5
commit bb1ebc9b57

View File

@ -78,16 +78,17 @@ configuration, or if your CA configuration involves two overlapping
domains, or something similar.
So, unfortunately, you'll have to work out what to do about it
yourself: install a new CA key (if you're really sure you trust it),
or edit your configuration in some other way, or abandon the
connection.
yourself: make an exception for this specific case, or abandon this
connection and install a new CA key before trying again (if you're
really sure you trust the CA), or edit your configuration in some
other way, or just stop trying to use this server.
If you're convinced that this particular server is legitimate even
though the CA is not one you trust, PuTTY will let you cache the
certified host key in the same way as an uncertified one. Then that
particular certificate will be accepted on the next connection, even
though other certificates signed by the same CA will still be
rejected.
certified host key, treating it in the same way as an uncertified one.
Then that particular certificate will be accepted for future
connections to this specific server, even though other certificates
signed by the same CA will still be rejected.
\H{errors-ssh-protocol} \q{SSH protocol version 2 required by our
configuration but remote only provides (old, insecure) SSH-1}