ubuntuusers.de

ssh - Connection closed

Status: Ungelöst | Ubuntu-Version: Lubuntu 12.04 (Precise Pangolin)
Antworten |

Panathinaikos

Anmeldungsdatum:
21. Juli 2013

Beiträge: 13

Hallo,

Ich habe hier zwei Laptops, die sich gegenseitig per ssh connecten sollten. In eine Richtung funktioniert es einwandfrei, der zweite weigert sich aber konsequent mit der Meldung:

Connection closed by und.die.ip.nummer

Weitere Versuche mit dem Befehl 'ssh benutzer@pc2 -vvv' zeigen mir unter anderem:

Connectinon established.
Incorrect RSA1 identifier
Could not load "/home/benutzer/.ssh/id_dsa" as a RSA1 public key
......
......
Authentications that can continue: publickey,password
we did not send a packet, disable method
authethod_lookup password
remaining preferred: ,password
authmethod_is_enabled password
Next authentication method: password
benutzer@pc2's password:
packet_send2:..
we sent a password packet, wait for replay
Connection closed by ip.adr.es.se

weiter komme nicht

Vibaf

Ehemaliger

Anmeldungsdatum:
27. Dezember 2007

Beiträge: 3046

Panathinaikos schrieb:

Incorrect RSA1 identifier
Could not load "/home/benutzer/.ssh/id_dsa" as a RSA1 public key

Hast du Keys selbst erzeugt? Wie sieht denn die Ausgabe von

ls -lah ~/.ssh/

aus? Bitte in einem {{{Code}}}-Block posten.

Panathinaikos

(Themenstarter)

Anmeldungsdatum:
21. Juli 2013

Beiträge: 13

Hi Vibaf,

Hast du Keys selbst erzeugt?

Bei der Suche bin ich auf einige Vorschläge aufmerksam geworden, die Befehle habe ich dann auch ausgeführt:

ssh-keygen -t rsa
ssh-keygen -t dsa
ssh-heygen -t ecdsa

Ausgabe von 'ls -lah ~/.ssh/':

drwx------  2 benutzer benutzer 4,0K Sep  6 20:40 .
drwxr-xr-x 50 benutzer benutzer 4,0K Sep  6 20:51 ..
-rw-------  1 benutzer benutzer  668 Sep  6 20:40 id_dsa
-rw-r--r--  1 benutzer benutzer  601 Sep  6 20:40 id_dsa.pub
-rw-------  1 benutzer benutzer  227 Sep  6 20:40 id_ecdsa
-rw-r--r--  1 benutzer benutzer  173 Sep  6 20:40 id_ecdsa.pub
-rw-------  1 benutzer benutzer 1,7K Sep  6 20:37 identity
-rw-r--r--  1 benutzer benutzer  393 Sep  6 20:37 identity.pub
-rw-------  1 benutzer benutzer 1,7K Sep  6 20:40 id_rsa
-rw-r--r--  1 benutzer benutzer  393 Sep  6 20:40 id_rsa.pub
-rw-r--r--  1 benutzer benutzer 1,3K Sep  6 20:52 known_hosts

Panathinaikos

(Themenstarter)

Anmeldungsdatum:
21. Juli 2013

Beiträge: 13

Meine Vermutung ist, dass es die doppelten key's sind: bei Anmeldung wurde ein zweites key erstellt und wird vom zweiten Rechner nicht angenommen.

ok, habe den key mit dem Befehl 'ssh-keygen -R hostname' entfernt.

Die Antwort sieht so aus:

The authenticity of host 'rechnername (ip.ad.re.sse)' can't be established.
ECDSA key fingerprint is (hexadezimalzahlen mit Doppelpunkt dazwischen)
Are you sure you want to continue connecting (yes/no)?

bei allen 'no' Fehlermeldung:

no
Host key verification failed.

bei 'yes' kommt weitere Abfrage:

Warning: Permanently added 'rechnername' (ECDSA) to the list of known hosts.
Warning: the ECDSA host key for 'rechnername' differs from the key for the IP address 'ip.ad.re.sse'

Offending key for IP in /home/benutzer/.ssh/known_hosts:4
Are you sure you want to continue connecting (yes/no)?

und mit 'yes'

Connection closed by ip.ad.re.sse

Suche nach einer Lösung

Panathinaikos

(Themenstarter)

Anmeldungsdatum:
21. Juli 2013

Beiträge: 13

habe versucht die Anleitung zu befolgen. PasswordAuthentication auf yes gesetzt, 'ssh-keygen -R host' auf beiden Rechnern durchgeführt und den host rebootet

ssh-copy-id -i ~/.ssh/id_rsa.pub benutzer@hostrechner
Warning: the ECDSA host key for 'hostrechner' differs from the key for the IP address 'ip.ad.res.se'
Offending key for IP in /home/benutzer/.ssh/known_hosts:4
Matching host key in /home/benutzer/.ssh/known_hosts:9
Are you sure you want to continue connecting (yes/no)? yes
Connection closed by ip.ad.res.se

