SSH sem chave para o Ubuntu

1

Estou tentando SSH com o PuTTY no Windows para uma caixa do Ubuntu.

Eu criei a chave pública e a chave privada com PuttyKeygen e adicionei a chave pública ao arquivo /home/[user]/.ssh/authorized_keys do servidor como uma única linha, adicionando [user@server] ao final e adicionando ssh-rsa no começo, então parece como:

ssh-rsa [key] [user]@[server]

Isto está em uma única linha; authorized_keys chmod é 600, a pasta ~ / .ssh é 700 no servidor. Tudo é o mesmo, de acordo com este tutorial .

Ainda quando tento usar o arquivo de chave privada do PuTTY, recebo a resposta abaixo:

"Server refused our key"

Aqui está o log da sessão:

2011-10-08 23:43:58 Looking up host "server"
2011-10-08 23:43:58 Connecting to server port 22
2011-10-08 23:43:58 Server version: SSH-2.0-OpenSSH_5.8p1 Debian-1ubuntu3
2011-10-08 23:43:58 We claim version: SSH-2.0-PuTTY_Release_0.60
2011-10-08 23:43:58 Using SSH protocol version 2
2011-10-08 23:43:58 Doing Diffie-Hellman group exchange
2011-10-08 23:43:58 Doing Diffie-Hellman key exchange with hash SHA-256
2011-10-08 23:43:59 Host key fingerprint is:
2011-10-08 23:43:59 ssh-rsa 2048 be:32:9b:69:e9:fb:5d:08:71:3e:08:09:4d:b2:c8:b4
2011-10-08 23:43:59 Initialised AES-256 SDCTR client->server encryption
2011-10-08 23:43:59 Initialised HMAC-SHA1 client->server MAC algorithm
2011-10-08 23:43:59 Initialised AES-256 SDCTR server->client encryption
2011-10-08 23:43:59 Initialised HMAC-SHA1 server->client MAC algorithm
2011-10-08 23:43:59 Reading private key file "C:\Users\User\.ssh\id_rsa.ppk"
2011-10-08 23:43:59 Offered public key
2011-10-08 23:43:59 Server refused public key

Aqui está o que eu vejo no arquivo auth.log

Oct  9 01:53:12 [server] sshd[1818]: Connection closed by [client-ip]
Oct  9 01:53:12 [server] sshd[1818]: Transferred: sent 3104, received 2008 bytes
Oct  9 01:53:12 [server] sshd[1818]: Closing connection to [client-ip] port 51499
Oct  9 01:53:12 [server] sshd[1800]: pam_unix(sshd:session): session closed for user [user]
Oct  9 01:53:15 [server] sshd[1786]: Connection closed by [client-ip]
Oct  9 01:53:15 [server] sshd[1786]: Transferred: sent 1944288, received 9040 bytes
Oct  9 01:53:15 [server] sshd[1786]: Closing connection to [client-ip] port 51498
Oct  9 01:53:15 [server] sshd[1764]: pam_unix(sshd:session): session closed for user [user]
Oct  9 01:53:20 [server] sshd[1933]: Set /proc/self/oom_score_adj to 0
Oct  9 01:53:20 [server] sshd[1933]: Connection from [client-ip] port 51501
Oct  9 01:53:20 [server] sshd[1933]: Failed publickey for [user] from [client-ip] port 51501 ssh2

Aqui está o arquivo sshd_config

# 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
#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 DEBUG#INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin no
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile /home/%u/.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 yes#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 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 aug70co 09.10.2011 / 06:47

2 respostas

1

Ao criar o arquivo ~/.ssh/authorized_keys , você não deverá modificar a linha que você colar. Esta linha deve ser exatamente igual ao conteúdo do arquivo de chave pública no cliente ssh. Seu comentário sobre acrescentar [user @ server] e prepending ssh-rsa indica para mim que você pode não ter colado a linha correta lá em primeiro lugar. Modificar a linha para adicionar esses bits não ajudará.

    
por 09.10.2011 / 10:08
0

Uma pergunta meio boba (seria um comentário se eu tivesse os direitos) ...

Você tem certeza de que está tentando fazer login como o usuário correto. Tente conectar-se como usuário @ host em massa como na captura de tela de exemplo abaixo.

Caso contrário, todas as configurações parecem razoáveis para mim ...

    
por 11.10.2011 / 12:00