<h2>What is an SSH Key?</h2>
An SSH key is a pair of cryptographic keys used for secure authentication. Think of it like a digital lock and key:
<ul>
<li>Public Key - The lock (shared with GitHub)</li>
<li>Private Key - The key (stays on your computer, never share!)</li>
</ul>
<h2>Why Do You Need SSH Keys?</h2>
The Problem with HTTPS
<pre><code># Every time you push with HTTPS:
git push

Username: your-username
Password: your-password or token

# Annoying to type every time!
</code></pre>
The Solution with SSH
<pre><code># With SSH configured:
git push

# No username/password needed!
# Automatic authentication!
</code></pre>
<h2>How SSH Keys Work</h2>
Here’s a simple visualization of the authentication flow:
<pre><code>Your Computer GitHub
───────────── ──────

1. Generate key pair
 ├── id_rsa (private key)
 └── id_rsa.pub (public key)

2. Upload public key ──────────→ Stored on GitHub

3. When you push:
 Private key signs request ───→ GitHub verifies with public key
 Authentication successful
</code></pre>
When you try to push code:
<ol>
<li>Your computer uses the private key to create a signature</li>
<li>GitHub checks this signature with your stored public key</li>
<li>If they match, you’re authenticated</li>
</ol>
<h2>Step-by-Step Setup Guide</h2>
Let’s set up SSH keys together. I’ll guide you through each step.
<h3>Step 1: Check if SSH Key Already Exists</h3>
Open Git Bash or your terminal in VS Code:
<pre><code>ls -la ~/.ssh
</code></pre>
If you see files like <code>idrsa</code>_, <code>idrsa.pub</code>, <code>ided25519</code>, or _<code>ided25519.pub</code>, you already have a key. Otherwise, continue to Step 2.
<h3>Step 2: Generate New SSH Key</h3>
<pre><code>ssh-keygen -t ed25519 -C &quot;your-email@example.com&quot;
</code></pre>
Important: Replace <code>your-email@example.com</code> with your actual GitHub email!
You’ll see:
<pre><code>Generating public/private ed25519 key pair.
Enter file in which to save the key (/c/Users/YourName/.ssh/id_ed25519):
</code></pre>
Press ENTER to use the default location.
<pre><code>Enter passphrase (empty for no passphrase):
</code></pre>
Press ENTER for no passphrase (or type one for extra security).
<pre><code>Enter same passphrase again:
</code></pre>
Press ENTER again.
You should see:
<pre><code>Your identification has been saved in /c/Users/YourName/.ssh/id_ed25519
Your public key has been saved in /c/Users/YourName/.ssh/id_ed25519.pub
</code></pre>
SSH key created successfully!
<h3>Step 3: Start SSH Agent</h3>
<pre><code>eval &quot;$(ssh-agent -s)&quot;
</code></pre>
You should see: <code>Agent pid 1234</code>
<h3>Step 4: Add Private Key to SSH Agent</h3>
<pre><code>ssh-add ~/.ssh/id_ed25519
</code></pre>
Output: <code>Identity added: /c/Users/YourName/.ssh/id_ed25519</code>
<h3>Step 5: Copy Your Public Key</h3>
<pre><code>cat ~/.ssh/id_ed25519.pub
</code></pre>
This will display your public key. It looks something like:
<pre><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGx... your-email@gmail.com
</code></pre>
Select and copy the ENTIRE output (from <code>ssh-ed25519</code> to your email).
<h3>Step 6: Add SSH Key to GitHub</h3>
Now, let’s add this key to your GitHub account:
<ol>
<li>Go to <a href="https://github.com" target="_blank" rel="noopener nofollow">GitHub</a></li>
<li>Click your profile picture (top right)</li>
<li>Click Settings</li>
<li>Click SSH and GPG keys (left sidebar)</li>
<li>Click New SSH key (green button)</li>
<li>Fill in:</li>
</ol>
<ul>
<li>Title: <code>My Laptop</code> or <code>VS Code Windows</code> (any name to identify this computer)</li>
<li>Key: Paste the public key you copied</li>
</ul>
<ol>
<li>Click Add SSH key</li>
<li>Confirm with your GitHub password if prompted</li>
</ol>
SSH key added to GitHub successfully!
<h3>Step 7: Test Your Connection</h3>
Let’s verify everything is working:
<pre><code>ssh -T git@github.com
</code></pre>
First time, you’ll see:
<pre><code>The authenticity of host &#x27;github.com&#x27;... can&#x27;t be established.
Are you sure you want to continue connecting (yes/no)?
</code></pre>
Type <code>yes</code> and press ENTER.
You should see:
<pre><code>Hi YourUsername! You&#x27;ve successfully authenticated, but GitHub does not provide shell access.
</code></pre>
Connection successful! You’re all set up!
<h2>Using SSH with Your Repositories</h2>
<h3>For New Repositories</h3>
When creating a repo on GitHub, use the SSH URL:
<pre><code>git clone git@github.com:username/repo-name.git
</code></pre>
<h3>For Existing Repositories (Switch from HTTPS to SSH)</h3>
If you’re currently using HTTPS, switch to SSH:
<pre><code># Check current remote URL
git remote -v

# Change to SSH
git remote set-url origin git@github.com:username/repo.git

