web-dev-qa-db-ja.com

サーバーにsftpできませんアクセス許可が拒否されました。再試行してください

サーバーにSFTPで接続しようとすると、

debug1: Authentications that can continue: publickey,password
Permission denied, please try again.

正しいパスワードを使用していますが。

接続しようとしているサーバーimのSSHD_CONFIG。

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

# What ports, IPs and protocols we listen for
Port 25595
# 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_dsa_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 INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin without-password
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication no
#AuthorizedKeysFile     %h/.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 yes

# 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 yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#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 -l INFO

# 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

完全なsftp-v -v -v -p HostImConnectingto25595出力

debug3: load_hostkeys: loading entries for Host "HostImConnectingto" from file "/home/grayson/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/grayson/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys
debug3: load_hostkeys: loading entries for Host "24.231.182.21" from file "/home/grayson/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/grayson/.ssh/known_hosts:3
debug3: load_hostkeys: loaded 1 keys
debug1: Host 'HostImConnectingto' is known and matches the ECDSA Host key.
debug1: Found key in /home/grayson/.ssh/known_hosts:2
debug1: ssh_ecdsa_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: /home/grayson/.ssh/id_rsa ((nil)),
debug2: key: /home/grayson/.ssh/id_dsa ((nil)),
debug2: key: /home/grayson/.ssh/id_ecdsa ((nil)),
debug2: key: /home/grayson/.ssh/id_ed25519 ((nil)),
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred gssapi-keyex,gssapi-with-mic,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: /home/grayson/.ssh/id_rsa
debug3: no such identity: /home/grayson/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /home/grayson/.ssh/id_dsa
debug3: no such identity: /home/grayson/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/grayson/.ssh/id_ecdsa
debug3: no such identity: /home/grayson/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/grayson/.ssh/id_ed25519
debug3: no such identity: /home/grayson/.ssh/id_ed25519: 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
[email protected]'s password:
debug3: packet_send2: adding 48 (len 64 padlen 16 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
[email protected] password:

ボックスにPuTTYを正常に挿入できますが、別のボックスからssh -p 25595 user @ WhereImTryingToConnectを試してみると、機能しません。両方のボックスはubuntu14.04です

編集1:PasswordAuthenticationをnoからyesに変更し、sshサービスを再起動しました。しかし、sftp -v -v -v [email protected]を試してみるとまだエラーが発生します

debug1: Authentications that can continue: publickey,password
Permission denied, please try again.

2人の異なるユーザーを試しましたが、両方のパスワードが正しく入力されていることを確認できます

編集2:ボックスb(接続しようとしているコンピューター)とボックスa(接続しているコンピューター)からsshを取得しました。最初に、ボックスbにキーを生成しました。次に、キーをボックスaにコピーしようとしましたが、エラーが発生しました。

bash: line 2: .ssh/authorized_keys: Permission denied

だから私の最初の考えは、ボックスaのパーミッションがめちゃくちゃ大丈夫だということでした。 (私はそれらをそれぞれ700と600に設定しましたが)次に行って〜/ .sshを777に設定しました(これIS悪いことはしないでください))そして私も〜/ .ssh /をに設定しました777(ALSO BAD)。これにより、sshキーをボックスbからボックスaにコピーできました。BからボックスAにリモートでアクセスすることもできますが、bからボックスaにSFTPで転送することはできません。 。

2
hurnhu

Askubuntuと同じ答え:

PasswordAuthentication yesPasswordAuthentication noの代わりにsshd_configを設定する必要があります。

2
Jakuje