This is to get rid of the need for typing in the username and password every time you make a Git push.Ĭopy the public key pbcopy < ~/.ssh/id_rsa.pub and then log in to your personal GitHub account: We already have the SSH public keys ready, and we will ask our GitHub accounts to trust the keys we have created. Adding the new SSH key to the corresponding GitHub account We have two different keys created: ~/.ssh/id_rsa
ARE KEY CODES THE SAME FOR MAC AND PC CODE
The below code will generate the SSH keys, and saves the public key with the tag to ~/.ssh/id_rsa_work_user1.pub $ ssh-keygen -t rsa -C -f "id_rsa_work_user1" Let’s use this default key pair for our personal account.įor the work accounts, we will create different SSH keys. A private key and public key ~/.ssh/id_rsa.pub will be created at the default ssh location ~/.ssh/. When asked for the location to save the keys, accept the default location by pressing enter. If ~/.ssh/id_rsa is available, we can reuse it, or else we can first generate a key to the default ~/.ssh/id_rsa by running: ssh-keygen -t rsa Generating the SSH keysīefore generating an SSH key, we can check to see if we have any existing SSH keys: ls -al ~/.ssh This will list out all existing public and private key pairs, if any. This endeavor is meant to help us all out. I’m sure there are many of you who have been there, done that and many more of you who are just waiting for the next time the same thing occurs (myself included!). My laziness in not documenting the process and inability to remember the steps makes me spent a decent amount of time getting the bits and pieces from all over the web and then somehow making it work. Every single time I happen to change my Mac or need to Git push with a new work account, I end up surfing for the how to’s of something I have done over half a dozen times.
The need to manage multiple GitHub accounts on the same machine comes up at some point in time for most developers.
0 kommentar(er)
