On Wed, Dec 05, 2012 at 04:55:37PM -0500, John Hupp wrote: > But > "ssh <client IP>" or "ssh <user>@<client IP>" fails from a server xterm with > "Read from socket failed: connection reset by peer" and in the forwarded > client > syslog I see: > > Dec 4 15:23:53 ltsp135 sshd[3179]: error: Could not load host key: /etc/ssh/ > ssh_host_rsa_key > Dec 4 15:23:53 ltsp135 sshd[3179]: error: Could not load host key: /etc/ssh/ > ssh_host_dsa_key > Dec 4 15:23:53 ltsp135 sshd[3179]: error: Could not load host key: /etc/ssh/ > ssh_host_ecdsa_key > Dec 4 15:23:53 ltsp135 sshd[3179]: fatal: No supported key exchange > algorithms > [preauth]
At least one of those keys is needed for sshd to operate. It's what's used to negotiate an encrypted connection, even for password based authentication. > I also tried ssh -o PreferredAuthentications=password with the same result. > > My only thought concerns the fact that I created the NBD image with > "ltsp-update-image --cleanup /" and --cleanup temporarily removes the user > accounts, logs, caches, etc. If that means that it removed my > .ssh/known_hosts > file, then perhaps that somehow explains the behavior. Newer versions of ltsp-cleanup, which is what ltsp-update-image calls, remove the ssh keys in /usr/share/ltsp/cleanup.d/*ssh, although should regenerate them as well. Maybe the older version of ltsp doesn't. live well, vagrant ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
