SSH (Secure Shell) is used to establish secure remote connections over an unsecured network, enabling secure access, management, and data transfer on remote systems, including running commands, transferring files, and managing applications.
Setup SSH keys:
To create an SSH key and add it to your GitHub account, follow these steps:
1. Generate an SSH Key
ssh-keygen -t ed25519 -C "your-email@example.com"
- Replace
"your-email@example.com" with your GitHub email.
- If prompted, press Enter to save the key in the default location (
~/.ssh/id_ed25519).
- Set a passphrase (optional for security).
2. Start the SSH Agent
3. Add the SSH Key to the Agent
ssh-add ~/.ssh/id_ed25519
4. Copy the SSH Key to Clipboard
cat ~/.ssh/id_ed25519.pub | pbcopy # macOS
cat ~/.ssh/id_ed25519.pub | xclip -selection clipboard # Linux
clip < ~/.ssh/id_ed25519.pub # Windows (Git Bash)
(If xclip is not installed, use sudo apt install xclip on Linux)
5. Add the SSH Key to GitHub
- Go to GitHub → Settings → SSH and GPG keys (GitHub SSH Keys).
- Click New SSH Key.
- Paste the copied key into the field and give it a title.
- Click Add SSH Key.
6. Test the SSH Connection
You should see a message like:
Hi username! You've successfully authenticated, but GitHub does not provide shell access.
Now you can clone, push, and pull repositories without entering your GitHub password!
You may be wondering what is ed25519 ?
ed25519 is a modern cryptographic algorithm used for generating SSH keys. It is an alternative to the older RSA algorithm and is considered more secure and faster.
Why Use ed25519 Instead of RSA?
- Stronger Security –
ed25519 provides 128-bit security, while RSA requires a 4096-bit key for similar security.
- Smaller Key Size – The generated keys are much shorter than RSA keys, making them faster to use.
- Faster Performance –
ed25519 is optimized for speed, especially on modern hardware.
- Resistant to Certain Attacks – Unlike RSA,
ed25519 is resistant to side-channel attacks.
Why GitHub Recommends ed25519?
- Since 2021, GitHub suggests using
ed25519 over RSA because of better security and efficiency.
- Older RSA keys (e.g., 1024-bit) are now considered weak.
When Should You Use ed25519?
- Always, unless you’re working with old systems that do not support it.
- If you need maximum security, speed, and smaller key sizes.
Example: Creating an ed25519 SSH Key
ssh-keygen -t ed25519 -C "your-email@example.com"
This creates a strong and secure SSH key for GitHub authentication.
What is the SSH Agent?
The SSH agent is a background process that securely stores your SSH private keys and manages authentication.
Instead of entering your private key passphrase every time you use SSH (e.g., for git push), the agent remembers your key after you add it.
Why Do We Need the SSH Agent?
- Avoid Entering Your Passphrase Repeatedly
- If your SSH key has a passphrase, you would normally need to enter it every time you use
git push or ssh.
- The agent caches the key in memory so you don’t need to enter the passphrase every time.
- Automatic Authentication
- Once the agent has your key, it can sign SSH requests for authentication automatically.
- Keeps Your Private Key Secure
- Your private key stays in memory and is not exposed on disk after adding it.
What Do These Commands Do?
1️⃣ Start the SSH Agent
- This starts the SSH agent in the background.
- The
eval "$(ssh-agent -s)" command initializes the agent and prints its process ID (PID), confirming it’s running.
2️⃣ Add the SSH Key to the Agent
ssh-add ~/.ssh/id_ed25519
- This adds your private key (
~/.ssh/id_ed25519) to the agent.
- Now, the agent will remember the key and use it when making SSH connections.
How to Check If Your Key is Added?
Run:
This lists all keys currently added to the agent. If your key is listed, it means the agent is working correctly.
Example: How This Helps?
Without the agent:
git push origin main
# Every time, you need to enter your SSH passphrase
With the agent:
ssh-add ~/.ssh/id_ed25519
git push origin main
# No need to enter your passphrase again!
Conclusion
- The SSH agent stores your private key securely in memory.
- It automates authentication, so you don’t need to enter your passphrase for every SSH request.
- Adding the key with
ssh-add lets Git and SSH use it without prompting.
Now, you can git push and git pull seamlessly!
But the question is: Can this make unauthorized persons to access with this commands without ssh passphrase?
Does using ssh-agent make your system less secure? Let’s break it down.
Can Someone Else Use My SSH Key Without a Passphrase?
✅ No, If Your System is Secure
- The SSH agent only runs under your user session.
- Other users on the same machine cannot access your agent.
- Your private key is never written to disk in an unprotected way.
- The agent only allows authentication, not direct access to your key.
⚠️ Yes, If Someone Gets Access to Your Session
- If an attacker gains access to your system (e.g., via malware, or if you leave your computer unlocked), they might use your active SSH agent to authenticate without needing your passphrase.
- However, they cannot extract your private key from the agent.
How to Improve Security?
If you want extra security, here are a few things you can do:
1️⃣ Remove Keys from Agent When Not Needed
After using your SSH key, you can remove it from the agent:
This removes all stored keys. Next time you push, you’ll need to re-enter your passphrase.
2️⃣ Use -t (Timeout) for Auto Removal
To automatically remove the key after a set time:
ssh-add -t 3600 ~/.ssh/id_ed25519 # Removes the key after 1 hour
3️⃣ Lock Your Screen When Away
If someone gets access to your logged-in session, they could use your agent to authenticate without needing the passphrase.
Always lock your screen (Ctrl + L or Win + L on Windows/Linux, Cmd + Ctrl + Q on Mac) when stepping away.
4️⃣ Disable Agent Forwarding (Extra Security)
By default, SSH agent forwarding (ssh -A) can expose your keys to remote servers. If you don’t need it, disable it by editing:
And adding:
Summary
- The SSH agent only runs in your session, so no one else can access it unless they get control of your user session.
- Attackers cannot steal your private key from the agent, but if they have access to your session, they could use it.
- To be safe, remove keys when not needed (
ssh-add -D), use timeouts (-t), and always lock your computer.
You’re now both secure and productive with SSH! 🚀
The Rails Drop 