From 31bce646407e26b1cfcbaa585d60771101600678 Mon Sep 17 00:00:00 2001 From: Leslie Murphy Date: Mon, 1 Mar 2010 19:46:56 -0700 Subject: better examples for first time SSL users of github --- _posts/2009-06-15-msysgit-key-setup.textile | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) (limited to '_posts/2009-06-15-msysgit-key-setup.textile') diff --git a/_posts/2009-06-15-msysgit-key-setup.textile b/_posts/2009-06-15-msysgit-key-setup.textile index b73f7df..fc9f320 100644 --- a/_posts/2009-06-15-msysgit-key-setup.textile +++ b/_posts/2009-06-15-msysgit-key-setup.textile @@ -14,6 +14,12 @@ h2. Backup and remove existing keys Unless this is your first time installing msys on your computer, you should double check 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. +First check to see if a ssh key directory exists. +
$ $ cd ~/.ssh
+
+ +If you get a "No such file or directory" error, you can skip the following step to back up the SSH key before generating a new keypair. + 
$ cd ~/.ssh
 $ ls
 config  id_rsa  id_rsa.pub  known_hosts
@@ -54,7 +60,17 @@ h2. Testing things out
 Testing if our new key works is simple:
 
 
$ ssh git@github.com
-Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access.
-Connection to github.com closed.

+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)?
+
+ +Respond with yes to confirm the first-time ssh connection to github: +
yes
+Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
+Enter passphrase for key '/c/Users/tekkub/.ssh/id_rsa':
+ERROR: Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access
+Connection to github.com closed.
+
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 From 8ec040bae0b6a601354973ae79cd2a87c68b519d Mon Sep 17 00:00:00 2001 From: tekkub Date: Tue, 2 Mar 2010 02:12:01 -0700 Subject: Key setup guide tweaks --- _posts/2009-06-15-linux-key-setup.textile | 24 +++++++++++++++++------- _posts/2009-06-15-mac-key-setup.textile | 24 +++++++++++++++++------- _posts/2009-06-15-msysgit-key-setup.textile | 20 +++++++------------- 3 files changed, 41 insertions(+), 27 deletions(-) (limited to '_posts/2009-06-15-msysgit-key-setup.textile') diff --git a/_posts/2009-06-15-linux-key-setup.textile b/_posts/2009-06-15-linux-key-setup.textile index 5cc40b5..ba627f4 100644 --- a/_posts/2009-06-15-linux-key-setup.textile +++ b/_posts/2009-06-15-linux-key-setup.textile @@ -16,8 +16,13 @@ p(. _If you have an existing keypair you wish to use, you can skip this step._ Unless this is your first time setting up ssh or git on your computer, you should double check 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. -
$ cd ~/.ssh
-$ ls
+First check to see if a ssh key directory exists.
+
+
$ cd ~/.ssh

+
+If you get a "No such file or directory" error, you can skip to "Generating a key".
+
+
$ ls
 config                id_rsa.pub
 id_rsa                known_hosts
 $ mkdir key_backup
@@ -59,10 +64,15 @@ $ cat ~/.ssh/id_rsa.pub | xclip -sel clip

 
 h2. Testing things out
 
-Testing if our new key works is simple:
+Testing if our new key works is simple, we just ssh to github.  If this is the first time you're connecting you'll have to save the server's key.  You can confirm the fingerprint on the SSH keys tab of the "account settings page":https://github.com/account
 
 
$ ssh git@github.com
-Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access.
-Connection to github.com closed.

-
-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
+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)? yes
+Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
+ERROR: Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access
+Connection to github.com closed.
+
+ +If you do not get the "successfully authenticated" message, check out the "troubleshooting guide":http://github.com/guides/addressing-authentication-problems-with-ssh. diff --git a/_posts/2009-06-15-mac-key-setup.textile b/_posts/2009-06-15-mac-key-setup.textile index ce88c0e..100e9b1 100644 --- a/_posts/2009-06-15-mac-key-setup.textile +++ b/_posts/2009-06-15-mac-key-setup.textile @@ -16,8 +16,13 @@ p(. _If you have an existing keypair you wish to use, you can skip this step._ Unless this is your first time setting up ssh or git on your computer, you should double check 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. -
$ cd ~/.ssh
-$ ls
+First check to see if a ssh key directory exists.
+
+
$ cd ~/.ssh

+
+If you get a "No such file or directory" error, you can skip to "Generating a key".
+
+
$ ls
 config  id_rsa  id_rsa.pub  known_hosts
 $ mkdir key_backup
 $ cp id_rsa* key_backup
@@ -67,10 +72,15 @@ Make sure you use the public key (@id_rsa.pub@ in our example), and do not add a
 
 h2. Testing things out
 
-Testing if our new key works is simple:
+Testing if our new key works is simple, we just ssh to github.  If this is the first time you're connecting you'll have to save the server's key.  You can confirm the fingerprint on the SSH keys tab of the "account settings page":https://github.com/account
 
 
$ ssh git@github.com
-Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access.
-Connection to github.com closed.

-
-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
+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)? yes
+Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
+ERROR: Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access
+Connection to github.com closed.
+

+
+If you do not get the "successfully authenticated" message, check out the "troubleshooting guide":http://github.com/guides/addressing-authentication-problems-with-ssh.
diff --git a/_posts/2009-06-15-msysgit-key-setup.textile b/_posts/2009-06-15-msysgit-key-setup.textile
index fc9f320..bf93f81 100644
--- a/_posts/2009-06-15-msysgit-key-setup.textile
+++ b/_posts/2009-06-15-msysgit-key-setup.textile
@@ -15,13 +15,12 @@ h2. Backup and remove existing keys
 Unless this is your first time installing msys on your computer, you should double check 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.
 
 First check to see if a ssh key directory exists.
-
$ $ cd ~/.ssh
-

 
-If you get a "No such file or directory" error, you can skip the following step to back up the SSH key before generating a new keypair.
+
$ cd ~/.ssh

+
+If you get a "No such file or directory" error, you can skip to "Generating a key".
 
-
$ cd ~/.ssh
-$ ls
+
$ ls
 config  id_rsa  id_rsa.pub  known_hosts
 $ mkdir key_backup
 $ cp id_rsa* key_backup
@@ -57,20 +56,15 @@ Make sure you use the public key (@id_rsa.pub@ in our example), and do not add a
 
 h2. Testing things out
 
-Testing if our new key works is simple:
+Testing if our new key works is simple, we just ssh to github.  If this is the first time you're connecting you'll have to save the server's key.  You can confirm the fingerprint on the SSH keys tab of the "account settings page":https://github.com/account
 
 
$ ssh git@github.com
 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)?
-

-
-Respond with yes to confirm the first-time ssh connection to github:
-
yes
+Are you sure you want to continue connecting (yes/no)? yes
 Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
-Enter passphrase for key '/c/Users/tekkub/.ssh/id_rsa':
 ERROR: Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access
 Connection to github.com closed.
 

 
-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
+If you do not get the "successfully authenticated" message, check out the "troubleshooting guide":http://github.com/guides/addressing-authentication-problems-with-ssh.
-- 
cgit v1.3.1