-- In Jim Jackson <> wrote:
> Check the permissions on the /home/flr/.ssh/
> directory and on the key files in that directory.
> They must not be world Readable (or even group I
> think).
Let's see... the only file in that client directory is a file named
"known_hosts"
On the server side there is no .ssh file anywhere. In /etc/dropbear there is a
single key file with -rw------- as the attributes.
What's also interesting is that my SSH client has zero problem getting in to a
different device running a "real" ssh (not DropBear), it is only only failing
with my installation of DropBear. On another device I have:
$ ssh -v
OpenSSH_5.9p1, OpenSSL 0.9.8t 18 Jan 2012
debug1: Connecting to 10.232.48.114 [10.232.48.114] port 22.
debug1: Connection established.
debug1: identity file /home/flr/.ssh/id_rsa type 1
debug1: identity file /home/flr/.ssh/id_rsa-cert type -1
debug1: identity file /home/flr/.ssh/id_dsa type -1
debug1: identity file /home/flr/.ssh/id_dsa-cert type -1
debug1: identity file /home/flr/.ssh/id_ecdsa type -1
debug1: identity file /home/flr/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version dropbear_0.52
debug1: no match: dropbear_0.52
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Server host key: RSA 82:58:7e:02:a5:53:64:5e:08:5e:bb:f4:ce:71:73:dc
debug1: Host '10.232.48.114' is known and matches the RSA host key.
debug1: Found key in /home/flr/.ssh/known_hosts:2
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/flr/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/flr/.ssh/id_dsa
debug1: Trying private key: /home/flr/.ssh/id_ecdsa
debug1: Next authentication method: password
password:
debug1: Authentication succeeded (password).
Authenticated to 10.232.48.114 ([10.232.48.114]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
BusyBox v1.17.1 (2010-10-25 16:01:06 PDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.
#
So my client side SSH is working, my RSA key file creation worked, it's failing
with DropBear.
When I generate an RSA key on a target device do I need to upload a file to the
target device, maybe?
Thanks!
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|