The key type can be determined automatically from the content of the public key, and the comment is optional, to make identifying individual keys easier.
The only required element is the public key blob itself.
Offending ECDSA key in /home/guest/.ssh/known_hosts:2 remove with: ssh-keygen -f "/home/guest/.ssh/known_hosts" -R username.ECDSA host key for username.has changed and you have requested strict checking. Which begs the following questions: if this file doesn't even exist, where's the discrepancy noted in the error message? Thanks to anyone willing to work through this with me!
-Jerry I should add that I am able to ssh locally using the locally assigned ip address.
I have 3 RHEL machines that were installed approximately the same time.
Two of the three ssh RSA key login works as expected, but the third machine, RSA key login has never worked. During my investigations, I discovered that ~/.ssh/known_hosts does not get updated, and is empty, despite having logged in from a number of machines.
One machine attempts to access another machine and presents its key pair.
This means that either the Server administrator has changed the host key, or you ...
It is also possible that the DSA host key has just been changed.
When keys are uploaded to the Id M entry, the key format can be either an Open SSH-style key or a raw RFC 4253-style blob.
Any RFC 4253-style key is automatically converted into an Open SSH-style key before it is imported and saved into the Id M LDAP server.