<p>In the dynamic realm of software development, it's not uncommon for developers to find themselves juggling multiple GitHub accounts—one for work and another for personal projects. Navigating this dual identity on Ubuntu/Mac requires a thoughtful approach, particularly when it comes to managing SSH keys. This article serves as a practical guide to seamlessly use two or more GitHub accounts on Ubuntu/Mac by employing multiple SSH keys.</p>

<h2>
  <a name="the-dilemma" href="#the-dilemma">
  </a>
  The Dilemma
</h2>

<p>Managing work and personal GitHub accounts simultaneously poses a unique challenge. A key aspect of addressing this challenge is the need for separate SSH keys, ensuring secure and efficient authentication for each account.</p>

<h2>
  <a name="understanding-ssh-keys" href="#understanding-ssh-keys">
  </a>
  Understanding SSH Keys
</h2>

<p>SSH keys play a pivotal role in secure authentication. By utilizing distinct keys for different GitHub accounts, developers can maintain a clear separation between their professional and personal coding endeavours.</p>

<h2>
  <a name="generating-ssh-keys-for-each-github-account" href="#generating-ssh-keys-for-each-github-account">
  </a>
  Generating SSH Keys for Each GitHub Account
</h2>

<h3>
  <a name="work-accountexample" href="#work-accountexample">
  </a>
  Work Account(example):
</h3>

<p>Open the terminal and generate an SSH key using: </p>

<p><code>ssh-keygen -t rsa -b 4096 -C "your-email@work.com"</code></p>

<p>Save the key to an appropriate directory. By default it is in the “~/.ssh” directory you can keep it that way.</p>

<p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwvnmqqlt320ux055dq7e.png" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwvnmqqlt320ux055dq7e.png" alt="Image description" loading="lazy" width="800" height="141"></a><br>
If you want to give a specific name to your key, it can be changed by renaming the file in which you want the key to be saved in. Renaming of keys can be used to properly identify different keys you saved.</p>
<h3>
  <a name="personal-account" href="#personal-account">
  </a>
  Personal Account:
</h3>

<p>Repeat the process with a different email for your personal GitHub account.</p>
<h2>
  <a name="configuring-ssh-config-file" href="#configuring-ssh-config-file">
  </a>
  Configuring SSH Config File
</h2>

<p>To manage multiple SSH keys effectively, edit your SSH config file. Add the following lines:<br>
Once the Keys properly generated, they should be found in the “~/.ssh” directory. </p>

<p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqwejp2b8ldbz7l16o6xz.jpg" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqwejp2b8ldbz7l16o6xz.jpg" alt="Image description" loading="lazy" width="800" height="58"></a></p>

<p>If all the key generated are available, then head to your different GitHub accounts on <a href="https://github.com">GitHub.com</a></p>

<p>Head  to the your profile settings and select “SSH and GPG keys” and click “New SSH key”</p>

<p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy6errbe7rvi5gxehzzea.jpg" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy6errbe7rvi5gxehzzea.jpg" alt="Image description" loading="lazy" width="800" height="302"></a></p>

<p>You need to add you generated public key that can be obtained from reading the public keys generated. With the command<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>cat ~/.ssh/&lt;your_key_name&gt;.pub
</code></pre>
<div class="highlight__panel js-actions-panel">
<div class="highlight__panel-action js-fullscreen-code-action">
    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-on"><title>Enter fullscreen mode</title>
    <path d="M16 3h6v6h-2V5h-4V3zM2 3h6v2H4v4H2V3zm18 16v-4h2v6h-6v-2h4zM4 19h4v2H2v-6h2v4z"></path>
</svg>

    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-off"><title>Exit fullscreen mode</title>
    <path d="M18 7h4v2h-6V3h2v4zM8 9H2V7h4V3h2v6zm10 8v4h-2v-6h6v2h-4zM8 15v6H6v-4H2v-2h6z"></path>
</svg>

</div>
</div>
</div>



<p>Copy and paste the result from the public key in the Key text area provided on your GitHub and click “Add SSH key”.<br>
Repeat the step for both GitHub accounts and any accounts you wish to add this way. </p>
<h2>
  <a name="bash-code" href="#bash-code">
  </a>
  Bash Code
</h2>

<p>To write the bash code go to the “.shh” folder and create a file to create a “config” text file using vim to properly separate the different public keys. </p>

<ol>
<li>Open your terminal</li>
<li>Go to the SSH folder using <code>cd ~/.ssh</code>.</li>
<li>Create a config file using the command “vim config”.</li>
<li>Insert the correct text below in the config file by replacing the data with your private data.</li>
<li>Check that the content of the config file is properly inserted using <code>cat ~/.ssh/config</code>
</li>
</ol>

<p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fw8rslficm7kkoxooi6oy.png" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fw8rslficm7kkoxooi6oy.png" alt="Image description" loading="lazy" width="800" height="726"></a></p>
<h3>
  <a name="personal-account" href="#personal-account">
  </a>
  Personal account
</h3>


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>Host github.com-personal
            HostName github.com
            IdentityFile ~/.ssh/&lt;Your private key&gt;
</code></pre>
<div class="highlight__panel js-actions-panel">
<div class="highlight__panel-action js-fullscreen-code-action">
    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-on"><title>Enter fullscreen mode</title>
    <path d="M16 3h6v6h-2V5h-4V3zM2 3h6v2H4v4H2V3zm18 16v-4h2v6h-6v-2h4zM4 19h4v2H2v-6h2v4z"></path>
</svg>

    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-off"><title>Exit fullscreen mode</title>
    <path d="M18 7h4v2h-6V3h2v4zM8 9H2V7h4V3h2v6zm10 8v4h-2v-6h6v2h-4zM8 15v6H6v-4H2v-2h6z"></path>
</svg>

</div>
</div>
</div>

<h3>
  <a name="work-account" href="#work-account">
  </a>
  Work account
</h3>


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>Host github.com-work
            HostName github.com
        IdentityFile ~/.ssh/&lt;Your work key&gt;
</code></pre>
<div class="highlight__panel js-actions-panel">
<div class="highlight__panel-action js-fullscreen-code-action">
    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-on"><title>Enter fullscreen mode</title>
    <path d="M16 3h6v6h-2V5h-4V3zM2 3h6v2H4v4H2V3zm18 16v-4h2v6h-6v-2h4zM4 19h4v2H2v-6h2v4z"></path>
</svg>

    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-off"><title>Exit fullscreen mode</title>
    <path d="M18 7h4v2h-6V3h2v4zM8 9H2V7h4V3h2v6zm10 8v4h-2v-6h6v2h-4zM8 15v6H6v-4H2v-2h6z"></path>
</svg>

</div>
</div>
</div>

<h2>
  <a name="bash-testing" href="#bash-testing">
  </a>
  Bash Testing
</h2>

<p>Testing the Configuration</p>
<h3>
  <a name="work-account" href="#work-account">
  </a>
  Work account
</h3>


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>ssh -T git@github.com-work
</code></pre>
<div class="highlight__panel js-actions-panel">
<div class="highlight__panel-action js-fullscreen-code-action">
    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-on"><title>Enter fullscreen mode</title>
    <path d="M16 3h6v6h-2V5h-4V3zM2 3h6v2H4v4H2V3zm18 16v-4h2v6h-6v-2h4zM4 19h4v2H2v-6h2v4z"></path>
</svg>

    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-off"><title>Exit fullscreen mode</title>
    <path d="M18 7h4v2h-6V3h2v4zM8 9H2V7h4V3h2v6zm10 8v4h-2v-6h6v2h-4zM8 15v6H6v-4H2v-2h6z"></path>
</svg>

</div>
</div>
</div>

<h3>
  <a name="personal-account" href="#personal-account">
  </a>
  Personal account
</h3>


<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>ssh -T git@github.com-personal
</code></pre>
<div class="highlight__panel js-actions-panel">
<div class="highlight__panel-action js-fullscreen-code-action">
    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-on"><title>Enter fullscreen mode</title>
    <path d="M16 3h6v6h-2V5h-4V3zM2 3h6v2H4v4H2V3zm18 16v-4h2v6h-6v-2h4zM4 19h4v2H2v-6h2v4z"></path>
</svg>

    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-off"><title>Exit fullscreen mode</title>
    <path d="M18 7h4v2h-6V3h2v4zM8 9H2V7h4V3h2v6zm10 8v4h-2v-6h6v2h-4zM8 15v6H6v-4H2v-2h6z"></path>
</svg>

</div>
</div>
</div>


<p>While testing you might be prompted to enter a password to unlock the private key. Enter the password given to the key that you generate in the steps above to continue with the operation.</p>

<p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fiwl9siv1gw1s23s38tsb.png" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fiwl9siv1gw1s23s38tsb.png" alt="Image description" loading="lazy" width="800" height="543"></a><br>
Here is what should be seen when the keys are properly distributed.</p>

<p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fruvl10wxbb0n5129fsuf.png" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fruvl10wxbb0n5129fsuf.png" alt="Image description" loading="lazy" width="800" height="74"></a></p>
<h2>
  <a name="adding-ssh-keys-to-the-authentication-agent" href="#adding-ssh-keys-to-the-authentication-agent">
  </a>
  Adding SSH Keys to the Authentication Agent
</h2>

<p>After configuring multiple SSH keys and testing the setup, you can enhance the workflow by using the <code>ssh-add</code> command. This command adds private keys to the SSH authentication agent, eliminating the need to enter the passphrase every time you use the keys.</p>

<p>Open a terminal and run the following commands for each key:</p>

<p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Faqnc9ujkfkrzot0fa70p.png" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Faqnc9ujkfkrzot0fa70p.png" alt="Image description" loading="lazy" width="800" height="223"></a></p>

<p>Note: You can then list all the ssh-keys information to verify that your keys are well implemented. By doing the command<br>
</p>

<div class="highlight js-code-highlight">
<pre class="highlight plaintext"><code>ssh-add -l
</code></pre>
<div class="highlight__panel js-actions-panel">
<div class="highlight__panel-action js-fullscreen-code-action">
    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-on"><title>Enter fullscreen mode</title>
    <path d="M16 3h6v6h-2V5h-4V3zM2 3h6v2H4v4H2V3zm18 16v-4h2v6h-6v-2h4zM4 19h4v2H2v-6h2v4z"></path>
</svg>

    <svg xmlns="http://www.w3.org/2000/svg" width="20px" height="20px" viewbox="0 0 24 24" class="highlight-action crayons-icon highlight-action--fullscreen-off"><title>Exit fullscreen mode</title>
    <path d="M18 7h4v2h-6V3h2v4zM8 9H2V7h4V3h2v6zm10 8v4h-2v-6h6v2h-4zM8 15v6H6v-4H2v-2h6z"></path>
</svg>

</div>
</div>
</div>



<h2>
  <a name="organizing-workspaces" href="#organizing-workspaces">
  </a>
  Organizing Workspaces
</h2>

<p>Consider organizing your workspaces effectively, keeping work and personal projects in separate directories. This helps maintain a clear distinction between the two.</p>

<h2>
  <a name="updating-git-configurations" href="#updating-git-configurations">
  </a>
  Updating Git Configurations
</h2>

<p>Update your Git configurations to align with the new SSH key setup. Ensure consistency across all relevant settings for a smooth experience.</p>

<h2>
  <a name="conclusion-a-seamless-workflow" href="#conclusion-a-seamless-workflow">
  </a>
  Conclusion: A Seamless Workflow
</h2>

<p>By following these steps, you've successfully configured multiple SSH keys for your dual GitHub accounts on Ubuntu/Mac. This setup ensures a harmonious balance between your professional and personal coding pursuits, enhancing both security and workflow.</p>



In the dynamic realm of software development, it's not uncommon for developers to find themselves juggling multiple GitHub accounts—one for work and another for personal projects. Navigating this dual identity on Ubuntu/Mac requires a thoughtful approach, particularly when it comes to managing SSH keys. This article serves as a practical guide to seamlessly use two or more GitHub accounts on Ubuntu/Mac by employing multiple SSH keys.

## The Dilemma
Managing work and personal GitHub accounts simultaneously poses a unique challenge. A key aspect of addressing this challenge is the need for separate SSH keys, ensuring secure and efficient authentication for each account.

## Understanding SSH Keys
SSH keys play a pivotal role in secure authentication. By utilizing distinct keys for different GitHub accounts, developers can maintain a clear separation between their professional and personal coding endeavours.


## Generating SSH Keys for Each GitHub Account

### Work Account(example):
Open the terminal and generate an SSH key using: 

`ssh-keygen -t rsa -b 4096 -C "your-email@work.com"`

Save the key to an appropriate directory. By default it is in the “~/.ssh” directory you can keep it that way.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wvnmqqlt320ux055dq7e.png)
If you want to give a specific name to your key, it can be changed by renaming the file in which you want the key to be saved in. Renaming of keys can be used to properly identify different keys you saved.


### Personal Account:
Repeat the process with a different email for your personal GitHub account.



## Configuring SSH Config File
To manage multiple SSH keys effectively, edit your SSH config file. Add the following lines:
Once the Keys properly generated, they should be found in the “~/.ssh” directory. 

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qwejp2b8ldbz7l16o6xz.jpg)

If all the key generated are available, then head to your different GitHub accounts on [GitHub.com](https://github.com)

Head  to the your profile settings and select “SSH and GPG keys” and click “New SSH key”

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/y6errbe7rvi5gxehzzea.jpg)

You need to add you generated public key that can be obtained from reading the public keys generated. With the command 

```
cat ~/.ssh/<your_key_name>.pub
```
 Copy and paste the result from the public key in the Key text area provided on your GitHub and click “Add SSH key”.
Repeat the step for both GitHub accounts and any accounts you wish to add this way. 



## Bash Code

To write the bash code go to the “.shh” folder and create a file to create a “config” text file using vim to properly separate the different public keys. 

1. Open your terminal
2. Go to the SSH folder using `cd ~/.ssh`.
3. Create a config file using the command “vim config”.
4. Insert the correct text below in the config file by replacing the data with your private data.
5. Check that the content of the config file is properly inserted using `cat ~/.ssh/config`

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/w8rslficm7kkoxooi6oy.png)

### Personal account
```
Host github.com-personal
            HostName github.com
            IdentityFile ~/.ssh/<Your private key>
```

### Work account
```
Host github.com-work
            HostName github.com
  	    IdentityFile ~/.ssh/<Your work key>
```

## Bash Testing
Testing the Configuration
### Work account

```
ssh -T git@github.com-work
```
### Personal account

```
ssh -T git@github.com-personal
```
While testing you might be prompted to enter a password to unlock the private key. Enter the password given to the key that you generate in the steps above to continue with the operation.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/iwl9siv1gw1s23s38tsb.png)
Here is what should be seen when the keys are properly distributed.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ruvl10wxbb0n5129fsuf.png)




## Adding SSH Keys to the Authentication Agent

After configuring multiple SSH keys and testing the setup, you can enhance the workflow by using the `ssh-add` command. This command adds private keys to the SSH authentication agent, eliminating the need to enter the passphrase every time you use the keys.

Open a terminal and run the following commands for each key:

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/aqnc9ujkfkrzot0fa70p.png)

Note: You can then list all the ssh-keys information to verify that your keys are well implemented. By doing the command

```
ssh-add -l
```


## Organizing Workspaces
Consider organizing your workspaces effectively, keeping work and personal projects in separate directories. This helps maintain a clear distinction between the two.

## Updating Git Configurations
Update your Git configurations to align with the new SSH key setup. Ensure consistency across all relevant settings for a smooth experience.







## Conclusion: A Seamless Workflow
By following these steps, you've successfully configured multiple SSH keys for your dual GitHub accounts on Ubuntu/Mac. This setup ensures a harmonious balance between your professional and personal coding pursuits, enhancing both security and workflow.



In the dynamic realm of software development, it's not uncommon for developers to find themselves...

What's Hot