# Verify the change
git remote -v
</code></pre>
<h3>Now Push Without Passwords</h3>
<pre><code>git add .
git commit -m &quot;My commit message&quot;
git push

# No username/password prompt!
</code></pre>
<h2>HTTPS vs SSH: Visual Comparison</h2>
<h3>HTTPS (The Old Way)</h3>
<pre><code>Your Computer → git push → GitHub
 ↓
 Need username &amp; password
 Type credentials every time
</code></pre>
<h3>SSH (The Better Way)</h3>
<pre><code>Your Computer → git push → GitHub
 Private key Public key
 ↓
 Automatic match
 No typing needed
</code></pre>
<h2>Common Issues &amp; Solutions</h2>
<h3>Problem 1: Permission Denied</h3>
<pre><code>git push
# Permission denied (publickey)
</code></pre>
Solution:
<pre><code># Check if key is added to agent
ssh-add -l

# If empty or error, add it again
ssh-add ~/.ssh/id_ed25519
</code></pre>
<h3>Problem 2: Can’t Find SSH Key</h3>
<pre><code>ls ~/.ssh
# No such file or directory
</code></pre>
Solution:
<pre><code># Create .ssh directory
mkdir ~/.ssh
chmod 700 ~/.ssh

# Generate key again
ssh-keygen -t ed25519 -C &quot;your-email@gmail.com&quot;
</code></pre>
<h3>Problem 3: Still Asking for Password</h3>
<pre><code>git push
# Still prompting for password!
</code></pre>
Solution:
<pre><code># Check if you&#x27;re using HTTPS URL
git remote -v

# If it shows https://, change to SSH
git remote set-url origin git@github.com:username/repo.git
</code></pre>
<h2>Understanding Your SSH Files</h2>
After setup, you’ll have these files in <code>~/.ssh/</code>:
<pre><code>~/.ssh/
├── id_ed25519 ← Your PRIVATE key (NEVER share!)
├── id_ed25519.pub ← Your PUBLIC key (safe to share)
└── known_hosts ← List of trusted servers
</code></pre>
Security Reminder:
<ul>
<li>Never share your private key (<code>id_ed25519</code>)</li>
<li>Safe to share your public key (<code>id_ed25519.pub</code>)</li>
<li>Private key = Your password, keep it secret!</li>
</ul>
<h2>Security Best Practices</h2>
1. Use Different Keys for Different Computers
<ul>
<li>Label them clearly on GitHub: “Work Laptop”, “Personal Desktop”</li>
<li>Easy to revoke if one computer is compromised</li>
</ul>
2. Add a Passphrase for Extra Security (Optional)
<pre><code>ssh-keygen -t ed25519 -C &quot;email@gmail.com&quot;
 Enter passphrase: ******
</code></pre>
<ul>
<li>Adds an extra layer of protection</li>
<li>You’ll need to enter it when using the key</li>
</ul>
3. Regularly Review Your Keys
<ul>
<li>Go to GitHub → Settings → SSH keys</li>
<li>Delete any keys from old/unused computers</li>
</ul>
4. Never Commit Private Keys to Git
<ul>
<li>Your private key stays on your computer only</li>
<li>Never add it to any repository</li>
</ul>
<h2>Complete Quick Reference</h2>
Here’s everything in one place for future reference:
<pre><code># 1. Generate SSH key
ssh-keygen -t ed25519 -C &quot;your-email@gmail.com&quot;
# Press ENTER 3 times

# 2. Start SSH agent
eval &quot;$(ssh-agent -s)&quot;

# 3. Add private key to agent
ssh-add ~/.ssh/id_ed25519

# 4. Display and copy public key
cat ~/.ssh/id_ed25519.pub
# Copy the entire output

# 5. Test GitHub connection
ssh -T git@github.com
# Type &#x27;yes&#x27; when prompted

# 6. Change existing repo to SSH
git remote set-url origin git@github.com:username/repo.git

# 7. Push without password
git push
</code></pre>
<h2></h2>
<h2>Key Takeaways</h2>
<ul>
<li>SSH keys provide password-less authentication - Set up once, use forever</li>
<li>Two keys work together - Private (your computer) + Public (GitHub)</li>
<li>More secure than passwords - Cryptographic authentication</li>
<li>One-time setup - 5-10 minutes saves hours of typing</li>
<li>Works with all Git operations - Push, pull, fetch, clone</li>
</ul>
<h2>What’s Next?</h2>
Now that you have SSH set up:
<ol>
<li>Clone your repos with SSH URLs - Use <code>git@github.com:...</code> instead of <code>https://...</code></li>
<li>Update existing repos - Convert HTTPS remotes to SSH</li>
<li>Enjoy password-free workflow - Focus on coding, not authentication</li>
</ol>
<h2>Final Thoughts</h2>
Setting up SSH keys might seem intimidating at first, but it’s a one-time investment that pays dividends every single day. No more interrupting your flow to type passwords. No more managing personal access tokens. Just pure, seamless Git workflow.
If you found this guide helpful, consider sharing it with fellow developers who are just starting their Git journey!
Have questions or ran into issues? Drop a comment below and I’ll help you troubleshoot!
Found this helpful? Give it a reaction and bookmark for future reference!
Happy coding!

SSH Keys for GitHub: A Complete Beginner's Guide