summaryrefslogtreecommitdiff
path: root/_posts/2009-06-15-msysgit-key-setup.textile
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2009-07-27 01:49:54 -0600
committertekkub <tekkub@gmail.com>2009-07-27 01:49:54 -0600
commitb5a95e8c10b04c5d2add56c9d9815113149adf3f (patch)
treec3387f5b5aeaeb6f8f140665e3af5ee612137cd4 /_posts/2009-06-15-msysgit-key-setup.textile
parent8352e9538ecd1a66a44239a3e775660d91f20d6d (diff)
h3. --> h2.
Diffstat (limited to '_posts/2009-06-15-msysgit-key-setup.textile')
-rw-r--r--_posts/2009-06-15-msysgit-key-setup.textile8
1 files changed, 4 insertions, 4 deletions
diff --git a/_posts/2009-06-15-msysgit-key-setup.textile b/_posts/2009-06-15-msysgit-key-setup.textile
index b0a12eb..651dd9a 100644
--- a/_posts/2009-06-15-msysgit-key-setup.textile
+++ b/_posts/2009-06-15-msysgit-key-setup.textile
@@ -9,7 +9,7 @@ main_category: setup
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
+h2. 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.
@@ -23,7 +23,7 @@ $ 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
+h2. Generating a key
p(. _If you have an existing keypair you wish to use, you can skip this step._
@@ -41,7 +41,7 @@ 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
+h2. 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.
@@ -49,7 +49,7 @@ Make sure you use the public key (@id_rsa.pub@ in our example), and do not add a
!/images/add_key.png!
-h3. Testing things out
+h2. Testing things out
Testing if our new key works is simple: