Ich habe meinen öffentlichen Schlüssel ~/.ssh/authorized_keysauf den Server kopiert . Jetzt versuche ich eine SSH-Verbindung herzustellen, aber es funktioniert nicht.
Dies ist die Ausgabe von ssh -v(Serverdomäne und IP-Adresse geändert).
OpenSSH_7.2p2 Ubuntu-4ubuntu2.5, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to <Server> [ip] port 22. debug1: Connection established. debug1: identity file /var/lib/jenkins/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /var/lib/jenkins/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /var/lib/jenkins/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /var/lib/jenkins/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /var/lib/jenkins/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /var/lib/jenkins/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /var/lib/jenkins/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.5 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.6 debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.6 pat OpenSSH* compat 0x04000000 debug1: Authenticating to <server>:<port> as 'jenkins' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:oDdpyTTKXVwLAF7RvyrBmTdtiYusX9Kh5unb/IVhQT0 debug1: Host <server> is known and matches the ECDSA host key. debug1: Found key in /var/lib/jenkins/.ssh/known_hosts:5 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_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /var/lib/jenkins/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Trying private key: /var/lib/jenkins/.ssh/id_dsa debug1: Trying private key: /var/lib/jenkins/.ssh/id_ecdsa debug1: Trying private key: /var/lib/jenkins/.ssh/id_ed25519 debug1: No more authentication methods to try. Es wurde bereits sichergestellt, dass Sie dem Inhalt von .ssh auf dem Server die richtigen Berechtigungen zuweisen, und ich habe einen anderen Euxer, der sich mit dem öffentlichen Schlüssel am Server anmelden kann.
Irgendeine Idee, was das Problem sein könnte?
ssh-copy-idDas Rätselraten bei der Migration von Schlüsseln auf Ihre Maschinen entfällt. Um Ihren Standardschlüssel zu kopieren, führen Sie einfach Folgendes aus:
ssh-copy-id user@newserver.com
Wenn Sie über mehrere SSH-Schlüssel verfügen, die Sie verwenden, können Sie das -iKennzeichen verwenden, um anzugeben, welchen Schlüssel Sie an den neuen Computer senden möchten. So wie:
ssh-copy-id -i /path/to/new_id_rsa user@newserver.com