From 08537b1ddba63636b7c08564d10dc4da4319be73 Mon Sep 17 00:00:00 2001
From: tekkub <tekkub@gmail.com>
Date: Mon, 15 Jun 2009 23:32:12 -0600
Subject: And our first guide

---
 _posts/2009-06-15-msysgit-key-setup.textile | 54 +++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100644 _posts/2009-06-15-msysgit-key-setup.textile

(limited to '_posts')

diff --git a/_posts/2009-06-15-msysgit-key-setup.textile b/_posts/2009-06-15-msysgit-key-setup.textile
new file mode 100644
index 0000000..faf51db
--- /dev/null
+++ b/_posts/2009-06-15-msysgit-key-setup.textile
@@ -0,0 +1,54 @@
+---
+layout: guide
+title: Generating SSH keys with msysgit
+subtitle: This guide will step you through the process of generating a keypair in msysgit and uploading it to GitHub
+categories: windows
+---
+
+Generating an SSH key with msysgit is a fairly straightforward process.  First and foremost, make sure you're working in the Git Bash console, not cmd (the default Windows command line).  You can find Git Bash under the git folder in your start menu, or by right clicking on a folder and selecting "Git Bash Here" if you choose to install context menu items during the msysgit installation.
+
+h3. Backup and remove existing keys
+
+Unless this is your first time installing msys on your computer, you should doublecheck that keys do not already exist.  If they do you can either use the existing key(s) or remove them.  In either case, you should make a backup of the keys.
+
+<pre>$ cd ~/.ssh
+$ ls
+config  id_rsa  id_rsa.pub  known_hosts
+$ cd ..
+$ mkdir ssh_key_backup
+$ cp .ssh/id_rsa* ssh_key_backup
+$ rm .ssh/id_rsa*</pre>
+
+Here we have an existing keypair, @id_rsa@ and @id_rsa.pub@, which we've copied into @~/ssh_key_backup@ before removing.  By default, ssh will use keys in @~/.ssh@ that are named @id_rsa@, @id_dsa@ or @identity@.
+
+h3. Generating a key
+
+Now that we're certain ssh won't use an existing key, it's time to generate a new keypair.  Lets make an RSA keypair:
+
+<pre>$ ssh-keygen -t rsa -c "tekkub@gmail.com"
+Generating public/private rsa key pair.
+Enter file in which to save the key (/c/Users/Tekkub/.ssh/id_rsa):
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /c/Users/Tekkub/.ssh/id_rsa.
+Your public key has been saved in /c/Users/Tekkub/.ssh/id_rsa.pub.
+The key fingerprint is:
+e8:ae:60:8f:38:c2:98:1d:6d:84:60:8c:9e:dd:47:81 tekkub@gmail.com</pre>
+
+At each prompt we just hit enter.  This will generate the key with the default name and no passphrase.  If you want to add a passphrase to your key you can do so later.  You will be prompted for the passphrase every time you push or pull from GitHub, so you might not want to use one unless you are using a shared computer.
+
+h3. Adding the key to your GitHub account
+
+Now launch your browser and open the "account page":https://github.com/account.  In the "SSH Public Keys" section click "add another public key", then paste your key into the "key" field.  If you leave the title blank the key comment (your email) will be used for the title.
+
+!/images/add_key.png!
+
+h3. Testing things out
+
+Testing if our new key works is simple:
+
+<pre>$ ssh git@github.com
+Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access.
+Connection to github.com closed.</pre>
+
+If you do not get the "successfully authenticated" message, check out the "troubleshooting guide":http://github.com/guides/addressing-authentication-problems-with-ssh.
\ No newline at end of file
-- 
cgit v1.3.1