It’s been bugging me for quite a while, but never enough to go and find a solution – until now.
Shamelessly re-posting a perfect guidance from https://apple.stackexchange.com/questions/48502/how-can-i-permanently-add-my-ssh-private-key-to-keychain-so-it-is-automatically:
On OSX, the native
ssh-add client has a special argument to save the private key’s passphrase in the OSX keychain, which means that your normal login will unlock it for use with ssh. On OSX Sierra and later, you also need to configure SSH to always use the keychain (see Step 2 below).
Alternatively you can use a key without a passphrase, but if you prefer the security that’s certainly acceptable with this workflow.
Step 1 – Store the key in the keychain
Just do this once:
ssh-add -K ~/.ssh/[your-private-key]
Enter your key passphrase, and you won’t be asked for it again.
(If you’re on a pre-Sierra version of OSX, you’re done, Step 2 is not required.)
Step 2 – Configure SSH to always use the keychain
It seems that OSX Sierra removed the convenient behavior of persisting your keys between logins, and the update to ssh no longer uses the keychain by default. Because of this, you will get prompted to enter the passphrase for a key after you upgrade, and again after each restart.
The solution is fairly simple, and is outlined in this github thread comment. Here’s how you set it up:
- Ensure you’ve completed Step 1 above to store the key in the keychain.
- If you haven’t already, create an
~/.ssh/configfile. In other words, in the
.sshdirectory in your home dir, make a file called
- In that
.ssh/configfile, add the following lines:
Host * UseKeychain yes AddKeysToAgent yes IdentityFile ~/.ssh/id_rsaChange
~/.ssh/id_rsato the actual filename of your private key. If you have other private keys in your
~.sshdirectory, also add an
IdentityFileline for each of them. For example, I have one additional line that reads
IdentityFile ~/.ssh/id_ed25519for a 2nd private key.The
UseKeychain yesis the key part, which tells SSH to look in your OSX keychain for the key passphrase.
- That’s it! Next time you load any ssh connection, it will try the private keys you’ve specified, and it will look for their passphrase in the OSX keychain. No passphrase typing required.
Source : StackExchange