Hi,
I just upgraded to 3.85 a week ago. Everything seems fine except I can't get it to detect the saved connection files. I get this with every new file I open -
" There is no entry for the server ## ## ### ### in your list of known hosts. The machine you have contacted may be a hostile machine pretending to be the server"
It also says if I add this machine and accept it I won't receive this warning again. But always do.
I've tried all that I know to and no change.
Any ideas would be great!
Are you using SSH1 or SSH2?
Brian
I was using SSH2 when this began, then tried SSH1 with no change. I have 43 files I connect to several times daily. Only about 14 of them refuse to be recognized.
And this just began with version 3.85, with no difference between SSH1 and SSH2? Is there any commonality between the 14 that are not working?
Could you email me two that have problems and two that do not? That will help me isolate the problem
Mail me here:
(bpence at celestialsoftware.net)
Hi Brian,
I decided to uninstall and start from scratch as it was so annoying. So far so good, no repeat prompt boxes. So seems to have been a glitch with the upgrade somehow(my part not yours. If this begins again, I will be sure to send you a few to examine. Thanks for such GREAT fast support.
I'm glad that uninstalling/reinstalling worked for you. I'd like to get some more information, though, so I can look into this a bit further. If there was an issue, it's likely to reappear at a later date.
The message you specified "there is no entry for server blah blah blah" is the message you get for SSH1. The message for ssh2 is a little different. The reason this is important is that SSH1 and SSH2 use slightly different mechanisms to store the key. SSH1, for example, stores the key in a file called 'ssh_known_hosts' in your 'application data\\AbsoluteTelnet' folder. SSH2 stores the key in the registry under 'HKEY_CURRENT_USER\\Software\\Celestial Software\\AbsoluteTelnet'.
So, a few things that might affect storing of the keys:
1. First, since SSH1 and SSH2 store different keys in different places, you could still get this message once for SSH2 and again for SSH1. Your scenario might be this... You try and try with SSH2 and the key won't save. You decide to switch and try again with SSH1 and it still complains about the key, so you lodge a bugreport. It will be normal in this scenario to get the warning once with SSH1. The real issue, though, would be that SSH2 wouldn't save it.
2. In SSH1, you must click the checkbox 'add to known hosts' so you don't get the message again. In SSH2, you click the button 'accept and save'
3. bad permissions or inability to read or write the ssh_known_hosts file or the registry will cause the entry to be lost, resulting in being prompted again.
4. Remote users whose registry and files are copied across the network (I believe this is called a traveling profile) may have problems if the registry or local data is not kept in sync.
So one more question... When you get this error message, do you get it immediately again by disconnecting and reconnecting even though you 'accept and save'?
Brian
Hi!
Do you have an update on this? Could you comment on whether any of the suggestions from my last post may have been affecting you?
Brian
Hi!
I did finally find the answer to this. A strange random error was causing the filename of the known_hosts file to get altered. It was never the same twice, so even though the keys were getting written, they could never be found.
I'm not sure why reinstalling would fix it. It would be likely that the problem would come back.
This is fixed in the new beta:
