该消息来自SSH，它警告您正在连接到一个您以前从未连接过的主机。我不建议关闭它，因为这意味着您可能会错过关于主机密钥更改的警告，这可能表明SSH会话受到MITM攻击。

我的情况下，我只得到ssh警告时使用Gridengine qrsh远程shell登录。然而，正常的ssh会像预期的那样工作(第一次发出警告，然后在随后的时间里保持安静)。

我的解决方案是手动填充~/。ssh/known_hosts与Gridengine可以选择的所有可能的服务器名称(使用qhost列出服务器):

for p in server1 server2 server3 server4; do
  ssh-keyscan -H ${p}.company.com;
  ssh-keyscan -H $(getent hosts $p | perl -lane 'print $F[0]');
done >> ~/.ssh/known_hosts

背景:

Gridengine is a job scheduler which can use ssh to select the least loaded server. The reason for the warning is that qrsh seem to always specify a non-standard port for doing the ssh connection, causing known_hosts to be updated with an entry also containing a port number. Next time when qrsh selects the same server there would be a new port-number and known_hosts would get updated with a new port-specific entry. The reason for also adding the raw host IP address is that some hosts used ecdsa-sha2-nistp521. If a raw IP entry is not added I would get the warning:

ECDSA host key for IP address '10.1.2.3' not in list of known hosts.

将您的私钥添加到ssh-agent:

ssh-add ~/.ssh/id_rsa

创建一个~/。Ssh /config文件并插入行:

UserKnownHostsFile ~/.ssh/known_hosts

然后，您将在下次访问Github时看到该消息，但在此之后，您将不再看到它，因为主机已添加到known_hosts文件。这可以修复问题，而不仅仅是隐藏日志消息。

这个问题困扰了我很长时间。出现此问题是因为为Windows编译的OpenSSH客户端没有检查~/.ssh/known_hosts中的known_hosts文件

SSH -vvv git@github.com

debug3: check_host_in_hostfile: filename /dev/null
debug3: check_host_in_hostfile: filename /etc/ssh/ssh_known_hosts
debug3: check_host_in_hostfile: filename /dev/null
debug3: check_host_in_hostfile: filename /etc/ssh/ssh_known_hosts
Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.

要屏蔽ssh的警告消息，可以在~/.ssh/config中添加以下行:

Host *
LogLevel error

这将禁用警告，但不会禁用错误消息。就像~/中的其他设置一样。如果你想要一个更细粒度的控制，你可以在每个主机上配置LogLevel。

我有同样的问题，我发现没有一个.ssh文件在我的~。所以我只是在~路径下创建了.ssh目录，问题就解决了。