__Do not use PuTTY if you are given the option. GitHub only provides support for openssh.__
##Next: Set Up SSH Keys
We use SSH keys to establish a secure connection between your computer and GitHub. Setting them up is fairly easy, but does involve a number of steps.
To make sure you generate a brand new key, you need to check if one already exists. First, you need to open Git Bash (not the Windows command line), found in the start menu in the git.
Code blocks like those on this page are part of a scripting language called Bash. To use Bash scripts, we need to use an application that was installed with Git called Git Bash.
$ echo 'This is input text'This tooltip tells you what's going on.
A line that begins with the dollar sign ($) indicates a line of Bash script you need to type. To enter it, type the text that follows the $, hitting the return key at the end of each line. You can hover your mouse over each line for an explanation of what the script is doing.
This is output text.
A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We’ve colored output text green in these bootcamp tutorials.
$ echo 'username'Outputs the text in the quotation marks.
Areas of yellow text represent your own personal info, repos, etc. If it is part of an input ($) line, you should replace it with your own info when you type it. If it is part of output text, it is just for your reference. It will automatically show your own info in Git Bash.
Good to know: There will be times when you type code, hit return, and all you are given is another prompt. Some actions that you execute in Git Bash don’t have any output. Don’t worry, if there is ever a problem with your code, Git Bash will let you know.
Good to know: For security reasons, Git Bash will not display what you type when entering passwords. Just type your password and hit the return key.
$ cd ~/.sshChecks to see if there is a directory named ".ssh" in your user directory
If it says “No such file or directory“ skip to __step 3__. Otherwise continue to __step 2__.
2. Backup and remove existing SSH keys.
Since there is already an SSH directory you’ll want to back the old one up and remove it:
$ lsLists all the subdirectories in the current directory config id_rsa id_rsa.pub known_hosts $ mkdir key_backupmakes a subdirectory called "key_backup" in the current directory $ cp id_rsa* key_backupCopies the contents of the id_rsa directory into key_backup directory $ rm id_rsa*Deletes the contents of the id_rsa directory3. Generate a new SSH key. To generate a new SSH key, enter the code below. We want the default settings so when asked to enter a file in which to save the key, just press enter.
$ ssh-keygen -t rsa -C "user_name@username.com"Creates a new ssh key using the provided email Generating public/private rsa key pair. Enter file in which to save the key (/c/Users/your_user_directory/.ssh/id_rsa):Now you need to enter a passphrase.
Passwords aren’t very secure, you already know this. If you use one that’s easy to remember, it’s easier to guess or brute-force (try many options until one works). If you use one that’s random it’s hard to remember, and thus you’re more inclined to write the password down. Both of these are Very Bad Things™. This is why you’re using ssh keys.
But using a key without a passphrase is basically the same as writing down that random password in a file on your computer. Anyone who gains access to your drive has gained access to every system you use that key with. This is also a Very Bad Thing™. The solution is obvious: add a passphrase.
But I don’t want to enter a long passphrase every time I use the key!
Neither do we! Thankfully, there’s a nifty little tool called ssh-agent that can save your passphrase securely so you don’t have to re-enter it. Unfortunately, it takes a little work to get it up and running on Windows. For more information check out our help guide.
Enter passphrase (empty for no passphrase): Enter same passphrase again:Which should give you something like this:
Your identification has been saved in /c/Users/your_user_directory/.ssh/id_rsa. Your public key has been saved in /c/Users/your_user_directory/.ssh/id_rsa.pub. The key fingerprint is: 01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db user_name@username.com4. Add your SSH key to GitHub. On the GitHub site _Click “Account Settings”_ > _Click “SSH Public Keys”_ > _Click “Add another public key”_ Open the id_rsa.pub file with a text editor (Notepad will do just fine). This is your SSH key. __It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace.__ Now paste it into the “Key” field.
Hit “Add Key.”
5. Test everything out.
To make sure everything is working you’ll now SSH to GitHub. Don’t change the “git@github.com” part. That’s supposed to be there.
$ ssh git@github.comAttempts to ssh to github
Which should give you this:
The authenticity of host 'github.com (207.97.227.239)' can't be established. RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48. Are you sure you want to continue connecting (yes/no)?Don’t worry, this is supposed to happen. Type “yes”.
PTY allocation request failed on channel 0 Hi username! You've successfully authenticated, but GitHub does not provide shell access. Connection to github.com closed.Don’t worry, about the “failed” part. All you should care about is that you see “You’ve successfully authenticated” ##Then: Set Up Your Info Now that you have Git set up and your SSH keys entered into GitHub, it’s time to configure your personal info. 1. Set your username and email. Git tracks who makes each commit by checking the user’s name and email. In addition, we use this info to associate your commits with your GitHub account. To set these, enter the code below, replacing the name and email with your own. The name should be your _actual name_, not your GitHub username.
$ git config --global user.name "Firstname Lastname"Sets the name of the user for all git instances on the system $ git config --global user.email "user_name@username.com"Sets the email of the user for all git instances on the system2. Set your GitHub token. Some tools connect to GitHub without SSH. To use these tools properly you need to find and configure your API Token. On the GitHub site _Click “Account Settings”_ > _Click “Account Admin.”_
In Git Bash, run the following code, using your GitHub username and token in place of the ones shown.
$ git config --global github.user usernameSets the GitHub username for all git instances on the system $ git config --global github.token 0123456789your0123456789tokenSets the GitHub token for all git instances on the system__*Note*__ If you ever change your GitHub password, a new token will be created and will need to be updated. ##Lastly: Celebrate Congratulations, you now have Git and GitHub all set up! What do you want to do next?