web-dev-qa-db-fra.com

Comment réparer une autorisation refusée lorsque j'essaie de me connecter via SSH à mon serveur Ubuntu?

Lorsque j'essaie de me connecter à mon serveur Ubuntu hébergé sur AWS, j'obtiens "Autorisation refusée".

ssh -v ... me donne ceci:

OpenSSH_7.2p2, LibreSSL 2.4.1
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: Connecting to 52.22.60.11 [52.22.60.11] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/RubenBerkhout/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.4
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.4 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 52.22.60.11:22 as 'admin'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: [email protected]
debug1: kex: Host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server Host key: ecdsa-sha2-nistp256 SHA256:BkkfDekRz+v2Q7D8KR+WUtSR8asoqnAyvQPJyLubaUI
debug1: Host '52.22.60.11' is known and matches the ECDSA Host key.
debug1: Found key in /Users/RubenBerkhout/.ssh/known_hosts:8
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/RubenBerkhout/.ssh/id_rsa
debug1: Trying private key: /Users/RubenBerkhout/.ssh/id_dsa
debug1: Trying private key: /Users/RubenBerkhout/.ssh/id_ecdsa
debug1: Trying private key: /Users/RubenBerkhout/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).
networkingserverpermissionssshauthentication
1
Ruben Berkhout

AWS force l'authentification par clé privée. Ils n'autorisent pas uniquement l'authentification utilisateur/passe.

Vous avez à faire:

ssh -i private-key.pem user@server-ip

Substitution dans vos informations, évidemment.

Si vous ne disposez pas déjà d'un .pem, vous pouvez le télécharger à partir du panneau de configuration AWS.

1
Android Dev