Archiv verlassen und diese Seite im Standarddesign anzeigen : keine Verbindung zu Raspberry OSMC per SSH
Hallo Ihr Lieben,
komme irgendwie nicht auf mein Raspberry Kodi Mediacenter mit aktuellen OSMC. Wollte paar Filme rüber schieben aber die SSH-Verbindung lässt sich nicht aufbauen, obwohl der SSH-Dienst auf dem Kodi Mediacenter aktiv ist und der Port22 von aussen erreichbar ist. Er fragt zwar das Passwort ab wenn man sich per SSH einloggen möchte und sagt auch bei der eingabe des falschen Passworts "Permission denied, please try again." aber sobald man das richtige Passwort eintippt passiert nichts mehr :( 30 Minuten gewartet, das Mediacenter zeigt keine Auslastung mit top an.
root@raspberrypi:~# host kodi
kodi.fritz.box has address 192.168.178.46
root@raspberrypi:~# netcat -v 192.168.178.46 22
Connection to 192.168.178.46 22 port [tcp/ssh] succeeded!
SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u2
Protocol mismatch.
root@raspberrypi:~# ssh osmc@192.168.178.46
The authenticity of host '192.168.178.46 (192.168.178.46)' can't be established.
ECDSA key fingerprint is 07:ba:cc:c9:c7:e8:aa:39:3c:60:02:05:59:83:4e:e3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.178.46' (ECDSA) to the list of known hosts.
osmc@192.168.178.46's password:
Ihr konntet mir schon oft weiter helfen, vielleicht auch diesmal?
Danke und Grüße
pulsar
Logs auf dem Server anschauen und ssh -v probieren. Loglevel evtl. hochdrehen.
Wie lange hast Du denn gewartet? Ggf. ist's auch einfahc "noch nicht soweit" .- z.B. wegen irgendwelche Reverse-DNS-Abfragen, da kann sowas je nach Lust und Laune schon mal 30s bis 2m gehen...
florian0285
04.08.16, 06:06
Wenn du dich mit root anmelden willst darfst du das vielleicht nicht. Probiers mit nem anderen user.
macht er doch:
ssh osmc@192.168.178.46
florian0285
04.08.16, 06:47
Oh sorry... ich gewöhns mir mal ab so früh hier rein zu schauen... ich bin einfach noch nicht hochgefahren [emoji16]
apt-get install coffee
oder
wget http://java.com/coffee.tar.gz
tar -xzf coffee.tar.gz && cd coffee && ./configure --with-milk --with-caffeine --with-suggar && make && make install
Moin, auf dem OSMC habe ich mir einmal die logs per journalctl -x anzeigen lassen und den Zeitabschnitt des SSH-Logins rausgesucht. Hier wundert mich das immer wiederkehrende "Unit UNIT has begun starting up" und anschließend dann, "Unit UNIT has finished starting up" :confused: Mit ssh -vv habe ich gestern auch schon nachgesehen, das werde ich auch noch hier posten, nur bin ich grad nicht in meinem LAN.
Aug 03 18:40:40 kodi sshd[483]: Accepted password for osmc from 192.168.178.44 port 34246 ssh2
Aug 03 18:40:40 kodi sshd[483]: pam_unix(sshd:session): session opened for user osmc by (uid=0)
Aug 03 18:40:40 kodi systemd-logind[249]: New session c1 of user osmc.
-- Subject: A new session c1 has been created for user osmc
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c1 has been created for the user osmc.
--
-- The leading process of the session is 483.
Aug 03 18:40:40 kodi systemd[488]: pam_unix(systemd-user:session): session opened for user osmc by (uid=0)
Aug 03 18:40:40 kodi systemd[488]: Starting Paths.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Aug 03 18:40:40 kodi systemd[488]: Reached target Paths.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 03 18:40:40 kodi systemd[488]: Starting Timers.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Aug 03 18:40:40 kodi systemd[488]: Reached target Timers.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 03 18:40:40 kodi systemd[488]: Starting Sockets.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Aug 03 18:40:40 kodi systemd[488]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 03 18:40:40 kodi systemd[488]: Starting Basic System.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Aug 03 18:40:40 kodi systemd[488]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 03 18:40:40 kodi systemd[488]: Starting Default.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Aug 03 18:40:40 kodi systemd[488]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 03 18:40:40 kodi systemd[488]: Startup finished in 24ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 24781 microseconds.
Aug 03 18:43:12 kodi sshd[500]: Accepted password for osmc from 192.168.178.44 port 34250 ssh2
Aug 03 18:43:12 kodi sshd[500]: pam_unix(sshd:session): session opened for user osmc by (uid=0)
Aug 03 18:43:12 kodi systemd-logind[249]: New session c2 of user osmc.
-- Subject: A new session c2 has been created for user osmc
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c2 has been created for the user osmc.
--
-- The leading process of the session is 500.
Aug 03 18:46:50 kodi sshd[505]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=raspberrypi.fritz.box user=root
Aug 03 18:46:52 kodi sshd[505]: Failed password for root from 192.168.178.44 port 34432 ssh2
Aug 03 18:46:57 kodi sshd[505]: Failed password for root from 192.168.178.44 port 34432 ssh2
Aug 03 18:47:06 kodi sshd[505]: Failed password for root from 192.168.178.44 port 34432 ssh2
Aug 03 18:47:06 kodi sshd[505]: Connection closed by 192.168.178.44 [preauth]
Aug 03 18:47:06 kodi sshd[505]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=raspberrypi.fritz.box user=root
Einen Kaffee könnte ich mir jetzt auch gerade mal kompilieren ;)
florian0285
04.08.16, 17:17
Oh der Befehl is ja nett, aber Bier mit Kaffee verträgt sich nicht [emoji12]
Ich finde failed password for root is mal ne eindeutige Fehlermeldung.
Tippfehler? Tastaturlayout vertauscht?
Hallo, da bin ich wieder.
habe nun einmal die Infos dabei wenn man sich mit ssh -vv (verbose) einloggt. Es endet mit der Zeile "debug2: channel 0: request window-change confirm 0"
pi@raspberrypi:~ $ ssh -vv osmc@192.168.178.46
OpenSSH_6.7p1 Raspbian-5+deb8u3, OpenSSL 1.0.1t 3 May 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.178.46 [192.168.178.46] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/pi/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Raspbian-5+deb8u3
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Debian-5+deb8u2
debug1: match: OpenSSH_6.7p1 Debian-5+deb8u2 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
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-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: 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-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-ed25519,ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: 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,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: 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,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,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: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: kex_parse_kexinit: 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: kex_parse_kexinit: 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: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
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 umac-64-etm@openssh.com
debug1: kex: server->client aes128-ctr umac-64-etm@openssh.com none
debug2: mac_setup: setup umac-64-etm@openssh.com
debug1: kex: client->server aes128-ctr umac-64-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 07:ba:cc:c9:c7:e8:aa:39:3c:60:02:05:59:83:4e:e3
debug1: Host '192.168.178.46' is known and matches the ECDSA host key.
debug1: Found key in /home/pi/.ssh/known_hosts:10
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: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/pi/.ssh/id_rsa ((nil)),
debug2: key: /home/pi/.ssh/id_dsa ((nil)),
debug2: key: /home/pi/.ssh/id_ecdsa ((nil)),
debug2: key: /home/pi/.ssh/id_ed25519 ((nil)),
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/pi/.ssh/id_rsa
debug1: Trying private key: /home/pi/.ssh/id_dsa
debug1: Trying private key: /home/pi/.ssh/id_ecdsa
debug1: Trying private key: /home/pi/.ssh/id_ed25519
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
osmc@192.168.178.46's password:
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to 192.168.178.46 ([192.168.178.46]:22).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug1: Sending environment.
debug1: Sending env LANG = de_DE.UTF-8
debug2: channel 0: request env confirm 0
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
@florian0285 Das failed password for root war nur ein test, was er macht bei falschen Passwort. Aber ich wollte mich als Nutzer osmc einloggen und ich weiß auch nicht ob ein root Login bei osmc ohne weiteres möglich ist.
florian0285
04.08.16, 21:16
Nächste Regel... keine Antworten während einem Bierchen [emoji12]
Geht denn überhaupt ein Konsolen Login? Also lokal mit Tastatur?
Was für ne Shell steht denn für osmc in der passwd?
Kannst du es an nem andere Host ggf. mit anderem SSH Client ausprobieren?
... und in die Logs des Servers schauen.
Lokal kann ich mich ganz normal auf die Konsole einloggen. Auch per SSH als osmc User:confused:
Als Shell wird auf dem OSMC /bin/bash angezeigt.
Von einem anderen Gerät (meinem Jolla Smartphone) habe ich es auch probiert, genau das gleiche wie von meiner Arbeitsstation:
,---
| SailfishOS 2.0.1.11 (Taalojärvi) (armv7hl)
'---
[nemo@Jolla ~]$
[nemo@Jolla ~]$
[nemo@Jolla ~]$ ssh -vv osmc@kodi
OpenSSH_7.1p2, OpenSSL 1.0.2g-fips 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to kodi [192.168.178.46] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/nemo/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Debian-5+deb8u2
debug1: match: OpenSSH_6.7p1 Debian-5+deb8u2 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to kodi:22 as 'osmc'
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-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: 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,ssh-rsa
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: 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,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: 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,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,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: first_kex_follows 0
debug2: reserved 0
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com
debug2: kex_parse_kexinit: 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: kex_parse_kexinit: 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: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:hZd3AhqKU+cdAk/SVnQRW3Go0XIsnS02S+phK2E6tcY
debug1: Host 'kodi' is known and matches the ECDSA host key.
debug1: Found key in /home/nemo/.ssh/known_hosts:1
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: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/nemo/.ssh/id_rsa ((nil)),
debug2: key: /home/nemo/.ssh/id_dsa ((nil)),
debug2: key: /home/nemo/.ssh/id_ecdsa ((nil)),
debug2: key: /home/nemo/.ssh/id_ed25519 ((nil)),
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/nemo/.ssh/id_rsa
debug1: Trying private key: /home/nemo/.ssh/id_dsa
debug1: Trying private key: /home/nemo/.ssh/id_ecdsa
debug1: Trying private key: /home/nemo/.ssh/id_ed25519
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
osmc@kodi's password:
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to kodi ([192.168.178.46]:22).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
Die Logs (journal) auf dem OSMC Server hatte ich ja bereits gepostet aber mir stoßt da nichts ins Auge.
Im Moment update ich mein OSMC und da sehe ich auch updates für den openssh-Server, vielleicht flickt es sich ja von selbst :rolleyes:
florian0285
05.08.16, 21:56
/var/log ?
Firewall.. NAT.. dazwischen? Oder hast du ne direkte Verbindung?
Kannst du das auch mit Putty testen? Oder nem anderen ssh client? Also nicht ssh [emoji6]
Hallo florian0285,
auch nach dem Update auf die neueste OSMC Version kann ich mich immer noch nicht per ssh einloggen :(
Habe eine direkte Verbindung und keine Firewall auf allen meiner Systeme.
Boor Putty, wenn ich das höre muss ich noch an MS Windows denken :-D Aber das gibts ja auch in der Debian(Raspbian) Paketverwaltung. Habe es mir mal installiert, aber auch hier passiert nach der Eingabe des Passworts nichts mehr.
Werde noch mal sehen ob noch mehr geloggt wird auf dem OSMC.
Danke Euch schon mal bis hier hin :-)
BetterWorld
08.08.16, 01:29
Wegen
debug1: Authentication succeeded (password).
Authenticated to kodi ([192.168.178.46]:22).brauchst du im Netz oder Firewall gar nicht suchen. Das klappt alles längst.
Selbst SSH hat die Verbindung hergestellt.
Du wirst auf diesem Kodi selbst suchen müssen, warum es nicht weitergeht.
Gibt es dort den User "oscm"?
Klappt ein ssh mit anderem User?
Ist das Home und Login-Shell korrekt gesetzt? Shell aufrufbar?
Wie ist sshd gekonft?
(Man kann dort auch Verbindungen akzeptieren, aber dennoch interaktive Shell unterbinden)
All son Kram halt.
Mal als "pi" einloggen, wenn das geht, und dann mit su -l zu oscm werden.
Powered by vBulletin® Version 4.2.5 Copyright ©2024 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.