1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-04-10 15:48:06 -05:00

Update docs for new host key prompts.

The message wording changed in d1dc1e927c.
This commit is contained in:
Jacob Nevins 2022-01-11 23:44:21 +00:00
parent e7b9eea786
commit 16ead30c0f
2 changed files with 6 additions and 5 deletions

View File

@ -10,8 +10,8 @@ self-explanatory. If you get an error message which is not listed in
this chapter and which you don't understand, report it to us as a
bug (see \k{feedback}) and we will add documentation for it.
\H{errors-hostkey-absent} \q{The server's host key is not cached in
the registry}
\H{errors-hostkey-absent} \q{The host key is not cached for this
server}
This error message occurs when PuTTY connects to a new SSH server.
Every server identifies itself by means of a host key; once PuTTY
@ -35,7 +35,7 @@ See \k{gs-hostkey} for more information on host keys.
\H{errors-hostkey-wrong} \q{WARNING - POTENTIAL SECURITY BREACH!}
This message, followed by \q{The server's host key does not match
the one PuTTY has cached in the registry}, means that PuTTY has
the one PuTTY has cached for this server}, means that PuTTY has
connected to the SSH server before, knows what its host key
\e{should} be, but has found a different one.

View File

@ -50,8 +50,9 @@ section.
If you are using SSH to connect to a server for the first time, you
will probably see a message looking something like this:
\c The server's host key is not cached in the registry. You have no
\c guarantee that the server is the computer you think it is.
\c The host key is not cached for this server:
\c ssh.example.com (port 22)
\c You have no guarantee that the server is the computer you think it is.
\c The server's ssh-ed25519 key fingerprint is:
\c ssh-ed25519 255 SHA256:TddlQk20DVs4LRcAsIfDN9pInKpY06D+h4kSHwWAj4w
\c If you trust this host, press "Accept" to add the key to PuTTY's