Jude,
I have a question.
i did run your command
ssh-keygen -r hostname.
Listed several keys associated.
However the new attempt did not let me save the new host, I have seen this
message.
Instead I get the error
hostname key has changed and you have requested strict checking.
I am paraphrasing.
Is there a way to run the ssh-keygen or ssh command without the strict
checking request so the new one can be saved?
Indeed things are in the known_host file as Chime suggested.
Worst case, I suppose? I can open known_hosts in nano, which defaults to
the bottom, and put the key there..but dreamhost will have to provide
that.
Thanks,
Karen
On Tue, 13 Feb 2024, Jude DaShiell wrote:
First delete the outdated key since it won't work any longer, then login
again and a new key will be added for you by the external server.
ssh-keygen -r hostname
should get that first task done.
When you log in without a key you'll be asked if you want to trust the
system and your answer is yes.
That adds the new key and you're on your way.
--
Jude <jdashiel at panix dot com>
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.
Please use in that order."
Ed Howdershelt 1940.
On Tue, 13 Feb 2024, Karen Lewellen wrote:
Hi all,
Will aim to keep this simple.
is there an option with ssh from the command line that allows you to update
new keys for the known host list?
I ssh into my dreamhost office workspace from shellworld, as in
ssh email@email.thingy.
I provide the password, reaching the dreamhost shell structure for the domains
they host on behalf of my employer.
dreamhost moved our services to a new server, changing our ip address, not an
issue, but also changing the fingertip keys <hope that is the correct term,
previously saved for my access from shellworld..who seems to use a strict
matching process of some kind.
My hope? is that there is an option that tells ssh to update the identifiers
used for known hosts?
Thanks,
Kare