nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-04-02 19:50:12 -05:00
Code Issues Projects Releases Wiki Activity

Docs: clarify wording about host key staleness.

Browse Source 
I stumbled over this paragraph on a re-read.
This commit is contained in:
Jacob Nevins 2025-02-11 23:52:24 +00:00
parent b205622789
commit 1c86360a03
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/using.but
View File

@ -184,14 +184,14 @@ new key). That key will be used for the rest of the current session;
it may not actually be used for future sessions, depending on your it may not actually be used for future sessions, depending on your
preferences (see \k{config-ssh-hostkey-order}). preferences (see \k{config-ssh-hostkey-order}).
Normally, PuTTY will carry on using a host key it already knows, even Normally, PuTTY will carry on using a host key it already knows for
if the server offers key formats that PuTTY would otherwise prefer, new sessions, even if the server starts offering key formats that
to avoid host key prompts. As a result, if you've been using a server PuTTY would otherwise prefer, to avoid host key prompts. As a result,
for some years, you may still be using an older key than a new user if you've been using a server for some years, you may still be using
would use, due to server upgrades in the meantime. The SSH protocol an older type of key than a new user would use, due to server
unfortunately does not have organised facilities for host key migration upgrades in the meantime. The SSH protocol unfortunately does not
and rollover, but this allows you to \I{host keys, upgrading}manually have organised facilities for host key migration and rollover, but
upgrade. this allows you to \I{host keys, upgrading}manually upgrade.
} }
\b \I{Break, SSH special command}Break \b \I{Break, SSH special command}Break