ssh scheint sehr komplex..

diesch Team-Icon

Avatar von diesch

Anmeldungsdatum:
18. Februar 2009

Beiträge: 5072

Wohnort: Brandenburg an der Havel

Existiert auf dem Server die Datei /etc/nologin? Wenn ja, lösche sie und versuche es nochmal.

Falls nein, beende den sshd auf dem Server und starte ihn mit

1
sudo /usr/sbin/sshd -d

. Welche Meldungen bekommst du, wenn der Client versucht, sich anzumelden?

Panathinaikos

(Themenstarter)

Anmeldungsdatum:
21. Juli 2013

Beiträge: 13

JA! es geht nun 😀

# /usr/sbin/sshd -d
debug1: sshd version OpenSSH_6.0p1 Ubuntu-4
debug1: read PEM private key done: type RSA
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024
debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024
debug1: private host key: #1 type 2 DSA
debug1: could not open key file '/etc/ssh/ssh_hos_ecdsa_key': No such file or directory
Could not load host key: /etc/ssh/ssh_hos_ecdsa_key
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.4.132 port 44228
debug1: Client protocol version 2.0; client software version OpenSSH_6.0p1 Ubuntu-4
debug1: match: OpenSSH_6.0p1 Ubuntu-4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Ubuntu-4
debug1: permanently_set_uid: 112/65534 [preauth]
debug1: list_hostkey_types: ssh-rsa,ssh-dss [preauth]
debug1: SSH2_MSG_KEXINIT sent [preauth]
debug1: SSH2_MSG_KEXINIT received [preauth]
debug1: kex: client->server aes128-ctr hmac-md5 none [preauth]
debug1: kex: server->client aes128-ctr hmac-md5 none [preauth]
debug1: expecting SSH2_MSG_KEX_ECDH_INIT [preauth]
debug1: SSH2_MSG_NEWKEYS sent [preauth]
debug1: expecting SSH2_MSG_NEWKEYS [preauth]
debug1: SSH2_MSG_NEWKEYS received [preauth]
debug1: KEX done [preauth]
debug1: userauth-request for user benutzer service ssh-connection method none [preauth]
debug1: attempt 0 failures 0 [preauth]
debug1: PAM: initializing for "benutzer"
debug1: PAM: setting PAM_RHOST to "host1"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth-request for user benutzer service ssh-connection method publickey [preauth]
debug1: attempt 1 failures 0 [preauth]
debug1: test whether pkalg/pkblob are acceptable [preauth]
debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024
debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys': No such file or directory
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys2
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys2': No such file or directory
debug1: restore_uid: 0/0
Failed publickey for benutzer from 192.168.4.132 port 44228 ssh2
debug1: userauth-request for user benutzer service ssh-connection method publickey [preauth]
debug1: attempt 2 failures 1 [preauth]
debug1: test whether pkalg/pkblob are acceptable [preauth]
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys': No such file or directory
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys2
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys2': No such file or directory
debug1: restore_uid: 0/0
Failed publickey for benutzer from 192.168.4.132 port 44228 ssh2
debug1: userauth-request for user benutzer service ssh-connection method publickey [preauth]
debug1: attempt 3 failures 2 [preauth]
debug1: test whether pkalg/pkblob are acceptable [preauth]
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys': No such file or directory
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys2
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys2': No such file or directory
debug1: restore_uid: 0/0
Failed publickey for benutzer from 192.168.4.132 port 44228 ssh2
debug1: userauth-request for user benutzer service ssh-connection method password [preauth]
debug1: attempt 4 failures 3 [preauth]
debug1: PAM: password authentication accepted for benuzer
debug1: do_pam_account: called
Accepted password for benutzer from 192.168.4.132 port 44228 ssh2
debug1: monitor_read_log: child log fd closed
debug1: monitor_child_preauth: benutzer has been authenticated by privileged process
debug1: PAM: establishing credentials
User child is on pid 6225
debug1: SELinux support disabled
debug1: PAM: establishing credentia# /usr/sbin/sshd -d
debug1: sshd version OpenSSH_6.0p1 Ubuntu-4
debug1: read PEM private key done: type RSA
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024
debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024
debug1: private host key: #1 type 2 DSA
debug1: could not open key file '/etc/ssh/ssh_hos_ecdsa_key': No such file or directory
Could not load host key: /etc/ssh/ssh_hos_ecdsa_key
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.4.132 port 44228
debug1: Client protocol version 2.0; client software version OpenSSH_6.0p1 Ubuntu-4
debug1: match: OpenSSH_6.0p1 Ubuntu-4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Ubuntu-4
debug1: permanently_set_uid: 112/65524 [preauth]
debug1: list_hostkey_types: ssh-rsa,ssh-dss [preauth]
debug1: SSH2_MSG_KEXINIT sent [preauth]
debug1: SSH2_MSG_KEXINIT received [preauth]
debug1: kex: client->server aes128-ctr hmac-md5 none [preauth]
debug1: kex: server->client aes128-ctr hmac-md5 none [preauth]
debug1: expecting SSH2_MSG_KEX_ECDH_INIT [preauth]
debug1: SSH2_MSG_NEWKEYS sent [preauth]
debug1: expecting SSH2_MSG_NEWKEYS [preauth]
debug1: SSH2_MSG_NEWKEYS received [preauth]
debug1: KEX done [preauth]
debug1: userauth-request for user benutzer service ssh-connection method none [preauth]
debug1: attempt 0 failures 0 [preauth]
debug1: PAM: initializing for "benutzer"
debug1: PAM: setting PAM_RHOST to "host1"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth-request for user benutzer service ssh-connection method publickey [preauth]
debug1: attempt 1 failures 0 [preauth]
debug1: test whether pkalg/pkblob are acceptable [preauth]
debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024
debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys': No such file or directory
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys2
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys2': No such file or directory
debug1: restore_uid: 0/0
Failed publickey for benutzer from 192.168.4.132 port 44228 ssh2
debug1: userauth-request for user benutzer service ssh-connection method publickey [preauth]
debug1: attempt 2 failures 1 [preauth]
debug1: test whether pkalg/pkblob are acceptable [preauth]
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys': No such file or directory
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys2
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys2': No such file or directory
debug1: restore_uid: 0/0
Failed publickey for benutzer from 192.168.4.132 port 44228 ssh2
debug1: userauth-request for user benutzer service ssh-connection method publickey [preauth]
debug1: attempt 3 failures 2 [preauth]
debug1: test whether pkalg/pkblob are acceptable [preauth]
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys': No such file or directory
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: trying public key file /home/benutzer/.ssh/authorized_keys2
debug1: Could not open authorized keys '/home/benutzer/.ssh/authorized_keys2': No such file or directory
debug1: restore_uid: 0/0
Failed publickey for benutzer from 192.168.4.132 port 44228 ssh2
debug1: userauth-request for user benutzer service ssh-connection method password [preauth]
debug1: attempt 4 failures 3 [preauth]
debug1: PAM: password authentication accepted for benutzer
debug1: do_pam_account: called
Accepted password for benutzer from 192.168.4.132 port 44228 ssh2
debug1: monitor_read_log: child log fd closed
debug1: monitor_child_preauth: benutzer has been authenticated by privileged process
debug1: PAM: establishing credentials
User child is on pid 6215
debug1: SELinux support disabled
debug1: PAM: establishing credentials
debug1: permanently_set_uid: 1000/1000
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 0 win 1048576 max 16384
debug1: input_session_request
debug1: channel 0: new [server-session]
debug1: session_new: session 0
debug1: session_open: channel 0
debug1: session_open: session 0: link with channel 0
debug1: server_input_channel_open: confirm session
debug1: server_input_global_request: rtype no-more-sessions@openssh.com want_reply 0
debug1: server_input_channel_req: channel 0 request pty-req reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req pty-req
debug1: Allocating pty.
debug1: session_new: session 0
debug1: SELinux support disabled
debug1: session_pty_req: session 0 alloc /dev/pts/2
debug1: server_input_channel_req: channel 0 request env reply 0
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req env
debug1: server_input_channel_req: channel 0 request shell reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req shell
debug1: Setting controlling tty using TIOCSCTTY.
ls
debug1: permanently_set_uid: 1000/1000
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 0 win 1048576 max 16384
debug1: input_session_request
debug1: channel 0: new [server-session]
debug1: session_new: session 0
debug1: session_open: channel 0
debug1: session_open: session 0: link with channel 0
debug1: server_input_channel_open: confirm session
debug1: server_input_global_request: rtype no-more-sessions@openssh.com want_reply 0
debug1: server_input_channel_req: channel 0 request pty-req reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req pty-req
debug1: Allocating pty.
debug1: session_new: session 0
debug1: SELinux support disabled
debug1: session_pty_req: session 0 alloc /dev/pts/2
debug1: server_input_channel_req: channel 0 request env reply 0
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req env
debug1: server_input_channel_req: channel 0 request shell reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req shell
debug1: Setting controlling tty using TIOCSCTTY.

Der Fehler müsste in der Liste stehen. "Could not open authorized keys '/home/benutzer/.ssh/authorized_keys2': No such file or directory"

Soweit ich es mitgekriegt habe, muss die Verbindung explizit mit 'sudo /usr/sbin/sshd -d' gestartet werden, sonst kommt die Meldung:

"ssh: connect to host host1 prot 22: Connection refused"

xabbuh Team-Icon

Anmeldungsdatum:
25. Mai 2006

Beiträge: 6411

Panathinaikos schrieb:

Soweit ich es mitgekriegt habe, muss die Verbindung explizit mit 'sudo /usr/sbin/sshd -d' gestartet werden, sonst kommt die Meldung:

"ssh: connect to host host1 prot 22: Connection refused"

Nein, eigentlich ist das nicht erforderlich. Lief der SSH Server vorher denn überhaupt?

Antworten |