对我来说，解决方案是:

配置文件的权限应该是600。Chmod 600 config

如上面的评论所述 generalopinion

无需修改配置文件内容。

在Ubuntu 14.04(也许更早，也许仍然如此)你甚至不需要控制台:

start seahorse or launch that thing you find searching for "key" create an SSH key there (or import one) no need to leave the passphrase empty it is offered to you to even push the public key to a server (or more) you will end up with an ssh-agent running and this key loaded, but locked using ssh will pickup the identity (i.e. key) through the agent on first use during the session, the passphrase will be checked and you have the option to automatically unlock the key on login this means the login auth will be used to wrap the passphrase of the key note: if you want to forward your identity (i.e. agent-forwarding) invoke your ssh with -A or make that the default otherwise you can't authenticate with that key on a machine you login to later to a third machine

在Mac OS X Lion系统下，这并没有为我解决同样的问题。最后我补充道:

ssh-add ~/.ssh/id_rsa &>/dev/null

到我的.zshrc(但.profile也可以)，这似乎已经修复了它。

(建议地址:http://geek.michaelgrace.org/2011/09/permanently-add-ssh-key-ssh-add/)

非常简单的^_^两步

1.Yum安装keychain

2.将下面的代码添加到.bash_profile

/usr/bin/keychain $HOME/.ssh/id_dsa
source $HOME/.keychain/$HOSTNAME-sh

在“~/.”中添加以下行。Bashrc“为我解决了这个问题。我使用的是Ubuntu 14.04桌面。

eval `gnome-keyring-daemon --start`
USERNAME="reynold"
export SSH_AUTH_SOCK="$(ls /run/user/$(id -u $USERNAME)/keyring*/ssh|head -1)"
export SSH_AGENT_PID="$(pgrep gnome-keyring)"

我在Mac OSX(10.10)上通过使用-K选项ssh-add解决了这个问题:

ssh-add -K ~/.ssh/your_private_key

对于macOS 10.12及以上版本，您需要额外编辑您的ssh配置，如下所示:https://github.com/jirsbek/SSH-keys-in-macOS-Sierra-keychain