On Wed, Aug 27, 2008 at 11:12:53PM -0700, James G. Sack (jim) wrote:
Yeah, openssh is not real good at telling the client why something failed <sigh>.
Some of this is intentional, to not give too much information to an attacker. But, there might be something useful in the hosts log file. The daemon can be run with some additional verbosity. It's best to run from the server's console, kill the regular sshd, and restart with '-d' which will spew information out at you.
Well, the ~user/known_hosts file is not a mythbox settings result, it is a history result. I am very familiar with client problems when a server host key changes, but maybe something similar happens when the client's host key changes.
Clients hosts don't have keys in ssh. You authenticate to the server with either one of your authorized keys, or with a password, or whatever sshd is configured to accept.
I'm stretching here, but imagining that you get different IP's for wired and wireless, and that your earlier windows connection perhaps effectively interferes with connecting from the linux OS because the IP is the same but the hostkey is different.
Again, no keys on the client. But, there could be arp problems. However, it sounds like the connection is getting quite a bit further. David -- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
