sshd: Username do usuário não permitido porque o shell zsh não existe

3

Estou tentando fazer login no meu PC com ssh, mas toda vez que o ssh diz Permission denied (publickey). e /var/log/auth.log contém entradas dizendo:

Jan 16 00:00:35 DerKonig sshd[11573]: Connection from 127.0.0.1 port 51482 on 127.0.0.1 port 22
Jan 16 00:00:35 DerKonig sshd[11573]: User <username> not allowed because shell zsh does not exist
Jan 16 00:00:35 DerKonig sshd[11573]: input_userauth_request: invalid user <username> [preauth]
Jan 16 00:00:35 DerKonig sshd[11573]: Connection closed by 127.0.0.1 port 51482 [preauth]

Eu sei de fato que:

  • O usuário existe.
  • O zsh está instalado.
  • /etc/shells contém /bin/zsh

/etc/ssh/sshd_config :

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

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

# Logging
SyslogFacility AUTH
LogLevel VERBOSE

# Authentication:
LoginGraceTime 120
PermitRootLogin no
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile /home/nabeel/.ssh/authorized_keys

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

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
PasswordAuthentication no

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

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# 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
    
por nom 15.01.2017 / 19:40

1 resposta

4

Com base na discussão nos comentários, descobriu-se que, embora /etc/shells contivesse /bin/zsh , o shell de login do usuário, conforme especificado em /etc/passwd , era apenas zsh

Corrigir o problema foi, então, apenas uma questão de alterar o shell de login do usuário para incluir o caminho completo:

sudo chsh -s /bin/zsh <username>
    
por steeldriver 15.01.2017 / 20:56

Tags