在我的 Raspberry Pi 上从 Gitlab.com 克隆 Repo 时权限被拒绝（公钥）

Posted 2023-03-23

【中文标题】在我的 Raspberry Pi 上从 Gitlab.com 克隆 Repo 时权限被拒绝（公钥）

【英文标题】：Permission denied (publickey) when cloning Repo from Gitlab.com on my Rasperry Pi

【发布时间】：2021-08-25 21:37:04

【问题描述】：

我正在尝试通过 ssh 从 Gitlab.com 克隆一个 repo。但我一直收到这个错误：

pi@prometheus:~/work/repos$ git clone [e-mail]:sommerfeld.sebastian/prometheus-grafana.git
Cloning into 'prometheus-grafana'...
[e-mail]: Permission denied (publickey,keyboard-interactive).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

我以这种方式创建了一个 SSH 密钥：

keyName="$1"
keyFile="/home/$USER/.ssh/$keyName.key"

echo -e "$LOG_INFO Create new ssh key: $keyName"
cd ~/.ssh || exit
ssh-keygen -f "$keyFile" -t ed25519 -C "[e-mail]"

echo -e "$LOG_INFO Start the ssh-agent in background"
eval "$(ssh-agent -s)"

echo -e "$LOG_INFO Add ssh key to the ssh-agent"
ssh-add "$keyFile"

echo -e "$LOG_DONE Key created"

我将公钥添加到 Gitlab.com（用户设置 > SSH 密钥 > KEYNAME）。我仍然一直收到此错误。

该错误发生在我运行 Ubuntu Server 21.04 64 位的 Raspberry Pi 上。相同的脚本可以在我运行 Ubuntu Desktop 20.04 64 位的常规工作站上运行。

运行 ssh -v [e-mail] 的 RasPi 的调试输出：

pi@prometheus:~/work/repos$ ssh -v [e-mail]
OpenSSH_8.4p1 Ubuntu-5ubuntu1, OpenSSL 1.1.1j  16 Feb 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to gitlab.com [2606:4700:90:0:f22e:fbec:5bed:a9b9] port 22.
debug1: Connection established.
debug1: identity file /home/pi/.ssh/id_rsa type -1
debug1: identity file /home/pi/.ssh/id_rsa-cert type -1
debug1: identity file /home/pi/.ssh/id_dsa type -1
debug1: identity file /home/pi/.ssh/id_dsa-cert type -1
debug1: identity file /home/pi/.ssh/id_ecdsa type -1
debug1: identity file /home/pi/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/pi/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/pi/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/pi/.ssh/id_ed25519 type -1
debug1: identity file /home/pi/.ssh/id_ed25519-cert type -1
debug1: identity file /home/pi/.ssh/id_ed25519_sk type -1
debug1: identity file /home/pi/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/pi/.ssh/id_xmss type -1
debug1: identity file /home/pi/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.4p1 Ubuntu-5ubuntu1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9p1 Debian-10+deb10u2
debug1: match: OpenSSH_7.9p1 Debian-10+deb10u2 pat OpenSSH* compat 0x04000000
debug1: Authenticating to gitlab.com:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: [e-mail] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [e-mail] MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:HbW3g8zUjNSksFbqTiUWPWg2Bq1x8xdGUrliXFzSnUw
debug1: Host 'gitlab.com' is known and matches the ECDSA host key.
debug1: Found key in /home/pi/.ssh/known_hosts:1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/pi/.ssh/id_rsa 
debug1: Will attempt key: /home/pi/.ssh/id_dsa 
debug1: Will attempt key: /home/pi/.ssh/id_ecdsa 
debug1: Will attempt key: /home/pi/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/pi/.ssh/id_ed25519 
debug1: Will attempt key: /home/pi/.ssh/id_ed25519_sk 
debug1: Will attempt key: /home/pi/.ssh/id_xmss 
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/pi/.ssh/id_rsa
debug1: Trying private key: /home/pi/.ssh/id_dsa
debug1: Trying private key: /home/pi/.ssh/id_ecdsa
debug1: Trying private key: /home/pi/.ssh/id_ecdsa_sk
debug1: Trying private key: /home/pi/.ssh/id_ed25519
debug1: Trying private key: /home/pi/.ssh/id_ed25519_sk
debug1: Trying private key: /home/pi/.ssh/id_xmss
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: No more authentication methods to try.
[e-mail]: Permission denied (publickey,keyboard-interactive).

我不明白为什么我的 RasPi 的行为与我的 Ubuntu 工作站不同。我的工作站上的相同命令返回不同的结果，在结束前打印Welcome to GitLab, @sommerfeld.sebastian! 几行。

我的 RasPi 上的 SSH 版本：

pi@prometheus:~/work/repos$ ssh -V
OpenSSH_8.4p1 Ubuntu-5ubuntu1, OpenSSL 1.1.1j  16 Feb 2021

【参考方案1】：

这取决于您在脚本中为 $keyFile 使用的内容。

默认名称应该是 SSH 会话期间考虑的 /home/pi/.ssh/id_xxx 名称的一部分。 但是需要在~/.ssh/config 中指定非默认名称：请仔细检查是否有。

另外，在您的脚本中，请确保不要始终使用~/.ssh,，而是始终使用/home/$USER/.ssh，以避免在shell 替换~ 时出现任何错误。

【讨论】：

非常感谢。这有帮助......我仍然有点困惑，因为在我的 Ubuntu 笔记本电脑上，我使用了一个键名和“gitlab.key”和“gitlab.key.pub”，而没有额外的 ~/.ssh/config 文件。但是使用这个文件为我的 raspi 解决了问题。不知道为什么两者的行为不同，但又一次：它有效

@SebastianSommerfeld 好的。您可以在您的 Ubuntu 笔记本电脑上执行ssh -Tv [e-mail]，查看那里实际使用了什么，以及为什么$HOME/.ssh/gitlab.key 在那里工作。

谢谢...我猜Found key in /home/sebastian/.ssh/known_hosts:13 这行暗示了为什么它可以在我的笔记本电脑中使用。

@SebastianSommerfeld 这只是意味着它知道目标服务器，而不是它可以访问它，如serverfault.com/q/571158/783 所示。