Hi,
I (cross) compiled lshd for an xscale (arm) device and set the public key things as described in the manual.
But when I try to login with:
laabs$ lsh -lroot 100.100.100.10
I get the following error from the lshd server:
lshd: Accepting connection from 100.100.100.6, port 58750 lshd: Initiating handshake with 100.100.100.6 lshd: Client version: SSH-2.0-lsh_1.5.4 lsh - a free ssh Server version: SSH-2.0-lshd_1.5.4 lsh - a free ssh lshd: Received KEXINIT message. Key exchange initated. lshd: Selected keyexchange algorithm: diffie-hellman-group1-sha1 with hostkey algorithm: ssh-dss lshd: Selected bulk algorithms: (client to server, server to client) Encryption: (aes256-cbc, aes256-cbc) Message authentication: (hmac-sha1, hmac-sha1) Compression: (none, none) lshd: garbage collecting... lshd: Objects alive: 100, garbage collected: 15 lshd: Received NEWKEYS. Key exchange finished. lshd: Setting session key lifetime to 5400 seconds lshd: Unknown publickey algorithm spki-sign-dss lshd: Disconnect for reason 14: No more auth methods available lshd: Connection died.
I tried to set an other publickey algorithm but I didn't found an option of lsh. I didn't subscibed to this mailing list .. but I'll look into the archive ...
Thank you Martin Laabs
Martin Laabs s8606710@rcs.urz.tu-dresden.de writes:
laabs$ lsh -lroot 100.100.100.10
Note that by default, lsh doesn't allow root login. You have to use lshd --root-login if you need that.
lshd: Unknown publickey algorithm spki-sign-dss
This is kind-of normal (spki support in lshd is not finished). If the client has a dsa key, it will try public-key auth with the algorithms "spki-sign-dss" and the standard "ssh-dss", as well as with password auth. So "spki-sign-dss" doesn't really matter.
Regards, /Niels