SSH kann aufgrund eines Authentifizierungsproblems nicht ausgeführt werden

643
Mrinmay Kalita

Ich kann jetzt aufgrund von Authentifizierungsproblemen keine SSH-Verbindung zu meinem API-Server herstellen. Früher musste er sich anmelden, ohne ein Passwort zu fragen. Ich habe mit ssh-copy-id versucht, den öffentlichen Schlüssel vor dem Ausführen von ssh auf den Server zu kopieren, was jedoch ebenfalls fehlschlägt, da er erneut nach dem Kennwort für die Anmeldung fragt.

Befehlsausführung: ssh -vvv -i /Users/mrinmaykalita/.ssh/id_rsa 173. *. . **

Ausgabe:

OpenSSH_7.6p1, LibreSSL 2.6.2 debug1: Reading configuration data /Users/mrinmaykalita/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 48: Applying options for * debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to 173.***.**.** port 22. debug1: Connection established. debug1: identity file /Users/mrinmaykalita/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /Users/mrinmaykalita/.ssh/id_rsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debian-4+deb7u2 debug1: match: OpenSSH_6.0p1 Debian-4+deb7u2 pat OpenSSH* compat 0x04000000 debug3: fd 5 is O_NONBLOCK debug1: Authenticating to 173.***.***.**:22 as 'mrinmaykalita' debug3: hostkeys_foreach: reading file "/Users/mrinmaykalita/.ssh/known_hosts" debug3: record_hostkey: found key type ECDSA in file /Users/mrinmaykalita/.ssh/known_hosts:10 debug3: load_hostkeys: loaded 1 keys from 173.***.***.** debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib@openssh.com,zlib debug2: compression stoc: none,zlib@openssh.com,zlib debug2: languages ctos:  debug2: languages stoc:  debug2: first_kex_follows 0  debug2: reserved 0  debug2: peer server KEXINIT proposal debug2: KEX algorithms: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: host key algorithms: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256 debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se debug2: MACs ctos: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: MACs stoc: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: compression ctos: none,zlib@openssh.com debug2: compression stoc: none,zlib@openssh.com debug2: languages ctos:  debug2: languages stoc:  debug2: first_kex_follows 0  debug2: reserved 0  debug1: kex: algorithm: ecdh-sha2-nistp256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: aes128-ctr MAC: umac-64@openssh.com compression: none debug1: kex: client->server cipher: aes128-ctr MAC: umac-64@openssh.com compression: none debug3: send packet: type 30 debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: Server host key: ecdsa-sha2-nistp256 SHA256:4PY+Dylr8QmusyDf/LELItbGGgEAH0d4+w0zywAK9c4 debug3: hostkeys_foreach: reading file "/Users/mrinmaykalita/.ssh/known_hosts" debug3: record_hostkey: found key type ECDSA in file /Users/mrinmaykalita/.ssh/known_hosts:10 debug3: load_hostkeys: loaded 1 keys from 173.***.***.** debug1: Host '173.***.***.**' is known and matches the ECDSA host key. debug1: Found key in /Users/mrinmaykalita/.ssh/known_hosts:10 debug3: send packet: type 21 debug2: set_newkeys: mode 1 debug1: rekey after 4294967296 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: SSH2_MSG_NEWKEYS received debug2: set_newkeys: mode 0 debug1: rekey after 4294967296 blocks debug2: key: /Users/mrinmaykalita/.ssh/id_rsa (0x7fd631506920), explicit debug3: send packet: type 5 debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 debug3: receive packet: type 51 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 public key: RSA SHA256:8mUbTef6GxJTz4TTxroTnj6vO2YacRUEIJzIxonpT1o /Users/mrinmaykalita/.ssh/id_rsa debug3: send_pubkey_test debug3: send packet: type 50 debug2: we sent a publickey packet, wait for reply debug3: receive packet: type 51 debug1: Authentications that can continue: publickey,password 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 mrinmaykalita@173.***.***.**'s password:  debug3: send packet: type 50 debug2: we sent a password packet, wait for reply debug3: receive packet: type 51 debug1: Authentications that can continue: publickey,password Permission denied, please try again. mrinmaykalita@173.***.***.**'s password:  

Reguläre ssh zeigt das gleiche -

Befehl-

MacBook-Pro-77:~ mrinmaykalita$ sudo ssh 173.***.***.** 

Ausgabe-

Password: The authenticity of host '173.***.***.** (173.***.***.**)' can't be established. ECDSA key fingerprint is SHA256:4PY+Dylr8QmusyDf/LELItbGGgEAH0d4+w0zywAK9c4. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '173.***.***.**' (ECDSA) to the list of known hosts. root@173.***.***.**'s password:  Permission denied, please try again. root@173.***.***.**'s password:  Permission denied, please try again. root@173.***.***.**'s password:  

Bitte führen Sie

0
Ich habe das gleiche Verhalten gesehen, als die ssh-Konfiguration root nicht erlaubte. Haben Sie kein anderes Konto, das verwendet werden kann? Ramhound vor 6 Jahren 1
Haben Sie Zugriff auf den Server, bei dem Sie sich anmelden möchten? Und wenn ja, könntest du bitte die `sshd_config'-Datei hier posten? Praveen P vor 6 Jahren 0

0 Antworten auf die Frage