我用useradd在CentOS Web服务器中创build了一个新用户。 用passwd添encryption码。 但我无法通过SSHlogin用户。 我一直在“拒绝访问”。 我检查,确保密码已分配,并且该帐户处于活动状态。
/ var / log / secure显示以下错误:
8月13日03:41:40 server1 su:pam_unix(su:auth):authentication失败; logname = uid = 500 euid = 0 tty = pts / 0 ruser = rwade rhost = user = root
请帮忙,谢谢
感谢迄今为止的答复:我应该补充说,这是一个远程计算机上的VPS,开箱即用。 我可以以root用户身份login。 我也可以su给新用户,但是我不能以新用户身份login。
这是我的sshd_config文件:
# $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin # 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 #Protocol 2,1 Protocol 2 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: # 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 # Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 1h #ServerKeyBits 768 # Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH SyslogFacility AUTHPRIV #LogLevel INFO # Authentication: #LoginGraceTime 2m #PermitRootLogin yes #StrictModes yes #MaxAuthTries 6 #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 PasswordAuthentication yes # 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 GSSAPIAuthentication yes #GSSAPICleanupCredentials yes 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 mechanism. # Depending on your PAM configuration, this may bypass the setting of # PasswordAuthentication, PermitEmptyPasswords, and # "PermitRootLogin without-password". If you just want the PAM account and # session checks to run without PAM authentication, then enable this but set # ChallengeResponseAuthentication=no #UsePAM no UsePAM yes # Accept locale-related environment variables AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT AcceptEnv LC_IDENTIFICATION LC_ALL #AllowTcpForwarding yes #GatewayPorts no #X11Forwarding no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PrintMotd yes #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #UsePrivilegeSeparation yes #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #ShowPatchLevel no #UseDNS yes #PidFile /var/run/sshd.pid #MaxStartups 10 #PermitTunnel no #ChrootDirectory none # no default banner path #Banner /some/path # override default of no subsystems Subsystem sftp /usr/libexec/openssh/sftp-server
Ron,检查/etc/security/access.conf文件,查看是否允许用户或组访问。
例如:
不允许控制台login到除pipe理员以外的所有人
-:ALL EXCEPT root admins :LOCAL
除了那些需要它的人以外,不允许login
-:ALL EXCEPT root ssh_users :ALL
禁止从任何地方直接login
-: service_account :ALL
也许你的用户得到noshell,所以login成功,但不能把你放在一个shell。
检查你的/ etc / passwd文件,例如:
# grep sumodirjo /etc/passwd sumodirjo:x:501:501::/home/sumodirjo:/bin/bash
检查最后一部分,例如/ bin / bash,如果你的用户得到/ bin / false或者/ bin / nologin试图把它改成/ bin / bash。
我没有看到您的sshdconfigurationallowuser指令。 这个指令告诉ssh守护进程用户可以和不能直接SSH进入计算机。
如果你把allowuser <some username>然后重新启动/重新加载SSH守护进程,你将能够使用该用户名SSH进入计算机。