DropBear ssh client - key auth issue

[serek]

Hello,

I have recently installed DropBear on my A-110. SSH server works like a charm, but I am having some issues with key authentication while trying to ssh out of my PCH to remote server (running Linux)

I have created pair of keys using 'dropbearkey' binary (found in /share/Apps/DropBear/bin/) and I treated the pair as I would usually do on Unix-flavoured OS, so private key named id_rsa placed into /root/.ssh/ and public portion of the key was copied onto my remote machine and added to authorized_keys.

Unfortunately that didn't do the trick. While trying to ssh out of my PCH I am getting following:

Code:

root@PCH-A110 bin# ssh serek@myhost.mydomain.mytld -i /root/.ssh/id_rsa      
ssh: connection to serek@myhost.mydomain.mytld:22 exited: No auth methods could be used.

As I noticed later that DropBear makes binary out of the private key (btw. don't do 'cat /root/.ssh/id_rsa' as it breaks the terminal and what worse 'reset' doesn't clear it.. but if you do than opening up 'mc' and closing it seems to reset term for me). When I convert key from binary to standard I am getting the following:

Code:

./dropbearconvert dropbear openssh /root/.ssh/id_rsa /root/.ssh/id_rsa.openssh
root@PCH-A110 bin# ssh serek@myhost.mydomain.mytld -i /root/.ssh/id_rsa.openssh
ssh: exited: string too long

Did anyone got any further with this than I did? Is there anything fundamental that I am missing..? I am pretty sure that if ssh client was embedded into DropBear than there must be the way to use it! Am I right?

Just for the clarity. I am using DropBear v0.52-3 installed using CSI on PCH-A110.

Regards,
Sergiusz

---

I have tried one more thing - enabling SSH version 1 on my remote box as I though maybe client can't do version 2 at all. Still the same results as described above