1. ronsch, 24.12.2013 #1
    ronsch

    ronsch Threadstarter Neues Mitglied

    Hallo zusammen,

    verzweifelt versuche ich dne SSH-Server (Public Key) zum laufen zu bringen. Hat jemand eine Idee, wo mein Fehler liegen koennte?

    Vielen Dank schonmal und schoene Guesse!:)

    Code:
    [user]@X61s:~$ ssh -vT root@192.168.2.213 
     OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012 
     debug1: Reading configuration data /etc/ssh/ssh_config 
     debug1: /etc/ssh/ssh_config line 19: Applying options for * 
     debug1: Connecting to 192.168.2.213 [192.168.2.213] port 22. 
     debug1: Connection established. 
     debug1: identity file /home/[user]/.ssh/id_rsa type 1 
     debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 
     debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 
     debug1: identity file /home/[user]/.ssh/id_rsa-cert type -1 
     debug1: identity file /home/[user]/.ssh/id_dsa type -1 
     debug1: identity file /home/[user]/.ssh/id_dsa-cert type -1 
     debug1: identity file /home/[user]/.ssh/id_ecdsa type -1 
     debug1: identity file /home/[user]/.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_6.0p1 Debian-3ubuntu1 
     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 18:51:58:ca:42:b0:17:5e:1d:3c:f9:0d:d7:59:02:74 
     debug1: Host '192.168.2.213' is known and matches the RSA host key. 
     debug1: Found key in /home/[user]/.ssh/known_hosts:13 
     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 
     debug1: Next authentication method: publickey 
     debug1: Offering RSA public key: /home/[user]/.ssh/id_rsa 
     debug1: Authentications that can continue: publickey 
     debug1: Trying private key: /home/[user]/.ssh/id_dsa 
     debug1: Trying private key: /home/[user]/.ssh/id_ecdsa 
     debug1: No more authentication methods to try. 
     Permission denied (publickey). 
      
    Berechtigungen auf dem Defy:
    Code:
    root@android:/data # ls -l
    drwxr-xr-x root     root              2013-12-24 13:31 dropbear
    
    Code:
    root@android:/data/dropbear # ls -al
    -rw-rw-rw- root     root           24 2013-12-23 21:44 .ptofile
    drwx------ root     root              2013-12-24 00:31 .ssh
    -rw-rw-rw- root     root            5 2013-12-24 13:31 dropbear.pid
    -rw-r--r-- root     root          458 2013-12-23 21:36 dropbear_dss_host_key
    -rw-r--r-- root     root          425 2013-12-23 21:38 dropbear_rsa_host_key
    
    Code:
    root@android:/data/dropbear/.ssh # ls -l
    -rws------ root     root          396 2013-12-24 00:31 authorized_keys
    
     
  2. vps, 29.12.2013 #2
    vps

    vps Fortgeschrittenes Mitglied

    Hallo ronsch,

    Ich kenne bei dropbear ein Kompatibilitätsproblem mit aktuellen SSH Clients, das doch durch Auswahl der blowfish Verschlüsselung beheben läßt. Link gerade nicht parat aber probiere doch mal

    ssh -c blowfish ....



    Gesendet von meinem MB525 mit der Android-Hilfe.de App
     
  1. Android-Hilfe.de verwendet Cookies um Inhalte zu personalisieren und dir den bestmöglichen Service zu gewährleisten. Wenn du auf der Seite weitersurfst stimmst du der Cookie-Nutzung zu.  Ich stimme zu.