You can generate SSH keys in a few steps from the command line in order to authenticate your GitHub account. A bad actor will not be able to login or push remotely without access to your secure keys.
GITHUB CLI SSH PASSWORD
Using SSH protocol is more secure than using a text password on the command line. SSH or Secure Shell keys is the name of the key (or protocol) used when you need to authenticate in order to use a provider. My first introduction to SSH was through setting up remote git pushes to GitHub. If you work as an engineer, you've probably set up some SSH keys to login to a service from one machine to another.
Before I get into how I set it up with one command, I want to first explain SSH keys. I delayed setting up my new dev machine to ensure I had enough time to set this up correctly the first time, but it turns out all I needed was the GitHub CLI.
GITHUB CLI SSH HOW TO
I recently got a new mac and always need to look up how to set up SSH on new machines, it is part of development you don't do often but benefit a ton when you do. Setting up SSH is not a trivial thing to do, but now it is a bit more approachable with the GitHub CLI. The alternative is using SSH, secure shell, allowing you to tell GitHub its you. Up until last fall, using your username and password was enough, but that is no longer deemed secure. Then give your key a recognizable title and paste in your public ( id_rsa.pub) key:įinally, test your authentication with: ssh -T you've followed all of these steps correctly, you should see this message: Hi your_user_name! You've successfully authenticated, but GitHub does not provide shell access.When working with a GitHub repository, you'll often need to identify yourself to GitHub. Go to your GitHub settings page and click the "New SSH key" button:
GITHUB CLI SSH WINDOWS
Or for Windows, simply run: clip < ~/.ssh/id_rsa.pub # Windows Add your public SSH key to GitHub Next, you need to copy your public SSH key to the clipboard.įor Linux or Mac, print the contents of your public key to the console with: cat ~/.ssh/id_rsa.pub # Linux Then, add your private key to ssh-agent with: ssh-add ~/.ssh/id_rsa Copy your public SSH key
GITHUB CLI SSH FOR MAC
For it to work properly, it needs to be running and have a copy of your private key.įirst, make sure that ssh-agent is running with: eval "$(ssh-agent -s)" # for Mac and Linux Ssh-agent is a program that starts when you log in and stores your private keys. You can read more about how SSH / RSA key pairs work here. It's extremely important that you never reveal your private key, and only use your public key for things like GitHub authentication. Note: SSH keys are always generated as a pair of public ( id_rsa.pub) and private ( id_rsa) keys. Then generate a new set of keys with: ssh-keygen -t rsa -b 4096 -C check that your keys exist with the ls -al ~/.ssh command and ensure that the output is similar to the one listed above. If you don't see any output or that directory doesn't exist (you get a No such file or directory message), then run: mkdir $HOME/.ssh If your keys already exist, skip ahead to the Copy your public SSH key section below. rw- 1 user_name user_name 12892 Feb 5 18:39 known_hosts rw-r-r- 1 user_name user_name 414 id_rsa.pub If you've already generated SSH keys, you should see output similar to this: -rw- 1 user_name user_name 1766 id_rsa Open a terminal and enter the following command: ls -al ~/.ssh Check for an existing SSH keyįirst, check if you've already generated SSH keys for your machine.
Here's a quick guide to generate and configure an SSH key with GitHub so you never have to authenticate the old fashioned way again. Just think–all of that time you spent entering your email address and password into the console every time you push a commit could have been spent coding. If you use GitHub without setting up an SSH key, you're really missing out.
0 kommentar(er)
