This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
nix:ssh_fingerprints [2018/07/06 11:58] tdobes created |
nix:ssh_fingerprints [2018/07/06 11:59] (current) tdobes |
||
---|---|---|---|
Line 19: | Line 19: | ||
If that happens, Basically, you just need to tell SSH to forget about the old server. To do this, you can delete the line(s) with the problematic key in the file ''~/.ssh/known_hosts'' -- Recent versions of ssh provide us with a handy command line tool to do that. You can just run this command: | If that happens, Basically, you just need to tell SSH to forget about the old server. To do this, you can delete the line(s) with the problematic key in the file ''~/.ssh/known_hosts'' -- Recent versions of ssh provide us with a handy command line tool to do that. You can just run this command: | ||
- | ''ssh-keygen -R {servername}'' | + | <code>ssh-keygen -R {servername}</code> |
(substitute {servername} for the name of the server in question, such as linux.cs.uchicago.edu) | (substitute {servername} for the name of the server in question, such as linux.cs.uchicago.edu) | ||
+ | |||
This command will search the file for any lines pertaining to {servername} and delete them. Then, you can run the normal ssh command to reconnect and your computer will act as though it's seeing the server for the first time (asking you to verify the fingerprint, then connecting you as expected). | This command will search the file for any lines pertaining to {servername} and delete them. Then, you can run the normal ssh command to reconnect and your computer will act as though it's seeing the server for the first time (asking you to verify the fingerprint, then connecting you as expected). |