Otentikasi Kunci Publik gagal

Saya menggunakan ubuntu 13.10, dan server menjalankan ubuntu 12.04. Saya telah menghasilkan kunci privat dan publik menggunakan ssh-keygen, dan meletakkan id_rsa.pub ke sisi server dan menambahkannya authorzied_keyssesuai dengan metode yang saya temukan di Internet. Tapi, saya masih harus memasukkan kata sandi saat saya mencoba masuk. Saya telah menetapkan dir home ke 700, .ssh dir ke 700, file authorzied_keys menjadi 600, dan saya telah memeriksa file sshd_config, dan tidak ada yang terjadi.

Informasi debug (dengan opsi -vvv) dan sshd_config adalah sebagai berikut, dan tidak ada yang tercantum dalam file auth.log server.

Saya bahkan telah memperbarui openssh-server openssh-client pada sisi klien dan server.

Apakah ada hal lain yang harus saya lakukan? Terima kasih atas infomasinya.

debug3: load_hostkeys: loading entries for host "[xxx.101.15.62]:2222" from file "/home/leetom/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/leetom/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys
debug3: load_hostkeys: loading entries for host "[xxx.101.15.62]:2222" from file "/home/leetom/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/leetom/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys
debug1: Host '[xxx.101.15.62]:2222' is known and matches the ECDSA host key.
debug1: Found key in /home/leetom/.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/leetom/.ssh/id_rsa ((nil)),
debug2: key: /home/leetom/.ssh/id_dsa ((nil)),
debug2: key: /home/leetom/.ssh/id_ecdsa ((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/leetom/.ssh/id_rsa
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey: RSA 68:51:b6:ed:cc:c2:54:f4:xx:15:41:d7:f5:4a:0e:da
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/leetom/.ssh/id_dsa
debug3: no such identity: /home/leetom/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/leetom/.ssh/id_ecdsa
debug3: no such identity: /home/leetom/.ssh/id_ecdsa: 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: 

dan 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_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

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

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes

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

# 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

Bit ini sepertinya kami menggunakan kunci pribadi Anda untuk mencoba login kriptografis, maka kami harus mencoba yang lain karena tidak diterima:

debug1: Trying private key: /home/leetom/.ssh/id_rsa
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey: RSA 68:51:b6:ed:cc:c2:54:f4:xx:15:41:d7:f5:4a:0e:da
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password

Masalah paling sederhana bisa terjadi pada penyalinan Anda atas kunci publik, karena saya mendapatkan respons yang sama dengan mencoba mengautentikasi dengan kunci yang saya tahu ujung lainnya tidak ada di sini.

Daripada menyalin id secara manual, mengapa tidak mencoba ssh-copy-id- masukkan kata sandi Anda dan itu akan diperbarui authorized_keys. Itu harus (a) pasti memilih kunci yang sama denganssh harus memilih, (b) memastikan Anda belum sengaja menambahkan kesalahan format.

Jika itu berhasil, bandingkan baris yang ditambahkan authorized_keysoleh ssh-copy-iddan semoga Anda akan mengerti apa yang salah.

Perizinan bisa menjadi semacam lain dari masalah yang menyebabkan kegagalan otentikasi publickey: cek yang Anda ~dan ~/.sshdirektori tidak terbaca oleh siapa pun kecuali untuk pengguna Anda ( chmod 700 ~ && chmod 700 ~/.sshbisa memperbaikinya).

Sunting: izin 750 untuk ~harus oke juga.

Secara kebetulan, saat membuat authorized_keysfile, apakah Anda salah mengeja nama file Anda (karena Anda mengejanya sebagaiauthorzied_keys dalam pertanyaan (saya dan z dipertukarkan), ada kemungkinan Anda telah menamai file dengan cara yang sama) Di file konfigurasi ssh, file nama file secara khusus disebut

AuthorizedKeysFile %h/.ssh/authorized_keys

Oleh karena itu, Anda harus yakin bahwa nama filenya sama. Jadi verifikasi saja nama filenya.

Terkadang Anda perlu memberikan kunci pribadi secara eksplisit dengan -i

Contoh: ssh -i /root/.ssh/id_rsa2 user@remote