Der ssh-server ist für Passwort authentication konfiguriert.
Eine Verbindung mit ssh -v bringt z.B. folgende Erkenntnisse:
user@local_machine:~$ ssh user@raspberrypi -v
OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to raspberrypi [ip_v6_adress] port 22.
debug1: connect to address [ip_v6_adress] port 22: Connection refused
debug1: Connecting to raspberrypi [192.168.0.3] port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
ssh_exchange_identification: read: Connection reset by peer
Lösung in diesem Fall war, den ssh-Key auf dem lokalen Rechner zu löschen, so dass der Austausch beim nächsten Login erneut stattfindet und der Key gecached wird:
ssh-keygen -R 192.168.1.123
Keine Kommentare:
Kommentar veröffentlichen