Hello list,

we have sshd installed in our client chroots, so that root can have
remote access to running clients. (We mainly use this for remote
shutdown of clients.)

After upgrade from 12.04 LTS to 13.04, root cannot connect to running
clients, although sshd is running.

The reason is that clients have no ssh host keys! They are actively
removed during generation of client chroots, due to the following line
in /etc/ltsp/ltsp-update-image.excludes:

----------- snip -----------
etc/ssh/ssh_host_*_key
----------- snip -----------

In consequence, when trying to ssh into the client, I see the following
in the client's /var/log/auth.log:

----------- snip -----------
Jul 21 16:27:46 ltsp52977 sshd[4248]: error: Could not load host key:
/etc/ssh/ssh_host_rsa_key
Jul 21 16:27:46 ltsp52977 sshd[4248]: error: Could not load host key:
/etc/ssh/ssh_host_dsa_key
Jul 21 16:27:46 ltsp52977 sshd[4248]: error: Could not load host key:
/etc/ssh/ssh_host_ecdsa_key
Jul 21 16:27:46 ltsp52977 sshd[4248]: fatal: No supported key exchange
algorithms [preauth]
----------- snip -----------

My question: How am I supposed to ssh into a running client with its
host keys removed? Is this a bug, or am I missing something stupid?

Thanks for your help,
regards,
Rüdiger

-- 
Dr. Rüdiger Kupper <k...@kg-fds.de>
Kepler-Gymnasium Freudenstadt

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_____________________________________________________________________
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

Reply via email to