This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

  • Resolved

Linux/OMAP-L138: Dropbear bublic key authentication

Part Number: OMAP-L138

Tool/software: Linux

Hello,

Due to the attacks by "Mirai" and equal, we're forced to increase the safety of our measuring devices which mainly are connected to 4g-modem/router with WiFi or ethernet and accessed from internet through port forwarding.Devices are  OMAPL138- based devices and are runnin Linux 3.3.0. We're concentrating all traffic to port 22 SSH which in OMAP- side is realized with dropbear. Communication works fine but we've faced problems with key authentication.

We've carefully been following instruction in  "wiki.openwrt.org/.../dropbear.public-key.auth"  and a number of related google-traces. Clients tried are MinGW and WinSCP in Windows and Virtualbox/Ubuntu terminal - results are the same from all clients...no connection.

Starting Dropbear with -E does not produce any valuable information. 

Below is the ssh -vvv listing of the connection trial - I would very much appreciate if someone familiar with SSH/Dropbear could check it.

Best Regards,

Risto 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

$ ssh -vvv root@192.168.1.110
OpenSSH_6.6.1, OpenSSL 1.0.1m 19 Mar 2015
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.1.110 [192.168.1.110] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier

    "stackoverflow.com/.../15563793
debug3: Could not load "/c/Users/risto/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /c/Users/risto/.ssh/id_rsa type 1
debug1: identity file /c/Users/risto/.ssh/id_rsa-cert type -1
debug1: identity file /c/Users/risto/.ssh/id_dsa type -1
debug1: identity file /c/Users/risto/.ssh/id_dsa-cert type -1
debug1: identity file /c/Users/risto/.ssh/id_ecdsa type -1
debug1: identity file /c/Users/risto/.ssh/id_ecdsa-cert type -1
debug1: identity file /c/Users/risto/.ssh/id_ed25519 type -1
debug1: identity file /c/Users/risto/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1
debug1: Remote protocol version 2.0, remote software version dropbear_2012.55
debug1: no match: dropbear_2012.55
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "192.168.1.110" from file "/c/Us
ers/risto/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /c/Users/risto/.ssh/known_host
s:2
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-
rsa-cert-v00@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-
sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hel
lman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh
.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v
01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@ope
nssh.com,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-ni
stp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour12
8,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,ae
s128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndae
l-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour12
8,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,ae
s128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndae
l-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,um
ac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hma
c-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@opens
sh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-1
28@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh
.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,um
ac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hma
c-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@opens
sh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-1
28@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh
.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group1-sha1,diffie-hellman-group14-sha
1
debug2: kex_parse_kexinit: ssh-rsa
debug2: kex_parse_kexinit: aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,ae
s256-cbc,twofish256-cbc,twofish-cbc,twofish128-cbc
debug2: kex_parse_kexinit: aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,ae
s256-cbc,twofish256-cbc,twofish-cbc,twofish128-cbc
debug2: kex_parse_kexinit: hmac-sha1-96,hmac-sha1,hmac-md5
debug2: kex_parse_kexinit: hmac-sha1-96,hmac-sha1,hmac-md5
debug2: kex_parse_kexinit: zlib,zlib@openssh.com,none
debug2: kex_parse_kexinit: zlib,zlib@openssh.com,none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: setup hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: setup hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug2: bits set: 1052/2048
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Server host key: RSA 0a:ed:5a:c5:25:d9:24:a7:4c:22:02:a0:d5:f9:d9:50
debug3: load_hostkeys: loading entries for host "192.168.1.110" from file "/c/Us
ers/risto/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /c/Users/risto/.ssh/known_host
s:2
debug3: load_hostkeys: loaded 1 keys
debug1: Host '192.168.1.110' is known and matches the RSA host key.
debug1: Found key in /c/Users/risto/.ssh/known_hosts:2
debug2: bits set: 1044/2048
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /c/Users/risto/.ssh/id_rsa (0xa021870),
debug2: key: /c/Users/risto/.ssh/id_dsa (0x0),
debug2: key: /c/Users/risto/.ssh/id_ecdsa (0x0),
debug2: key: /c/Users/risto/.ssh/id_ed25519 (0x0),
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /c/Users/risto/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /c/Users/risto/.ssh/id_dsa
debug3: no such identity: /c/Users/risto/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /c/Users/risto/.ssh/id_ecdsa
debug3: no such identity: /c/Users/risto/.ssh/id_ecdsa: No such file or director
y
debug1: Trying private key: /c/Users/risto/.ssh/id_ed25519
debug3: no such identity: /c/Users/risto/.ssh/id_ed25519: No such file or direct
ory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
root@192.168.1.110's password:

  • Hi Risto,

    See if these links will help:
    bbs.archlinux.org/viewtopic.php
    stackoverflow.com/.../could-not-load-id-rsa-as-a-rsa1-public-key

    Best Regards,
    Yordan

     


     Please make sure you read the forum guidelines first.

  • In reply to Yordan Kovachev:

    Hi Yordan,

    Thank you but I've already studied those links :-(

    My concern is that the owners of the key files are wrong. In OMAPL I have
    drw------- 2 root root 4096 Dec 18 2017 181217
    -rw------- 1 root root 789 Nov 8 23:37 authorized_keys
    -rw-rw-rw- 1 root root 427 Nov 8 16:12 dropbear_rsa_host_key

    and in PC
    -rw------- 1 emmecon emmecon 1675 Dec 18 16:44 id_rsa
    -rw-r--r-- 1 emmecon emmecon 408 Dec 18 16:44 id_rsa.pub
    -rw------- 1 emmecon emmecon 506 Dec 18 16:51 known_hosts

    if I try connection with:
    ssh -vvv root@192.168.1.110
    I think it should work???

    Should I test with another user in OMAPL, does it make sense?

    risto
  • In reply to Risto Hedman:

    Hi,

    Should I test with another user in OMAPL, does it make sense?


    root is the default user on OMAP-L138 SDK. It should work.
    Do you have OMAP-L138 LCDK at your disposal? Can you try on it with the latest TISDK?

    Best Regards,
    Yordan

     


     Please make sure you read the forum guidelines first.

  • In reply to Yordan Kovachev:

    Hi Yordan,

    Thank you and apologies for my delayed reply.

    Mode for path /home/root/.ssh indeed was wrong - now Dropbear and OpenSSH work both.

    risto

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.