{"id":7864,"date":"2025-10-26T10:47:31","date_gmt":"2025-10-26T10:47:31","guid":{"rendered":"https:\/\/focary.app\/blog\/?p=7864"},"modified":"2025-10-26T11:51:22","modified_gmt":"2025-10-26T11:51:22","slug":"how-to-generate-ssh-key-for-github-securely","status":"publish","type":"post","link":"https:\/\/focary.app\/blog\/how-to-generate-ssh-key-for-github-securely\/","title":{"rendered":"9 Steps to Master How to Generate SSH Key for GitHub"},"content":{"rendered":"\n

Midway through a deployment. Jenkins pipeline throwing errors. GitHub rejecting pushes. Why? No SSH key. Rookie mistake. <\/p>\n\n\n\n

Happens all the time. I\u2019ve been coding, deploying, and securing repos for over 15 years. From bare-metal servers to cloud-native CI\/CD, I\u2019ve seen it all. If you don\u2019t know how to generate SSH key for GitHub properly, you\u2019re leaving the door wide open. <\/p>\n\n\n\n

This guide walks you through every step\u2014no fluff, no shortcuts. And yeah, I use Focary\u2019s web Pomodoro<\/a> timer to stay locked in while setting up keys across multiple environments. Keeps me focused. Keeps me sane.<\/p>\n\n\n\n

1. Check for Existing SSH Keys<\/h2>\n\n\n\n

Before generating anything, check your system. No point duplicating keys or cluttering your .ssh<\/code> directory. Open your terminal and run:<\/p>\n\n\n\n

bash<\/p>\n\n\n\n

ls -al ~\/.ssh\n<\/code><\/pre>\n\n\n\n
You\u2019re looking for files like id_rsa.pub<\/code>, id_ed25519.pub<\/code>, or any custom-named public keys. If they exist, great. If not, we move forward.<\/p>\n\n\n\n
I always name mine with project context. Like id_ed25519_github_main<\/code>\u2014makes it easier when juggling multiple repos. Especially when working with clients who demand isolated access.<\/p>\n\n\n\n
And yeah, I use Focary\u2019s Pomodoro timer here. 25-minute sprint to audit keys across machines. No distractions. Just terminal, coffee, and focus.<\/p>\n\n\n\n
2. Generate a New SSH Key<\/h2>\n\n\n\n
Now the real work begins. Use ssh-keygen<\/code> to create a new key pair. I prefer Ed25519 over RSA. Faster. More secure. Supported by GitHub.<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
ssh-keygen -t ed25519 -C \"your_email@example.com\"\n<\/code><\/pre>\n\n\n\n
That -C<\/code> flag? It\u2019s just a label. Helps identify the key later. When prompted, name the file something meaningful. Don\u2019t just hit enter.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
Enter file in which to save the key (\/home\/user\/.ssh\/id_ed25519): \/home\/user\/.ssh\/id_ed25519_github_main\n<\/code><\/pre>\n\n\n\n
Add a passphrase. Always. Even if it\u2019s annoying. Security matters. I use Bitwarden to store mine. Encrypted. Synced. Bulletproof.<\/p>\n\n\n\n
3. Add the Key to the SSH Agent<\/h2>\n\n\n\n
You don\u2019t wanna type your passphrase every time you push code. That\u2019s where ssh-agent<\/code> comes in. It remembers your key. Keeps it loaded.<\/p>\n\n\n\n
Start the agent:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
eval \"$(ssh-agent -s)\"\n<\/code><\/pre>\n\n\n\n
Then add your key:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
ssh-add ~\/.ssh\/id_ed25519_github_main\n<\/code><\/pre>\n\n\n\n
Done. Now your system knows what to do. No more manual entry. No more friction.<\/p>\n\n\n\n
I usually do this during my second Pomodoro block. First block is setup. Second is optimization. Focary\u2019s timer keeps me from rushing. Or skipping steps.<\/p>\n\n\n\n
4. Copy the Public Key<\/h2>\n\n\n\n
Time to grab the public key and paste it into GitHub. Use:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
cat ~\/.ssh\/id_ed25519_github_main.pub<\/code><\/pre>\n\n\n\n
Copy the output. All of it. Starts with ssh-ed25519<\/code> and ends with your email. Don\u2019t miss a character. One typo and GitHub throws a fit.<\/p>\n\n\n\n
I paste it into a temporary markdown file first. Just to double-check formatting. Learned that the hard way after a 2-hour debug session.<\/p>\n\n\n\n
5. Add the Key to GitHub<\/h2>\n\n\n\n
Log into GitHub. Go to:<\/p>\n\n\n\n
Settings > SSH and GPG keys > New SSH key<\/strong><\/p>\n\n\n\n
Paste your public key. Name it something useful. Like \u201cWork Laptop – Main Repo Access.\u201d Hit save.<\/p>\n\n\n\n
Boom. You\u2019re connected.<\/p>\n\n\n\n
As GeeksforGeeks explains, SSH keys allow encrypted communication between your machine and GitHub without needing passwords. It\u2019s faster. Safer. Cleaner.<\/p>\n\n\n\n
6. Test the Connection<\/h2>\n\n\n\n
Don\u2019t assume it works. Test it.<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
ssh -T git@github.com<\/code><\/pre>\n\n\n\n
You should see:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
Hi username! You've successfully authenticated, but GitHub does not provide shell access.<\/code><\/pre>\n\n\n\n
If you get a permission denied error, check your key path, agent status, and GitHub settings. Happens more than you\u2019d think.<\/p>\n\n\n\n
I keep a checklist in Notion<\/a>. And yeah, I run this test during my third Pomodoro block. Focary\u2019s timer helps me batch tasks without burning out.<\/p>\n\n\n\n
7. Configure Git to Use SSH<\/h2>\n\n\n\n
Make sure Git uses SSH instead of HTTPS. Run:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
git remote set-url origin git@github.com:username\/repo.git<\/code><\/pre>\n\n\n\n
Replace username\/repo.git<\/code> with your actual repo path. You can verify with:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
git remote -v<\/code><\/pre>\n\n\n\n
If you see https:\/\/<\/code>, fix it. SSH is the goal. HTTPS prompts for credentials. SSH doesn\u2019t.<\/p>\n\n\n\n
I\u2019ve seen junior devs push to HTTPS for months without realizing. Total time sink. Fix it early.<\/p>\n\n\n\n
8. Use Multiple Keys (Advanced)<\/h2>\n\n\n\n
Got multiple GitHub accounts<\/a>? You\u2019ll need to configure ~\/.ssh\/config<\/code>. Here\u2019s a sample:<\/p>\n\n\n\n
C\u00f3digo<\/p>\n\n\n\n
Host github.com-work\n  HostName github.com\n  User git\n  IdentityFile ~\/.ssh\/id_ed25519_work<\/code><\/pre>\n\n\n\n
Then clone using:<\/p>\n\n\n\n
bash<\/p>\n\n\n\n
git clone git@github.com-work:username\/repo.git<\/code><\/pre>\n\n\n\n
This setup avoids conflicts. Keeps your keys organized. I use it for client work, personal projects, and test environments.<\/p>\n\n\n\n
And yes, I configure this during my fourth Pomodoro block. Focary\u2019s timer helps me avoid context-switching. One task. One focus.<\/p>\n\n\n\n
9. Rotate Keys Periodically<\/h2>\n\n\n\n
Security isn\u2019t static. Rotate your keys every 6\u201312 months. Especially if you work in fintech, healthcare, or government.<\/p>\n\n\n\n
Delete old keys from GitHub. Generate new ones. Update your agent and config files.<\/p>\n\n\n\n
I schedule this quarterly. Focary\u2019s Pomodoro timer makes it manageable. 25 minutes to rotate keys across all machines. No stress. No skipped steps.<\/p>\n\n\n\n
As GitHub\u2019s official documentation states, SSH keys are critical for secure authentication. Treat them like passwords. Rotate. Protect. Audit.<\/p>\n\n\n\n
How to Generate SSH Key for GitHub<\/strong><\/h2>\n\n\n\n
\"9<\/figure>\n\n\n\n
Hands sweaty. Terminal blinking. You just pushed code to GitHub via SSH. No password prompts. No errors. Just clean, secure authentication.<\/p>\n\n\n\n
That\u2019s the feeling. Like nailing a perfect drywall corner. Or watching varnish cure without bubbles. Satisfaction.<\/p>\n\n\n\n
Learning how to generate SSH key for GitHub isn\u2019t just technical. It\u2019s foundational. It\u2019s the difference between amateur and pro. Between friction and flow.<\/p>\n\n\n\n
And if you\u2019re juggling multiple environments, repos, or clients\u2014use Focary\u2019s web Pomodoro timer. It\u2019s free. It\u2019s simple. It keeps your brain locked in when the terminal starts throwing curveballs.<\/p>\n\n\n\n
Because in this game, focus isn\u2019t optional. It\u2019s everything.<\/p>\n\n\n\n
Sources:<\/strong><\/p>\n\n\n\n