So while the ssh-add -A option should work for most basic cases, I ran into an issue recently where I had 6-7 Vagrant boxes (which uses SSH keys/identities for access) setup on a machine on top of the more common id_rsa.pub in place. Now when you open a new Terminal window, all should be good! Method 2: Add only SSH keys that are in the keychain to the agent. So if you want to never worry about this again, just open up your user’s ~/.bash_profile file like this: nano ~/.bash_profileĪnd add this line to the bottom: ssh-add -A 2>/dev/null Now this works but it won’t persist across reboots. So one solution I found is to run ssh-add with the -A option-which adds all known identities to the SSH agent using any passphrases stored in your keychain-like this: ssh-add -A Method 1: Add all known keys to the SSH agent. ![]() Here are two methods I know of to deal with this issue. ![]() I had this issue as well when attempting to deploy some code using Capistrano.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |