将 ssh 密钥复制到另一台机器上,以便我可以在那里使用 GitHub?

Ric*_*ard 13 ssh git

我有一个远程服务器。我已经可以成功地通过 ssh 连接到该远程服务器 - 我的密钥在authorized_keys远程服务器上。

现在我想从 GitHub 直接拉到那个远程服务器上。但是permission denied (publickey)当我尝试ssh -T git@github.com远程服务器时,我得到了。

我应该id_rsa.pub直接从我的本地机器复制到远程服务器上,还是那样危险?

如果这是答案,那么最好的方法是什么?

或者我应该在远程服务器上生成一个新的公钥,并将其添加到我的 github acocount 中?

更新:

这是详细 ssh 的输出:

~$ ssh -Tv git@github.com
OpenSSH_6.0p1 Debian-4+deb7u2, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to github.com [192.30.252.131] port 22.
debug1: Connection established.
debug1: identity file /home/richard/.ssh/id_rsa type -1
debug1: identity file /home/richard/.ssh/id_rsa-cert type -1
debug1: identity file /home/richard/.ssh/id_dsa type -1
debug1: identity file /home/richard/.ssh/id_dsa-cert type -1
debug1: identity file /home/richard/.ssh/id_ecdsa type -1
debug1: identity file /home/richard/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version libssh-0.6.0
debug1: no match: libssh-0.6.0
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 none
debug1: kex: client->server aes128-ctr hmac-sha1 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: RSA 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/richard/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/richard/.ssh/id_rsa
debug1: Trying private key: /home/richard/.ssh/id_dsa
debug1: Trying private key: /home/richard/.ssh/id_ecdsa
debug1: No more authentication
Run Code Online (Sandbox Code Playgroud)

Jar*_*und 6

id_rsa.pub可以在任何地方没有任何真正的危险,它被复制。这是您的公钥,用于此类用途。它是密钥对的一半,与您想要访问的地方共享它是您允许私钥发挥作用的方式。

为了允许远程登录,您的公钥需要列在authorized_keys(authorized_keys2在某些系统上)。每行一个键,格式如下:

ssh-rsa AAAIHAVEREMOVEDTHEMAJORITYOFTHEKEYBECAUSEISEENONEEDTOPOSTTHATWALLOFTEXTHERE9yfRjxw== jarmund@jarmint
Run Code Online (Sandbox Code Playgroud)

为了实现这一点,一旦你复制了它,只需将它附加到authorized_keys文件中,如下所示:cat id_rsa.pub >> ~/.ssh/authorized_keys

如果.ssh文件夹的权限太松,大多数健全的系统都会怯懦地拒绝允许您使用基于密钥的登录。该文件夹应该是700,所以如果您仍然遇到问题:chmod 700 ~/.ssh

另外,文件.ssh夹中的文件应该是600:chmod 600 ~/.ssh


编辑1:

id_rsa.pub远程服务器上不需要文件本身。只有内容,作为authorized_keys. 我建议运行ssh -vT git@github.com以启用详细日志记录,以便您可以准确查看它抱怨的权限。

编辑2:

这意味着所提供的密钥都不匹配远程服务器上的文件。你想看到的是这样的:

debug1: Offering RSA public key: /home/jarmund/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 535
Run Code Online (Sandbox Code Playgroud)

检查事项:

  • 确保其中一个私钥与您添加到远程的公钥匹配 authorized_keys
  • 确保密钥与您尝试登录的用户名匹配(应该是公钥的最后一部分)
  • 尝试重命名authorized_keysauthorized_keys2