SSH funktioniert nicht mehr (auch per root)

[Tazzler]

Also ich kann mich seit ein paar Tagen nicht mehr per SSH auf die Diskstation verbinden. Und zwar sowohl per root, als auch 2 weiteren Accounts, die ich in der passwd freigeschaltet habe.

Eigentlich wollte ich die SSH-Keys von der alten Installation importieren, damit ein externer Server ohne Passwort-Abfrage auf die Syno verbinden kann, was jetzt leider nicht funktioniert, genauso wie per Passwort. Jetzt hab ich zur Not auf Telnet zurückgegriffen, das zum Glück funktioniert.

Beim verbose-Mode (ssh -v root@IP) krieg ich folgendes Feedback:

rmbp:~ MYUSER$ ssh -v root@IPSYNO
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/MYUSER/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to IPSYNO [IPSYNO] port 22.
debug1: Connection established.
debug1: identity file /Users/MYUSER/.ssh/id_rsa type -1
debug1: identity file /Users/MYUSER/.ssh/id_rsa-cert type -1
debug1: identity file /Users/MYUSER/.ssh/id_dsa type -1
debug1: identity file /Users/MYUSER/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1-hpn13v11
debug1: match: OpenSSH_5.8p1-hpn13v11 pat OpenSSH_5*
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: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA abcdefgh
debug1: Host 'IPSYNO' is known and matches the RSA host key.
debug1: Found key in /Users/MYUSER/.ssh/known_hosts:19
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,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/MYUSER/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/MYUSER/.ssh/id_rsa
debug1: Trying private key: /Users/MYUSER/.ssh/id_dsa
debug1: Next authentication method: password
root@IPSYNO's password: 
debug1: Authentication succeeded (password).
Authenticated to IPSYNO ([IPSYNO]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = de_CH.UTF-8
Permission denied, please try again.
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to IPSYNO closed.
Transferred: sent 3024, received 2416 bytes, in 0.0 seconds
Bytes per second: sent 286822.4, received 229154.4
debug1: Exit status 1
rmbp:~ MYUSER$

Erstmal meine sshd_config (/etc/ssh/sshd_config), die ich aus etc.defaults wiederhergestellt habe:

#       $OpenBSD: sshd_config,v 1.82 2010/09/06 17:10:19 naddy Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# The default requires explicit activation of protocol 1
#Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile     .ssh/authorized_keys

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing, 
# and session processing. If this is enabled, PAM authentication will 
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes
#UsePAM no

#AllowAgentForwarding yes
AllowTcpForwarding no
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
UseDNS no
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
ChrootDirectory none
#ChrootDirectory /var/services/homes/%u
#DenyUsers admin

# no default banner path
#Banner none

# override default of no subsystems
#Subsystem      sftp    /usr/libexec/sftp-server
#Subsystem       sftp    internal-sftp -f DAEMON -l VERBOSE -u 000
Subsystem       sftp    internal-sftp -f DAEMON -u 000
#Subsystem       sftp    /usr/syno/sbin/sftp-server -l DEBUG3

# the following are HPN related configuration options
# tcp receive buffer polling. disable in non autotuning kernels
#TcpRcvBufPoll yes
 
# allow the use of the none cipher
#NoneEnabled no

# disable hpn performance boosts. 
#HPNDisabled no

# buffer size for hpn to non-hpn connections
#HPNBufferSize 2048


# Example of overriding settings on a per-user basis
Match User root
#       X11Forwarding no
        AllowTcpForwarding yes
#       ForceCommand cvs server

Ausschnitt aus der /etc/passwd (sollte auch OK sein):

root:x:0:0:root:/root:/bin/ash

Dann mal noch ein paar Ordner/Datei-Rechte:
- Ausschnitt /etc/:

-rw-r--r--    1 root     root        2.5K Jan  3 22:48 passwd

- /:

drwxr-xr-x    5 root     root        4.0K Dec  9 09:59 root

- /root/:

drwxr-xr-x    5 root     root        4.0K Dec  9 09:59 .
drwxr-xr-x   26 root     root        4.0K Jan  3 22:56 ..
-rw-------    1 root     root          16 Dec  8 16:45 .esd_auth
drwx------    2 root     root        4.0K Dec  8 12:56 .gnupg
-rw-r--r--    1 root     root         364 Oct 27 07:39 .profile
drwx------    2 root     root        4.0K Jan  3 22:57 .pulse
-rw-------    1 root     root         256 Dec  8 16:45 .pulse-cookie
drwx------    2 root     root        4.0K Jan  3 21:15 .ssh

Gerne reiche ich noch weitere Infos nach. Habe die Syno natürlich schon diverse Male neugestartet. Hat jemand eine Idee, wie ich der Sache auf den Grund gehe? Hab jetzt seit 2 Tagen gegooglet, Rechte zigmal angepasst, hat alles nichts geholfen. Vermutlich ist das für jemanden mit bisschen Erfahrung einfach zu lösen?

Danke schon mal!

 

[Tommi2day]

Die Rechte für das Verzeichnis(und nur das) .ssh bitte auf 755 setzen. Dann noch die Rechte der Dateien in .ssh prüfen,die authorized_keys muss 600 haben.

 

[Tazzler]

Hab die Rechte des .ssh-Verzeichnis angepasst. Habe für den root kein authorized_keys.
Hat leider nicht geholfen.

Sonst noch einen Tipp?

 

[Tommi2day]

wie sieht die Definition in /etc/passwd aus?

 

[Tazzler]

Die ist bereits im Startpost:

Ausschnitt aus der /etc/passwd (sollte auch OK sein):

root:x:0:0:root:/root:/bin/ash

 

[Tommi2day]

Hm, ich hätte jetzt auf die Shell getippt, nachdem die Authentikation OK war. Mach doch mal ein ssh -vvv ..., evtl. sieht man dort mehr, welche Permission ihm fehlt

 

[Tazzler]

Gute Idee, werde aus dem Log aber nicht schlau. Du?

rmbp:~ MYUSER$ ssh -vvv root@SYNOIP
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/MYUSER/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to SYNOIP [SYNOIP] port 22.
debug1: Connection established.
debug1: identity file /Users/MYUSER/.ssh/id_rsa type -1
debug1: identity file /Users/MYUSER/.ssh/id_rsa-cert type -1
debug1: identity file /Users/MYUSER/.ssh/id_dsa type -1
debug1: identity file /Users/MYUSER/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1-hpn13v11
debug1: match: OpenSSH_5.8p1-hpn13v11 pat OpenSSH_5*
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "SYNOIP" from file "/Users/MYUSER/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /Users/MYUSER/.ssh/known_hosts:19
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,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,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,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: 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: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256
debug2: kex_parse_kexinit: 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: kex_parse_kexinit: 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: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
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: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 123/256
debug2: bits set: 978/2048
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA xxxxxxxx
debug3: load_hostkeys: loading entries for host "SYNOIP" from file "/Users/MYUSER/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /Users/MYUSER/.ssh/known_hosts:19
debug3: load_hostkeys: loaded 1 keys
debug1: Host 'SYNOIP' is known and matches the RSA host key.
debug1: Found key in /Users/MYUSER/.ssh/known_hosts:19
debug2: bits set: 1068/2048
debug1: ssh_rsa_verify: signature correct
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: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /Users/MYUSER/.ssh/id_rsa (0x0),
debug2: key: /Users/MYUSER/.ssh/id_dsa (0x0),
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: Trying private key: /Users/MYUSER/.ssh/id_rsa
debug3: no such identity: /Users/MYUSER/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /Users/MYUSER/.ssh/id_dsa
debug3: no such identity: /Users/MYUSER/.ssh/id_dsa: No such file or directory
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
root@SYNOIP's password: 
debug3: packet_send2: adding 48 (len 73 padlen 7 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to SYNOIP ([SYNOIP]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
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
debug3: packet_set_tos: set IP_TOS 0x10
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug1: Sending environment.
debug3: Ignored env TERM_PROGRAM
debug3: Ignored env SHELL
debug3: Ignored env TERM
debug3: Ignored env TMPDIR
debug3: Ignored env Apple_PubSub_Socket_Render
debug3: Ignored env TERM_PROGRAM_VERSION
debug3: Ignored env TERM_SESSION_ID
debug3: Ignored env USER
debug3: Ignored env SSH_AUTH_SOCK
debug3: Ignored env __CF_USER_TEXT_ENCODING
debug3: Ignored env PATH
debug3: Ignored env __CHECKFIX1436934
debug3: Ignored env PWD
debug1: Sending env LANG = de_CH.UTF-8
debug2: channel 0: request env confirm 0
debug3: Ignored env SHLVL
debug3: Ignored env HOME
debug3: Ignored env LOGNAME
debug3: Ignored env _
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 87380
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Permission denied, please try again.
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug2: channel 0: rcvd eow
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug2: channel 0: rcvd close
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)

Connection to SYNOIP closed.
Transferred: sent 2672, received 2368 bytes, in 0.0 seconds
Bytes per second: sent 124865.5, received 110659.3
debug1: Exit status 1

 

[Tommi2day]

Anmeldung war OK,

debug1: Authentication succeeded (password).
Authenticated to SYNOIP ([SYNOIP]:22).

aber beim Öffnen der Shell gibt es den Fehler

debug2: shell request accepted on channel 0
Permission denied, please try again.

So langsam gehen mir auch die Ideen aus.
Hast Du was am Profile gemacht? Evtl. IPKG etc. aktiviert. Oder ist der Link von /bin/ash nicht mehr valid?

 

[Tazzler]

Am .profile hab ich nichts gemacht.
Hier dennoch deren Inhalt:
vi /root/.profile

umask 022

PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin
export PATH

#This fixes the backspace when telnetting in.
#if [ "$TERM" != "linux" ]; then
#        stty erase
#fi

HOME=/root
export HOME

TERM=${TERM:-cons25}
export TERM

PAGER=more
export PAGER

PS1="`hostname`> "

alias dir="ls -al"
alias ll="ls -la"

IPKG hab ich nicht aktiviert.


ls -lah /bin/:

ls -lah /bin/
drwxr-xr-x    2 root     root        4.0K Dec  8 12:31 .
drwxr-xr-x   26 root     root        4.0K Jan  3 22:56 ..
lrwxrwxrwx    1 root     root           7 Dec  8 12:31 ash -> busybox
-rwxr-xr-x    1 root     root      495.2K Oct 27 09:09 busybox
lrwxrwxrwx    1 root     root           7 Dec  8 12:31 cat -> busybox
lrwxrwxrwx    1 root     root           7 Dec  8 12:31 catv -> busybox
lrwxrwxrwx    1 root     root           7 Dec  8 12:31 chgrp -> busybox
lrwxrwxrwx    1 root     root           7 Dec  8 12:31 chmod -> busybox
lrwxrwxrwx    1 root     root           7 Dec  8 12:31 chown -> busybox

Beim vorletzten Log war das environment vor dem Abbruch. Damit ist der Home-Ordner gemeint? Die Rechte dort müssten doch stimmen?

 

[Tommi2day]

OK.
Du kannst es ja noch einmal mit 0700 auf /root versuchen. Sonst muss ich leider passen und an den Support verweisen.

 

[Tazzler]

Klappt leider auch nicht. Danke trotzdem!

Sonst jemand eine Idee?
Mit dem Support hab ich leider die letzten 2 mal schlechte Erfahrungen gemacht, mir wurde einmal erst nach 3 Wochen geantwortet, beim anderen mal nach 2-3 Wochen, jedoch eine komplett unbrauchbare Antwort. Früher war das gefühlt deutlich besser.

 

[tmaex]

Setzte mal den .ssh/ auf 0700 und auch /root auf 0700

und schau (mit telnet) in die Logs /var/log/upstart/ssh-shell.log und /var/log/upstart/sshd.log

 

[Tazzler]

Wird nichts in die logs geschrieben...

tail -f sshd.log 
Sat Jan  3 22:55:20 CET 2015
Sat Jan  3 22:55:20 CET 2015
Sat Jan  3 22:55:20 CET 2015
Sat Jan  3 22:55:20 CET 2015
Sat Jan  3 22:55:20 CET 2015
Sat Jan  3 22:56:48 CET 2015
Sat Jan  3 23:31:39 CET 2015
Sat Jan  3 23:32:19 CET 2015
Sun Jan  4 11:53:27 CET 2015
Mon Jan  5 11:12:10 CET 2015

tail -f ssh-shell.log 
Thr Jan  1 21:04:08 CET 2015
Thr Jan  1 21:04:08 CET 2015
start: Job is already running: sshd
Thr Jan  1 21:04:08 CET 2015
Thr Jan  1 21:04:08 CET 2015
start: Job is already running: sshd
Thr Jan  1 21:04:08 CET 2015
Thr Jan  1 21:04:08 CET 2015
start: Job is already running: sshd
Thr Jan  1 21:04:09 CET 2015

Hab auch kurz später mal mit vi reingeschaut. Nichts neues...
Ist das gut oder schlecht?