I did delete the known_hosts file (though I did it via the Finder—User folder > CMD + Shift + G and type “.ssh”. Delete the known hosts file) and a new file was created upon reboot. Still no entry.
EH tech support said yesterday:
“Perhaps we have a coincidence in somehting on your network or ISP blocking you at the same time that the key had changed. Let me see what else I can dig up in the meantime.”
But I haven’t heard anything back yet.
Along with the assistance you are getting from our support staff, if you would be so kind as to follow the steps outlined in our news post, rather than deleting the file via the Finder. While the act of deleting it via the Finder seems to do the same thing, we know for sure that following the simple steps via a Terminal window do indeed work.
This “issue” is not a unique issue to just us, any ssh or sFTP server that needs to do an OS reinstall, regenerate ssh keys on a periodic basis for security reasons, or as in the case of a few months ago, any place running Debian or Ubuntu Linux would have had to regenerate their ssh and SSL server keys because of a very weak key generation routine in those OSs that was found.
What added to the issues was that it seems that most OS X sFTP GUI applications do not provide proper error reporting, so claiming “permission denied” rather then, like Filezilla (and most Windows sFTP clients), simply telling you that the server key changed, do you want to accept the new one, and updating from there. As a long time OS X user I am actually shocked at how few sFTP clients handle this properly, and in fact handle it extremely poorly in my book.
I do apologize you are having extended issues with this as the steps my staff are stepping you through have universally worked for all other clients that have contacted us directly, or simply followed our server news posting instructions.
Thank you.