From 3a592ce3fcb350904d614baf90bc851c21dc805d Mon Sep 17 00:00:00 2001 From: tekkub Date: Wed, 2 Mar 2011 00:19:37 -0700 Subject: Add quasi-redirects from the old guides --- .../2009-06-13-git-installation-redirect.markdown | 15 ++-- _posts/2009-06-14-linux-git-installation.markdown | 85 +-------------------- _posts/2009-06-14-mac-git-installation.markdown | 34 +-------- _posts/2009-06-14-win-git-installation.markdown | 22 +----- _posts/2009-06-15-key-setup-redirect.markdown | 18 +++++ _posts/2009-06-15-key-setup-redirect.textile | 19 ----- _posts/2009-06-15-linux-key-setup.markdown | 78 ++++++++++++++++++++ _posts/2009-06-15-linux-key-setup.textile | 78 -------------------- _posts/2009-06-15-mac-key-setup.markdown | 86 ++++++++++++++++++++++ _posts/2009-06-15-mac-key-setup.textile | 86 ---------------------- _posts/2009-06-15-msysgit-key-setup.markdown | 11 +++ _posts/2009-06-15-msysgit-key-setup.textile | 70 ------------------ 12 files changed, 212 insertions(+), 390 deletions(-) create mode 100644 _posts/2009-06-15-key-setup-redirect.markdown delete mode 100644 _posts/2009-06-15-key-setup-redirect.textile create mode 100644 _posts/2009-06-15-linux-key-setup.markdown delete mode 100644 _posts/2009-06-15-linux-key-setup.textile create mode 100644 _posts/2009-06-15-mac-key-setup.markdown delete mode 100644 _posts/2009-06-15-mac-key-setup.textile create mode 100644 _posts/2009-06-15-msysgit-key-setup.markdown delete mode 100644 _posts/2009-06-15-msysgit-key-setup.textile (limited to '_posts') diff --git a/_posts/2009-06-13-git-installation-redirect.markdown b/_posts/2009-06-13-git-installation-redirect.markdown index 1589bdb..3040d7f 100644 --- a/_posts/2009-06-13-git-installation-redirect.markdown +++ b/_posts/2009-06-13-git-installation-redirect.markdown @@ -2,17 +2,16 @@ layout: default title: Installing git description: How to install git -categories: setup --- Attempting to redirect to the guide for your OS. If the redirect fails, pick your OS: -* [Windows](win-git-installation) -* [Mac](mac-git-installation) -* [Linux](linux-git-installation) +* [Windows](win-set-up-git) +* [Mac](mac-set-up-git) +* [Linux](linux-set-up-git) \ No newline at end of file + if (navigator.appVersion.indexOf("Win") != -1) {window.location = '/win-set-up-git'} + else if (navigator.appVersion.indexOf("Mac") != -1) {window.location = '/mac-set-up-git'} + else if (navigator.appVersion.indexOf("X11") != -1 || navigator.appVersion.indexOf("Linux") != -1) {window.location = '/linux-set-up-git'} + diff --git a/_posts/2009-06-14-linux-git-installation.markdown b/_posts/2009-06-14-linux-git-installation.markdown index f2eabe8..97f5af4 100644 --- a/_posts/2009-06-14-linux-git-installation.markdown +++ b/_posts/2009-06-14-linux-git-installation.markdown @@ -2,87 +2,10 @@ layout: default title: Installing git (Linux) description: How to install git on Linux -categories: linux -main_category: setup --- -Ubuntu ------- +This page has moved. If the redirect fails, [click me](linux-set-up-git) -Git can be installed on ubuntu from the default package repositories using synaptic or apt-get. It is suggested you install git-core, git-gui, and git-doc. If you are moving from svn you may want to install git-svn as well. - -After you have completed installation you will need to [generate an SSH keypair](/linux-key-setup) and [set your local git config](/git-email-settings). - -### Synaptic (GUI) - -Launch Synaptic: - -![launch](http://img.skitch.com/20100224-b2qe2x24fke3y9y4s3tmb2mhjb.jpg) - -Select the packages you wish to install. - -![pick packs](http://img.skitch.com/20100224-cfpf7ki753fdw9tf89a7grgb1g.jpg) - -Click apply to install: - -![apply](http://img.skitch.com/20100224-82sg5b1pje12sjr3d8tkntmpmd.jpg) - -### apt-get (command line) - -
$ sudo apt-get install git-core git-gui git-doc
-Reading package lists... Done
-Building dependency tree
-Reading state information... Done
-The following packages were automatically installed and are no longer required:
-  linux-headers-2.6.28-11 linux-headers-2.6.28-11-generic
-Use 'apt-get autoremove' to remove them.
-The following extra packages will be installed:
-  gitk tcl tcl8.4 tk tk8.4
-Suggested packages:
-  git-arch git-cvs git-svn git-email git-daemon-run gitweb tclreadline
-The following NEW packages will be installed:
-  git-core git-doc git-gui gitk tcl tcl8.4 tk tk8.4
-0 upgraded, 8 newly installed, 0 to remove and 112 not upgraded.
-Need to get 4074kB/8396kB of archives.
-After this operation, 22.7MB of additional disk space will be used.
-Do you want to continue [Y/n]? y
-Get:1 http://us.archive.ubuntu.com jaunty/main git-doc 1:1.6.0.4-1ubuntu2 [1126kB]
-Get:2 http://us.archive.ubuntu.com jaunty/main tcl8.4 8.4.19-2 [1178kB]
-Get:3 http://us.archive.ubuntu.com jaunty/main tcl 8.4.16-2 [4154B]
-Get:4 http://us.archive.ubuntu.com jaunty/main tk8.4 8.4.19-2 [1019kB]
-Get:5 http://us.archive.ubuntu.com jaunty/main tk 8.4.16-2 [4184B]
-Get:6 http://us.archive.ubuntu.com jaunty/universe git-gui 1:1.6.0.4-1ubuntu2 [425kB]
-Get:7 http://us.archive.ubuntu.com jaunty/main gitk 1:1.6.0.4-1ubuntu2 [318kB]
-Fetched 4074kB in 1min 12s (56.6kB/s)
-Selecting previously deselected package git-core.
-(Reading database ... 121308 files and directories currently installed.)
-Unpacking git-core (from .../git-core_1%3a1.6.0.4-1ubuntu2_i386.deb) ...
-Selecting previously deselected package git-doc.
-Unpacking git-doc (from .../git-doc_1%3a1.6.0.4-1ubuntu2_all.deb) ...
-Selecting previously deselected package tcl8.4.
-Unpacking tcl8.4 (from .../tcl8.4_8.4.19-2_i386.deb) ...
-Selecting previously deselected package tcl.
-Unpacking tcl (from .../archives/tcl_8.4.16-2_all.deb) ...
-Selecting previously deselected package tk8.4.
-Unpacking tk8.4 (from .../tk8.4_8.4.19-2_i386.deb) ...
-Selecting previously deselected package tk.
-Unpacking tk (from .../archives/tk_8.4.16-2_all.deb) ...
-Selecting previously deselected package git-gui.
-Unpacking git-gui (from .../git-gui_1%3a1.6.0.4-1ubuntu2_all.deb) ...
-Selecting previously deselected package gitk.
-Unpacking gitk (from .../gitk_1%3a1.6.0.4-1ubuntu2_all.deb) ...
-Processing triggers for man-db ...
-Setting up git-core (1:1.6.0.4-1ubuntu2) ...
-Setting up git-doc (1:1.6.0.4-1ubuntu2) ...
-Setting up tcl8.4 (8.4.19-2) ...
-
-Setting up tcl (8.4.16-2) ...
-
-Setting up tk8.4 (8.4.19-2) ...
-
-Setting up tk (8.4.16-2) ...
-
-Setting up git-gui (1:1.6.0.4-1ubuntu2) ...
-Setting up gitk (1:1.6.0.4-1ubuntu2) ...
-Processing triggers for libc6 ...
-ldconfig deferred processing now taking place
+ diff --git a/_posts/2009-06-14-mac-git-installation.markdown b/_posts/2009-06-14-mac-git-installation.markdown index 853929d..a63a7c8 100644 --- a/_posts/2009-06-14-mac-git-installation.markdown +++ b/_posts/2009-06-14-mac-git-installation.markdown @@ -2,36 +2,10 @@ layout: default title: Installing git (OSX) description: How to install git on OSX -categories: mac -main_category: setup --- -There are a number of methods to install git on OSX. This guide details the most common methods, in order of ease of install. +This page has moved. If the redirect fails, [click me](mac-set-up-git) -After you have completed installation you will need to [generate an SSH keypair](/mac-key-setup) and [set your local git config](/git-email-settings). - -Pre-compiled Installer ----------------------- - -Download and run [git-osx-installer](http://code.google.com/p/git-osx-installer/) - -Homebrew --------- - -Install [Homebrew](http://github.com/mxcl/homebrew) if you haven't already done so. - -Install Git *(You may want to include Subversion support if you want to import SVN repositories. Snow Leopard already contains a copy of SVN)* - - $ brew install git - ==> Downloading http://kernel.org/pub/software/scm/git/git-1.6.5.7.tar.bz2 - ######################################################################## 100.0% - ==> ./configure --prefix=/usr/local/Cellar/git/1.6.5.7 - ==> make install - ==> Downloading http://kernel.org/pub/software/scm/git/git-manpages-1.6.5.7.tar.bz2 - ######################################################################## 100.0% - /usr/local/Cellar/git/1.6.5.7: 383 files, 16M, built in 74 seconds - -Compiling git manually ----------------------- - -See [this guide](http://gist.github.com/423308). + diff --git a/_posts/2009-06-14-win-git-installation.markdown b/_posts/2009-06-14-win-git-installation.markdown index 7d9c87a..4e618f4 100644 --- a/_posts/2009-06-14-win-git-installation.markdown +++ b/_posts/2009-06-14-win-git-installation.markdown @@ -2,24 +2,10 @@ layout: default title: Installing git (Win/msysgit) description: How to install git on Windows -categories: windows -main_category: setup --- -Installing git on windows is a fairly straightforward process. To begin, download the latest version of [msysgit](http://code.google.com/p/msysgit/). +This page has moved. If the redirect fails, [click me](win-set-up-git) -_This guide was written with Git-1.6.5.1-preview20091022.exe, newer versions may differ._ - -For each step we will use the default options. It is advisable that you do not use PuTTY if the installer gives you that option. GitHub only provides support for openssh. - -After you have completed installation you will need to [generate an SSH keypair](/msysgit-key-setup) and [set your local git config](/git-email-settings). - -![Welcome](http://img.skitch.com/20100125-fndn896jf6rfj5cs6nfhj9bxiq.jpg) -![License](http://img.skitch.com/20100125-dmx43twyjrrksdmn76pcj3prdi.jpg) -![Path](http://img.skitch.com/20100125-tepu9jhdnq5yh5a5ecdrtwxibm.jpg) -![Start menu](http://img.skitch.com/20100125-ju7te2wr8hus7u7c1beghxpd9h.jpg) -![Shortcuts](http://img.skitch.com/20100125-g5rpq18d1jryg2bhg72urypd2j.jpg) -![PATH](http://img.skitch.com/20100125-d3urje18fhhf5b99st6yyypp6w.jpg) -![CRLF](http://img.skitch.com/20100125-k3g1yeru3af1u31r5bu9b5t7xt.jpg) -![Installin'](http://img.skitch.com/20100125-knmcqg7d9dqsxbk13iityyrxji.jpg) -![Finished](http://img.skitch.com/20100125-q1tjy72n1tk1c191fdfp9jkspg.jpg) \ No newline at end of file + diff --git a/_posts/2009-06-15-key-setup-redirect.markdown b/_posts/2009-06-15-key-setup-redirect.markdown new file mode 100644 index 0000000..45e7327 --- /dev/null +++ b/_posts/2009-06-15-key-setup-redirect.markdown @@ -0,0 +1,18 @@ +--- +layout: default +title: Generating SSH keys +description: How to generate SSH keys and add them to GitHub +--- + +Attempting to redirect to the guide for your OS. If the redirect fails, pick your OS: + +* [Windows](win-set-up-git) +* [Mac](mac-set-up-git) +* [Linux](linux-set-up-git) + + +> \ No newline at end of file diff --git a/_posts/2009-06-15-key-setup-redirect.textile b/_posts/2009-06-15-key-setup-redirect.textile deleted file mode 100644 index 29b7428..0000000 --- a/_posts/2009-06-15-key-setup-redirect.textile +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: default -title: Generating SSH keys -description: How to generate SSH keys and add them to GitHub -categories: setup popular -main_category: setup ---- - -Attempting to redirect to the guide for your OS. If the redirect fails, pick your OS: - -* "Windows":msysgit-key-setup -* "Mac":mac-key-setup -* "Linux":linux-key-setup - - \ No newline at end of file diff --git a/_posts/2009-06-15-linux-key-setup.markdown b/_posts/2009-06-15-linux-key-setup.markdown new file mode 100644 index 0000000..ba627f4 --- /dev/null +++ b/_posts/2009-06-15-linux-key-setup.markdown @@ -0,0 +1,78 @@ +--- +layout: default +title: Generating SSH keys (Linux) +description: Setting up SSH keys on Linux +categories: linux +main_category: setup +--- + +This guide will step you through the process of generating a keypair on linux and uploading it to GitHub. We use Ubuntu and bash in this guide, command may vary depending on your linux flavor and shell. + +Generating an SSH key on linux is a fairly straightforward process. First and foremost, open up a "terminal":https://help.ubuntu.com/community/UsingTheTerminal. + +h2. Backup and remove existing keys + +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. + +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
+$ cp id_rsa* key_backup
+$ rm id_rsa*
+ +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@. + +h2. Generating a key + +p(. _If you have an existing keypair you wish to use, you can skip this step._ + +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: + +
$ ssh-keygen -t rsa -C "tekkub@gmail.com"
+Generating public/private rsa key pair.
+Enter file in which to save the key (/home/tekkub/.ssh/id_rsa):
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /home/tekkub/.ssh/id_rsa.
+Your public key has been saved in /home/tekkub/.ssh/id_rsa.pub.
+The key fingerprint is:
+01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db tekkub@gmail.com
+ +At the first prompt you can just hit enter to generate the key with the default name. *You should use a good passphrase with your key.* See "Working with SSH key passphrases":/working-with-key-passphrases for more details on why you should use a passphrase and how to avoid re-entering it every time you use your key. + +p(. *Note:* If you don't use the default key names, or store your keys in a different path, you may need to run @ssh-add path/to/my_key@ so that ssh knows where to find your key. + +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 public key into the "key" field. If you leave the title blank the key comment (your email) will be used for the title. + +Make sure you use the public key (@id_rsa.pub@ in our example), and do not add any newlines or whitespace inside the key. To ensure you copy the key correctly, you can copy the key directly into the clipboard from the terminal using "xclip":http://www.cyberciti.biz/faq/xclip-linux-insert-files-command-output-intoclipboard/: + +
$ sudo apt-get install xclip
+$ cat ~/.ssh/id_rsa.pub | xclip -sel clip
+ +!/images/add_key.png! + +h2. Testing things out + +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)? 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-linux-key-setup.textile b/_posts/2009-06-15-linux-key-setup.textile deleted file mode 100644 index ba627f4..0000000 --- a/_posts/2009-06-15-linux-key-setup.textile +++ /dev/null @@ -1,78 +0,0 @@ ---- -layout: default -title: Generating SSH keys (Linux) -description: Setting up SSH keys on Linux -categories: linux -main_category: setup ---- - -This guide will step you through the process of generating a keypair on linux and uploading it to GitHub. We use Ubuntu and bash in this guide, command may vary depending on your linux flavor and shell. - -Generating an SSH key on linux is a fairly straightforward process. First and foremost, open up a "terminal":https://help.ubuntu.com/community/UsingTheTerminal. - -h2. Backup and remove existing keys - -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. - -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
-$ cp id_rsa* key_backup
-$ rm id_rsa*
- -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@. - -h2. Generating a key - -p(. _If you have an existing keypair you wish to use, you can skip this step._ - -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: - -
$ ssh-keygen -t rsa -C "tekkub@gmail.com"
-Generating public/private rsa key pair.
-Enter file in which to save the key (/home/tekkub/.ssh/id_rsa):
-Enter passphrase (empty for no passphrase):
-Enter same passphrase again:
-Your identification has been saved in /home/tekkub/.ssh/id_rsa.
-Your public key has been saved in /home/tekkub/.ssh/id_rsa.pub.
-The key fingerprint is:
-01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db tekkub@gmail.com
- -At the first prompt you can just hit enter to generate the key with the default name. *You should use a good passphrase with your key.* See "Working with SSH key passphrases":/working-with-key-passphrases for more details on why you should use a passphrase and how to avoid re-entering it every time you use your key. - -p(. *Note:* If you don't use the default key names, or store your keys in a different path, you may need to run @ssh-add path/to/my_key@ so that ssh knows where to find your key. - -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 public key into the "key" field. If you leave the title blank the key comment (your email) will be used for the title. - -Make sure you use the public key (@id_rsa.pub@ in our example), and do not add any newlines or whitespace inside the key. To ensure you copy the key correctly, you can copy the key directly into the clipboard from the terminal using "xclip":http://www.cyberciti.biz/faq/xclip-linux-insert-files-command-output-intoclipboard/: - -
$ sudo apt-get install xclip
-$ cat ~/.ssh/id_rsa.pub | xclip -sel clip
- -!/images/add_key.png! - -h2. Testing things out - -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)? 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.markdown b/_posts/2009-06-15-mac-key-setup.markdown new file mode 100644 index 0000000..100e9b1 --- /dev/null +++ b/_posts/2009-06-15-mac-key-setup.markdown @@ -0,0 +1,86 @@ +--- +layout: default +title: Generating SSH keys (OSX) +description: Setting up SSH keys on Mac OSX +categories: mac +main_category: setup +--- + +This guide will step you through the process of generating a keypair on Mac OSX and uploading it to GitHub + +Generating an SSH key on OSX is a fairly straightforward process. First and foremost, open up Terminal.app. You can usually find it at @/Applications/Utilities@. + +h2. Backup and remove existing keys + +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. + +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
+$ rm id_rsa*
+ +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@. + +h2. Generating a key + +p(. _If you have an existing keypair you wish to use, you can skip this step._ + +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: + +
$ ssh-keygen -t rsa -C "tekkub@gmail.com"
+Generating public/private rsa key pair.
+Enter file in which to save the key (/Users/tekkub/.ssh/id_rsa):
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /Users/tekkub/.ssh/id_rsa.
+Your public key has been saved in /Users/tekkub/.ssh/id_rsa.pub.
+The key fingerprint is:
+01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db tekkub@gmail.com
+The key's randomart image is:
++--[ RSA 2048]----+
+|     .+   +      |
+|       = o O .   |
+|        = * *    |
+|       o = +     |
+|      o S .      |
+|     o o =       |
+|      o . E      |
+|                 |
+|                 |
++-----------------+
+ +At the first prompt you can just hit enter to generate the key with the default name. *You should use a good passphrase with your key.* See "Working with SSH key passphrases":/working-with-key-passphrases for more details on why you should use a passphrase and how to avoid re-entering it every time you use your key. + +p(. *Note:* If you don't use the default key names, or store your keys in a different path, you will need to run @ssh-add path/to/my_key@ so that ssh knows where to find your key. + +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 public key into the "key" field. If you leave the title blank the key comment (your email) will be used for the title. + +Make sure you use the public key (@id_rsa.pub@ in our example), and do not add any newlines or whitespace inside the key. To ensure you copy the key correctly, you can copy the key directly into the clipboard from Terminal.app: 
$ cat ~/.ssh/id_rsa.pub | pbcopy
+ +!/images/add_key.png! + +h2. Testing things out + +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)? 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 deleted file mode 100644 index 100e9b1..0000000 --- a/_posts/2009-06-15-mac-key-setup.textile +++ /dev/null @@ -1,86 +0,0 @@ ---- -layout: default -title: Generating SSH keys (OSX) -description: Setting up SSH keys on Mac OSX -categories: mac -main_category: setup ---- - -This guide will step you through the process of generating a keypair on Mac OSX and uploading it to GitHub - -Generating an SSH key on OSX is a fairly straightforward process. First and foremost, open up Terminal.app. You can usually find it at @/Applications/Utilities@. - -h2. Backup and remove existing keys - -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. - -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
-$ rm id_rsa*
- -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@. - -h2. Generating a key - -p(. _If you have an existing keypair you wish to use, you can skip this step._ - -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: - -
$ ssh-keygen -t rsa -C "tekkub@gmail.com"
-Generating public/private rsa key pair.
-Enter file in which to save the key (/Users/tekkub/.ssh/id_rsa):
-Enter passphrase (empty for no passphrase):
-Enter same passphrase again:
-Your identification has been saved in /Users/tekkub/.ssh/id_rsa.
-Your public key has been saved in /Users/tekkub/.ssh/id_rsa.pub.
-The key fingerprint is:
-01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db tekkub@gmail.com
-The key's randomart image is:
-+--[ RSA 2048]----+
-|     .+   +      |
-|       = o O .   |
-|        = * *    |
-|       o = +     |
-|      o S .      |
-|     o o =       |
-|      o . E      |
-|                 |
-|                 |
-+-----------------+
- -At the first prompt you can just hit enter to generate the key with the default name. *You should use a good passphrase with your key.* See "Working with SSH key passphrases":/working-with-key-passphrases for more details on why you should use a passphrase and how to avoid re-entering it every time you use your key. - -p(. *Note:* If you don't use the default key names, or store your keys in a different path, you will need to run @ssh-add path/to/my_key@ so that ssh knows where to find your key. - -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 public key into the "key" field. If you leave the title blank the key comment (your email) will be used for the title. - -Make sure you use the public key (@id_rsa.pub@ in our example), and do not add any newlines or whitespace inside the key. To ensure you copy the key correctly, you can copy the key directly into the clipboard from Terminal.app: 
$ cat ~/.ssh/id_rsa.pub | pbcopy
- -!/images/add_key.png! - -h2. Testing things out - -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)? 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.markdown b/_posts/2009-06-15-msysgit-key-setup.markdown new file mode 100644 index 0000000..70f340f --- /dev/null +++ b/_posts/2009-06-15-msysgit-key-setup.markdown @@ -0,0 +1,11 @@ +--- +layout: default +title: Generating SSH keys (Win/msysgit) +description: Setting up SSH keys with msysgit on Windows +--- + +This page has moved. If the redirect fails, [click me](win-set-up-git) + + diff --git a/_posts/2009-06-15-msysgit-key-setup.textile b/_posts/2009-06-15-msysgit-key-setup.textile deleted file mode 100644 index 45efa09..0000000 --- a/_posts/2009-06-15-msysgit-key-setup.textile +++ /dev/null @@ -1,70 +0,0 @@ ---- -layout: default -title: Generating SSH keys (Win/msysgit) -description: Setting up SSH keys with msysgit on Windows -categories: windows -main_category: setup ---- - -This guide will step you through the process of generating a keypair in msysgit and uploading it to GitHub - -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. - -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 to "Generating a key". - -
$ ls
-config  id_rsa  id_rsa.pub  known_hosts
-$ mkdir key_backup
-$ cp id_rsa* key_backup
-$ rm id_rsa*
- -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@. - -h2. Generating a key - -p(. _If you have an existing keypair you wish to use, you can skip this step._ - -Now that we're certain ssh won't use an existing key, it's time to generate a new keypair. Let's make an RSA keypair: - -
$ 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
- -At the first prompt you can just hit enter to generate the key with the default name. *You should use a good passphrase with your key.* See "Working with SSH key passphrases":/working-with-key-passphrases for more details on why you should use a passphrase and how to avoid re-entering it every time you use your key. - -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. - -Make sure you use the public key (@id_rsa.pub@ in our example), and do not add any newlines or whitespace inside the key. - -!/images/add_key.png! - -h2. Testing things out - -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)? 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. -- cgit v1.3.1