Git 总是提示“你确定要继续连接吗（是/否/[指纹]）？”

Question

我在

~/.config/ssh

中设置了 ssh，而不是默认的

~/.ssh

。

每次我执行

git pull

或

git push

时，我都会收到以下消息：

The authenticity of host 'github.com (192.30.255.112)' can't be established.
RSA key fingerprint is SHA256:....
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Failed to add the host to the list of known hosts (/Users/username/.ssh/known_hosts).

输入 yes 后，下一步将主机添加到

known_hosts

失败，但操作（

git pull

和

git push

）成功完成。

操作完成后没有

~/.ssh

（因此也没有

~/.ssh/known_hosts

）。

我已知的主机文件的位置是：

~/.config/ssh/known_hosts

。

我已经完成了：

ssh -o UserKnownHostsFile=~/.config/ssh/known_hosts -T [email protected]

和

eval $(ssh-agent)
ssh-add -K ~/.config/ssh/id_rsa

还使用

pbcopy < ~/.config/ssh/id_rsa.pub

将 SSH 密钥添加到我的 github 配置文件中。

~/.config/ssh/config

的内容：

Host *
  AddKeysToAgent yes
  UseKeychain yes
  IdentityFile ~/.config/ssh/id_rsa

~/.config/ssh/known_hosts

的内容：

github.com,192.30.255.112 ssh-rsa ...
...
...==
192.30.255.113 ssh-rsa ...
...
...==

~/.config/ssh

的文件权限:

drwxr-xr-x  6 username  staff   192 Aug 29 19:12 .
drwxr-xr-x  7 username  staff   224 Aug 29 16:17 ..
-rw-r--r--  1 username  staff    83 Aug 29 19:01 config
-rw-------  1 username  staff  3434 Aug 29 19:00 id_rsa
-rw-r--r--  1 username  staff   747 Aug 29 19:00 id_rsa.pub
-rw-r--r--  1 username  staff   803 Aug 29 19:31 known_hosts

编辑：

做

ssh -o UserKnownHostsFile=$HOME/.config/ssh/known_hosts [email protected]

给出：

[email protected]: Permission denied (publickey)

如何避免每次

git pull

和

git push

都输入“是”？

Answer 1

每次我收到警告时-
您确定要继续连接吗（是/否）？
修复：

1. 打开文件-
   

   nano ~/.ssh/config

2. 应出现以下行 -

如-

Host github.com
     StrictHostKeyChecking no

这对我有用。

Answer 2

按照 this GitHub 页面上的说明，我执行了命令

ssh -vT [email protected]

。

它给出了以下输出：

OpenSSH_8.1p1, LibreSSL 2.7.3
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 47: Applying options for *
debug1: Connecting to github.com port 22.
debug1: Connection established.
debug1: identity file /Users/saurabh/.ssh/id_rsa type -1
debug1: identity file /Users/saurabh/.ssh/id_rsa-cert type -1
debug1: identity file /Users/saurabh/.ssh/id_dsa type -1
debug1: identity file /Users/saurabh/.ssh/id_dsa-cert type -1
debug1: identity file /Users/saurabh/.ssh/id_ecdsa type -1
debug1: identity file /Users/saurabh/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/saurabh/.ssh/id_ed25519 type -1
debug1: identity file /Users/saurabh/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/saurabh/.ssh/id_xmss type -1
debug1: identity file /Users/saurabh/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.1
debug1: Remote protocol version 2.0, remote software version babeld-c2ee9279
debug1: no match: babeld-c2ee9279
debug1: Authenticating to github.com:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: rsa-sha2-512
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: ssh-rsa SHA256:...
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /Users/saurabh/.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: [email protected] RSA SHA256:...
debug1: Will attempt key: /Users/saurabh/.ssh/id_rsa 
debug1: Will attempt key: /Users/saurabh/.ssh/id_dsa 
debug1: Will attempt key: /Users/saurabh/.ssh/id_ecdsa 
debug1: Will attempt key: /Users/saurabh/.ssh/id_ed25519 
debug1: Will attempt key: /Users/saurabh/.ssh/id_xmss 
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa,rsa-sha2-512,rsa-sha2-256,ssh-dss>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: [email protected] RSA SHA256:...
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/saurabh/.ssh/id_rsa
debug1: Trying private key: /Users/saurabh/.ssh/id_dsa
debug1: Trying private key: /Users/saurabh/.ssh/id_ecdsa
debug1: Trying private key: /Users/saurabh/.ssh/id_ed25519
debug1: Trying private key: /Users/saurabh/.ssh/id_xmss
debug1: No more authentication methods to try.
[email protected]: Permission denied (publickey).

“身份文件”行末尾的“-1”表示 SSH 找不到要使用的文件。

我修改了这个答案，以便全局配置私钥：

git config --global core.sshCommand "ssh -i $HOME/.config/ssh/id_rsa -o UserKnownHostsFile=$HOME/.config/ssh/known_hosts -F /dev/null"

Answer 3

更安全的方法是添加

Host *
        StrictHostKeyChecking accept-new

至

~/.ssh/config

文件。
open-ssh 客户端中的新选项

accept-new

将接受新密钥，但如果对现有密钥进行更改，则会拒绝。