CARVIEW |
Select Language
HTTP/2 302
server: nginx
date: Wed, 23 Jul 2025 08:20:24 GMT
content-type: text/plain; charset=utf-8
content-length: 0
x-archive-redirect-reason: found capture at 20090217103234
location: https://web.archive.org/web/20090217103234/https://github.com/guides/providing-your-ssh-key.atom
server-timing: captures_list;dur=1.023846, exclusion.robots;dur=0.034459, exclusion.robots.policy;dur=0.015436, esindex;dur=0.019999, cdx.remote;dur=150.548458, LoadShardBlock;dur=155.913272, PetaboxLoader3.datanode;dur=96.184847
x-app-server: wwwb-app204
x-ts: 302
x-tr: 414
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=1
set-cookie: SERVER=wwwb-app204; path=/
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
HTTP/2 200
server: nginx
date: Wed, 23 Jul 2025 08:20:25 GMT
content-type: application/atom+xml; charset=utf-8
content-length: 594099
x-archive-orig-server: nginx/0.6.31
x-archive-orig-date: Tue, 17 Feb 2009 10:32:33 GMT
x-archive-orig-connection: close
x-archive-orig-status: 200 OK
x-archive-orig-x-runtime: 2070ms
x-archive-orig-etag: "03c450510cc3696f3945cd56714a6537"
x-archive-orig-cache-control: private, max-age=0, must-revalidate
x-archive-orig-content-length: 594099
cache-control: max-age=1800
x-archive-guessed-content-type: text/xml
x-archive-guessed-charset: utf-8
memento-datetime: Tue, 17 Feb 2009 10:32:34 GMT
link: ; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Thu, 18 Sep 2008 23:33:28 GMT", ; rel="prev memento"; datetime="Thu, 18 Dec 2008 07:00:50 GMT", ; rel="memento"; datetime="Tue, 17 Feb 2009 10:32:34 GMT", ; rel="next memento"; datetime="Sun, 19 Apr 2009 05:53:22 GMT", ; rel="last memento"; datetime="Sun, 19 Apr 2009 05:53:22 GMT"
content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org
x-archive-src: 52_8_20090217081833_crawl102-c/52_8_20090217103058_crawl101.arc.gz
server-timing: captures_list;dur=0.807097, exclusion.robots;dur=0.049262, exclusion.robots.policy;dur=0.034536, esindex;dur=0.017112, cdx.remote;dur=25.351964, LoadShardBlock;dur=435.209165, PetaboxLoader3.datanode;dur=368.186053, PetaboxLoader3.resolve;dur=268.678619, load_resource;dur=224.846094
x-app-server: wwwb-app204
x-ts: 200
x-tr: 740
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=1
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
accept-ranges: bytes
tag:github.com,2008:/guides/providing-your-ssh-key
GitHub Guides - Providing your SSH Key
2009-01-27T20:57:28-08:00
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-27T20:57:28-08:00
Providing your SSH Key - version 70
Tue Jan 27 20:57:28 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! This text entry box can be found after logging in by clicking <a href="https://github.com/account">Account</a> in the top right and looking under “SSH Public Keys”.</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! “</p>
thynctank
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-27T20:56:25-08:00
Providing your SSH Key - version 69
Tue Jan 27 20:56:25 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! (this text entry box can be found after logging in by clicking <a href="https://github.com/account">Account</a> in the top right and looking under “SSH Public Keys”.</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! “</p>
thynctank
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-27T20:54:47-08:00
Providing your SSH Key - version 68
Tue Jan 27 20:54:47 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! (this text entry box can be found after logging in by clicking <span style="color:#aaa">/account</span><a href="/guides/new?title=%2Faccount">?</a> and looking under “SSH Public Keys”.</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! “</p>
thynctank
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T11:27:24-08:00
Providing your SSH Key - version 67
Tue Jan 20 11:27:24 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! “</p>
eric
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T10:49:53-08:00
Providing your SSH Key - version 66
Tue Jan 20 10:49:53 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config\t\tid_rsa.pub
id_rsa\t\tknown_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config\t\tid_rsa.pub
id_rsa\t\tknown_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! “</p>
defunkt
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T10:49:44-08:00
Providing your SSH Key - version 65
Tue Jan 20 10:49:44 -0800 2009
<blockquote>
<blockquote>
<p>g.model.body(:source)
=> “h2. Overview</p>
</blockquote>
</blockquote>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config\t\tid_rsa.pub
id_rsa\t\tknown_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config\t\tid_rsa.pub
id_rsa\t\tknown_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! ”
>></p>
defunkt
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T10:47:34-08:00
Providing your SSH Key - version 64
Tue Jan 20 10:47:34 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps"><span class="caps">SSH</span></span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps"><span class="caps">SSH</span></span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps"><span class="caps">SSH</span></span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps"><span class="caps">OS X</span></span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps"><span class="caps">OS X</span></span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command">&lt;enter&gt;</span>
Enter passphrase (empty for no passphrase): <span class="command">&lt;enter passphrase or hit enter&gt;</span>
Enter same passphrase again: <span class="command">&lt;enter passphrase again&gt;</span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps"><span class="caps">STDIN</span></span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi <sub>/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command">&lt;enter&gt;</span>
Enter passphrase (empty for no passphrase): <span class="command">&lt;enter passphrase or hit enter&gt;</span>
Enter same passphrase again: <span class="command">&lt;enter passphrase again&gt;</span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps"><span class="caps">STDIN</span></span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps"><span class="caps">GUI</span></span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/</sub>sgtatham/putty/download.html”>PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
defunkt
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T10:47:15-08:00
Providing your SSH Key - version 63
Tue Jan 20 10:47:15 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href=\"https://en.wikipedia.org/wiki/Public-key_cryptography\">public-key cryptography</a> and <a href=\"https://en.wikipedia.org/wiki/SSH\"><span class=\"caps\"><span class="caps">SSH</span></span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class=\"caps\"><span class="caps">SSH</span></span> public key. The rest of this page contains instructions on how to locate or create a set of <span class=\"caps\"><span class="caps">SSH</span></span> keys.</p>
<ul>
<li><a href=\"#macosx\">Mac <span class=\"caps\"><span class="caps">OS X</span></span></a></li>
<li><a href=\"#linux\">Linux</a></li>
<li><a href=\"#msysGit\">Windows using msysGit</a></li>
<li><a href=\"#windowsxp\">Windows using PuTTYgen</a></li>
</ul>
<h2 id=\"macosx\">Mac <span class=\"caps\"><span class="caps">OS X</span></span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class=\"console\"><code><span>[~]</span>$ <span class=\"command\">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class=\"command\">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href=\"#macosx-3\">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class=\"console\"><code><span>[~/.ssh]</span>$ <span class=\"command\">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class=\"command\">&lt;enter&gt;</span>
Enter passphrase (empty for no passphrase): <span class=\"command\">&lt;enter passphrase or hit enter&gt;</span>
Enter same passphrase again: <span class=\"command\">&lt;enter passphrase again&gt;</span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id=\"macosx-3\">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class=\"console\"><code><span>[~/.ssh]</span>$ <span class=\"command\">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class=\"caps\"><span class="caps">STDIN</span></span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href=\"https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html\">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi <sub>/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class=\"console\"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id=\"linux\">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class=\"console\"><code><span>[~]</span>$ <span class=\"command\">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class=\"command\">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href=\"#linux-3\">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class=\"console\"><code><span>[~/.ssh]</span>$ <span class=\"command\">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class=\"command\">&lt;enter&gt;</span>
Enter passphrase (empty for no passphrase): <span class=\"command\">&lt;enter passphrase or hit enter&gt;</span>
Enter same passphrase again: <span class=\"command\">&lt;enter passphrase again&gt;</span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id=\"linux-3\">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class=\"console\"><code><span>[~/.ssh]</span>$ <span class=\"command\">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class=\"caps\"><span class="caps">STDIN</span></span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class=\"console\"><code><span>[~/.ssh]</span>$ <span class=\"command\">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id=\"msysGit\">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href=\"https://code.google.com/p/msysgit/downloads/list\">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class=\"console\"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\\Documents and Settings\\Username\\.ssh</code> on XP or <code>c:\\Users\\Username\\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class=\"caps\"><span class="caps">GUI</span></span> that all come part of msysGit..</p>
<h2 id=\"windowsxp\">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href=\"https://www.chiark.greenend.org.uk/</sub>sgtatham/putty/download.html\”>PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href=\"https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html\">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
defunkt
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T09:39:31-08:00
Providing your SSH Key - version 62
Tue Jan 20 09:39:31 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAsQ/Nk763jKaRqn35Fxcit2Zuvt3ut9Defp5J7+K7SHxrHwoH/5h7golq+vf8VhPkOBVdV6DbAV7mx0ycDSOn7L95y9uGyRFAeZ0fFG0PIEQ30e/a22rVh4yFrqkfqCt00lhGPEep7yKHpx6VLOEkYegrVbzl8Gv7ysCRQNHvfSPE12P40AbWKKKIl2wVPO04LyacBf0nh3VMuT39KdteeBttix8XZDXscSv9+F4RYwaH8P3lrnt7×1oGPOIb1tKnc7z6xKJn/CFHZcZyly9cOp0nQH2A07HNt8sk1FBwtD1Hk3bqBghSt2xXoBPzHunH1vxEJ55PtK6LiivK9ph1Yw== maghroum_hassen@hotmail.com</p>
Goldrojer
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T02:13:52-08:00
Providing your SSH Key - version 61
Tue Jan 20 02:13:52 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAsQ/Nk763jKaRqn35Fxcit2Zuvt3ut9Defp5J7+K7SHxrHwoH/5h7golq+vf8VhPkOBVdV6DbAV7mx0ycDSOn7L95y9uGyRFAeZ0fFG0PIEQ30e/a22rVh4yFrqkfqCt00lhGPEep7yKHpx6VLOEkYegrVbzl8Gv7ysCRQNHvfSPE12P40AbWKKKIl2wVPO04LyacBf0nh3VMuT39KdteeBttix8XZDXscSv9+F4RYwaH8P3lrnt7×1oGPOIb1tKnc7z6xKJn/CFHZcZyly9cOp0nQH2A07HNt8sk1FBwtD1Hk3bqBghSt2xXoBPzHunH1vxEJ55PtK6LiivK9ph1Yw== toto@gmail.com</p>
ahsx
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T02:13:22-08:00
Providing your SSH Key - version 60
Tue Jan 20 02:13:22 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAsQ/Nk763jKaRqn35Fxcit2Zuvt3ut9Defp5J7+K7SHxrHwoH/5h7golq+vf8VhPkOBVdV6DbAV7mx0ycDSOn7L95y9uGyRFAeZ0fFG0PIEQ30e/a22rVh4yFrqkfqCt00lhGPEep7yKHpx6VLOEkYegrVbzl8Gv7ysCRQNHvfSPE12P40AbWKKKIl2wVPO04LyacBf0nh3VMuT39KdteeBttix8XZDXscSv9+F4RYwaH8P3lrnt7×1oGPOIb1tKnc7z6xKJn/CFHZcZyly9cOp0nQH2A07HNt8sk1FBwtD1Hk3bqBghSt2xXoBPzHunH1vxEJ55PtK6LiivK9ph1Yw== ahsx@ahsx.be</p>
ahsx
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T01:40:39-08:00
Providing your SSH Key - version 59
Tue Jan 20 01:40:39 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAsQ/Nk763jKaRqn35Fxcit2Zuvt3ut9Defp5J7+K7SHxrHwoH/5h7golq+vf8VhPkOBVdV6DbAV7mx0ycDSOn7L95y9uGyRFAeZ0fFG0PIEQ30e/a22rVh4yFrqkfqCt00lhGPEep7yKHpx6VLOEkYegrVbzl8Gv7ysCRQNHvfSPE12P40AbWKKKIl2wVPO04LyacBf0nh3VMuT39KdteeBttix8XZDXscSv9+F4RYwaH8P3lrnt7×1oGPOIb1tKnc7z6xKJn/CFHZcZyly9cOp0nQH2A07HNt8sk1FBwtD1Hk3bqBghSt2xXoBPzHunH1vxEJ55PtK6LiivK9ph1Yw== tujiao.com@gmail.com</p>
tujiao
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T01:29:47-08:00
Providing your SSH Key - version 58
Tue Jan 20 01:29:47 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA06h/xl9g7C5G/PDrwfB+qHzcAzl9I/RCQ5IjcCeCrQH6sB4St/Y0BZ3QdOxJhwg7/in35CVSqk6IPxbrYKMa3BrYZJ4mewNCphyOlIPqKubqH3L3aRHarZQSeEkCWSSEMgR/1BWy15poDCrf/WQLniwnBfug185AeuuayH4rBCl2hEF+vPVrtRpyrXtLq5AkSo25VX+FTKbvfSPVLcOH/D9egRgoEeVCHKBAf7/AQFxQA8KqHiBrW1+0kgmkNcMPqAggo4lb1ym1jKsRl+RsUqcPOAqQlbh5nhrhZ4nx4AlnB6nT0oTpWHzBgltjyFp+tAoQAQmu2PKb4kyYVAG5Rw== arden.emily@gmail.com</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T01:26:52-08:00
Providing your SSH Key - version 57
Tue Jan 20 01:26:52 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAz6MTJJAHMPZFtm5n+xV9t5JwTis82BKBt//kcqk3UzfXFwCOdb9utC02g8h7abdQXAtjhIfNhikL5L18C0kq3IeQpCVEx4ghXqbJQ1lXzuvEYWCI1Th5YpZQfTIcL/Ku+p6Iv68tCm2CEIFbjUBiKIn+KNl1BMBN/AzNd786/8rEFAgAh715R4xAkGx0n61PL/IfbZ2GeClznT9N14ANAVPIeOVjDDyuCv0+VPJAj8PDGN4Hpft6tEiZihT7vDHGFUqK9C7fInXbZlMNAC7u+J/i4Sq9Tr0u90xUhg5zjmq/Gyrk5UdDmRZ8NYx4WT0s3FfFG1×4hvG2qoKdYP5iKw== arden.emily@gmail.com</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T01:09:33-08:00
Providing your SSH Key - version 56
Tue Jan 20 01:09:33 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAzzwrqWvAyb8ACCS6MJD6A5lzvgJbo7hMci0firG/Xs9Ct9lm5LBEDZ1mL9ppllIhUms+KdKbakm9dRmDmGvRqihNf8Y3deBAVK+i5pSlL8YO+bLie+jxuD9WcJ9yXEWCkWOnEa2LYuui/9kCghbdF28EVVUMol5gvdsXj/SzwmtsqIALSqYDpsh4OSVl1vBSEUwyhZsgVmV0UYjgfNdcqKUvHPOCPe9vd9ZqWRLP30TpjCjege4YYL0FKuXj4wQNHUGdXzWqW+YT1NlwaDPiUBfMgHYlqwHvCMsiC1ZYc8hJypnrj1UeL7omqIbCO7T33R1fIgCblY33Pq+VIw1J7Q== arden.emily@gmail.com</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:50:22-08:00
Providing your SSH Key - version 55
Tue Jan 20 00:50:22 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAzzwrqWvAyb8ACCS6MJD6A5lzvgJbo7hMci0firG/Xs9Ct9lm5LBEDZ1mL9ppllIhUms+KdKbakm9dRmDmGvRqihNf8Y3deBAVK+i5pSlL8YO+bLie+jxuD9WcJ9yXEWCkWOnEa2LYuui/9kCghbdF28EVVUMol5gvdsXj/SzwmtsqIALSqYDpsh4OSVl1vBSEUwyhZsgVmV0UYjgfNdcqKUvHPOCPe9vd9ZqWRLP30TpjCjege4YYL0FKuXj4wQNHUGdXzWqW+YT1NlwaDPiUBfMgHYlqwHvCMsiC1ZYc8hJypnrj1UeL7omqIbCO7T33R1fIgCblY33Pq+VIw1J7Q== arden.emily@gmail.com</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:49:16-08:00
Providing your SSH Key - version 54
Tue Jan 20 00:49:16 -0800 2009
<p>Proc-Type: 4,ENCRYPTED
<span class="caps">DEK</span>-Info: <span class="caps">DES</span>-EDE3-CBC,BC32952D3B877A65</p>
<p>rqw71QKDIHl/gH8xfr85aec4SQladaXB30RZ+Qt3v4mqRbVUKdiuxL4KFH23kKQz
0WKVsQcWqOaFnwD+oZndxpleVYUH4jtWNP2PEfpkHSBi1xE1b/6GYGWpENs2jpnz
n5Qg6K3PCw8a/F3CsG5EBVEFagvaLXdlGZ5ASqJ7f/5UnNElVIv5vTlxQ/2KH1iZ
FmVO1W1rdrGN2XeHKHrAcPOBlpnuKPml4mCKBZ5LMksHY/aEfq70giYIECXvPmxB
Zu1HlVpmWNmKxZoMKsIbO/6eIjKAfhjmrC+S6obQvuEU2bbq2qJ5fPy8HUdQGUQX
4zTwZkpTSPMlkJmWORSLnBjFtcQUPLiWtt6qMtORs4SenTveWKHHIVCUhB18Txwe
HXIlizFrrTcaOxIS1FylNqTN8oGn72gqfyDi5+SGTcz6rMk7O/wqzGB9yGNHCbn9
59aSPd3JXvljZqwBq2yioqyUWDApJHNrV0J5+Tc3RZn7EHROQpcKxTrnn0MFumWZ
FMyeorkrdITn3ia7MW5CvY9+qAhaf5heZf3GXhnOOSGaspJxSVroes+x30xnkeG5
/GOnM0mOQmrE+ahI+4×1Snwmcr+YdO8MPbeMqNxpljSvtSU5aw/+QoqqmIUBmBC7
ZBwM3zv5QoIIUim/jhIPTuVwNKnN8b94KanbY1CDtHeVH6TUj0M2ro6AofSw8R/9
BAD9xI1BMLy2NZltIq86AD2b4rJBOGqMLDGPcl46GCraTwtN8u40le/yq6+xu27h
/hMQmM8JaAplL7Nd8hxrfW35BXunTMoFigKIxsgiugN/+L80kyKGS8FdyaDYN3m/
5XB91NpY0CZ4RjhkPSqS+wvmiVVaorZDb+DkkztOK+h4gNwyr7jdRp7CkVVNdGTe
qbq/mJ49e1HG0lDB/AK4fnm+E9yd8V/P7W9Rb/12TURqLYLw4OisbX4uk0nWR6hk
uXryo3jz0hqu28R50BcN03uB2pD0OSSmFRoUxi7fwVweGjJIHJWi9yXVduQAuYyd
w9ZATvHfmn0TcAp5VPVCjOAP+zsw/HhKkhlRpdLcd6LR7DIrKqeogZnfqA9Q+zDr
Wvn7jZ1zGfotQL8dUSNENkzjAdd3MmMzzsvM/PMi0B+ThRynSS7m81KZmPst5cn2
p/zMmidiKqmDbYxTFlFiSXrtZMIn/PQoADz9+LbMbhrAz0Rwha8aFONvyBEX+Zk+
nER4g/qd9wA2ogXEeyXjT5IsUDDsMSSa75HWsT7APnfczMypTjDs7z1KE4/jKpfG
zV1Pu1u4VM1vdiD8tduB/b+zW2AeBQmA77vFhtyRa0b5eZd1cjytM4QX6uHgMIyF
0PhnHnMB/EBD6bCDIoo7eB3H6HDbwYPw488H9WJexCa08FUQfPAYOceoNQq9pDlm
T9xzXxT/ctoht8vJYwwvhXsiByu4G7RIXr1WWpNdb5H7dl/i17tLr/d0kj6Z1Mb3
Pakvg15JceftS2E8GMHarpDGomnpomvZD1mgB6vlNzr4DtONpq+bq+bmV+FQa4rF
dxKJQcAJ0iHXvLWnniIY3T7KxWFz+V43L26PX3fg7Stzkje2AB4pvA==</p>
alagu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:37:53-08:00
Providing your SSH Key - version 53
Tue Jan 20 00:37:53 -0800 2009
<p>Proc-Type: 4,ENCRYPTED
<span class="caps">DEK</span>-Info: <span class="caps">DES</span>-EDE3-CBC,BC32952D3B877A65</p>
<p>rqw71QKDIHl/gH8xfr85aec4SQladaXB30RZ+Qt3v4mqRbVUKdiuxL4KFH23kKQz
0WKVsQcWqOaFnwD+oZndxpleVYUH4jtWNP2PEfpkHSBi1xE1b/6GYGWpENs2jpnz
n5Qg6K3PCw8a/F3CsG5EBVEFagvaLXdlGZ5ASqJ7f/5UnNElVIv5vTlxQ/2KH1iZ
FmVO1W1rdrGN2XeHKHrAcPOBlpnuKPml4mCKBZ5LMksHY/aEfq70giYIECXvPmxB
Zu1HlVpmWNmKxZoMKsIbO/6eIjKAfhjmrC+S6obQvuEU2bbq2qJ5fPy8HUdQGUQX
4zTwZkpTSPMlkJmWORSLnBjFtcQUPLiWtt6qMtORs4SenTveWKHHIVCUhB18Txwe
HXIlizFrrTcaOxIS1FylNqTN8oGn72gqfyDi5+SGTcz6rMk7O/wqzGB9yGNHCbn9
59aSPd3JXvljZqwBq2yioqyUWDApJHNrV0J5+Tc3RZn7EHROQpcKxTrnn0MFumWZ
FMyeorkrdITn3ia7MW5CvY9+qAhaf5heZf3GXhnOOSGaspJxSVroes+x30xnkeG5
/GOnM0mOQmrE+ahI+4×1Snwmcr+YdO8MPbeMqNxpljSvtSU5aw/+QoqqmIUBmBC7
ZBwM3zv5QoIIUim/jhIPTuVwNKnN8b94KanbY1CDtHeVH6TUj0M2ro6AofSw8R/9
BAD9xI1BMLy2NZltIq86AD2b4rJBOGqMLDGPcl46GCraTwtN8u40le/yq6+xu27h
/hMQmM8JaAplL7Nd8hxrfW35BXunTMoFigKIxsgiugN/+L80kyKGS8FdyaDYN3m/
5XB91NpY0CZ4RjhkPSqS+wvmiVVaorZDb+DkkztOK+h4gNwyr7jdRp7CkVVNdGTe
qbq/mJ49e1HG0lDB/AK4fnm+E9yd8V/P7W9Rb/12TURqLYLw4OisbX4uk0nWR6hk
uXryo3jz0hqu28R50BcN03uB2pD0OSSmFRoUxi7fwVweGjJIHJWi9yXVduQAuYyd
w9ZATvHfmn0TcAp5VPVCjOAP+zsw/HhKkhlRpdLcd6LR7DIrKqeogZnfqA9Q+zDr
Wvn7jZ1zGfotQL8dUSNENkzjAdd3MmMzzsvM/PMi0B+ThRynSS7m81KZmPst5cn2
p/zMmidiKqmDbYxTFlFiSXrtZMIn/PQoADz9+LbMbhrAz0Rwha8aFONvyBEX+Zk+
nER4g/qd9wA2ogXEeyXjT5IsUDDsMSSa75HWsT7APnfczMypTjDs7z1KE4/jKpfG
zV1Pu1u4VM1vdiD8tduB/b+zW2AeBQmA77vFhtyRa0b5eZd1cjytM4QX6uHgMIyF
0PhnHnMB/EBD6bCDIoo7eB3H6HDbwYPw488H9WJexCa08FUQfPAYOceoNQq9pDlm
T9xzXxT/ctoht8vJYwwvhXsiByu4G7RIXr1WWpNdb5H7dl/i17tLr/d0kj6Z1Mb3
Pakvg15JceftS2E8GMHarpDGomnpomvZD1mgB6vlNzr4DtONpq+bq+bmV+FQa4rF
dxKJQcAJ0iHXvLWnniIY3T7KxWFz+V43L26PX3fg7Stzkje2AB4pvA==</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:37:05-08:00
Providing your SSH Key - version 52
Tue Jan 20 00:37:05 -0800 2009
<p><del>—</del>-BEGIN <span class="caps">RSA PRIVATE KEY</span>-<del>—</del>
Proc-Type: 4,ENCRYPTED
<span class="caps">DEK</span>-Info: <span class="caps">DES</span>-EDE3-CBC,BC32952D3B877A65</p>
<p>rqw71QKDIHl/gH8xfr85aec4SQladaXB30RZ+Qt3v4mqRbVUKdiuxL4KFH23kKQz
0WKVsQcWqOaFnwD+oZndxpleVYUH4jtWNP2PEfpkHSBi1xE1b/6GYGWpENs2jpnz
n5Qg6K3PCw8a/F3CsG5EBVEFagvaLXdlGZ5ASqJ7f/5UnNElVIv5vTlxQ/2KH1iZ
FmVO1W1rdrGN2XeHKHrAcPOBlpnuKPml4mCKBZ5LMksHY/aEfq70giYIECXvPmxB
Zu1HlVpmWNmKxZoMKsIbO/6eIjKAfhjmrC+S6obQvuEU2bbq2qJ5fPy8HUdQGUQX
4zTwZkpTSPMlkJmWORSLnBjFtcQUPLiWtt6qMtORs4SenTveWKHHIVCUhB18Txwe
HXIlizFrrTcaOxIS1FylNqTN8oGn72gqfyDi5+SGTcz6rMk7O/wqzGB9yGNHCbn9
59aSPd3JXvljZqwBq2yioqyUWDApJHNrV0J5+Tc3RZn7EHROQpcKxTrnn0MFumWZ
FMyeorkrdITn3ia7MW5CvY9+qAhaf5heZf3GXhnOOSGaspJxSVroes+x30xnkeG5
/GOnM0mOQmrE+ahI+4×1Snwmcr+YdO8MPbeMqNxpljSvtSU5aw/+QoqqmIUBmBC7
ZBwM3zv5QoIIUim/jhIPTuVwNKnN8b94KanbY1CDtHeVH6TUj0M2ro6AofSw8R/9
BAD9xI1BMLy2NZltIq86AD2b4rJBOGqMLDGPcl46GCraTwtN8u40le/yq6+xu27h
/hMQmM8JaAplL7Nd8hxrfW35BXunTMoFigKIxsgiugN/+L80kyKGS8FdyaDYN3m/
5XB91NpY0CZ4RjhkPSqS+wvmiVVaorZDb+DkkztOK+h4gNwyr7jdRp7CkVVNdGTe
qbq/mJ49e1HG0lDB/AK4fnm+E9yd8V/P7W9Rb/12TURqLYLw4OisbX4uk0nWR6hk
uXryo3jz0hqu28R50BcN03uB2pD0OSSmFRoUxi7fwVweGjJIHJWi9yXVduQAuYyd
w9ZATvHfmn0TcAp5VPVCjOAP+zsw/HhKkhlRpdLcd6LR7DIrKqeogZnfqA9Q+zDr
Wvn7jZ1zGfotQL8dUSNENkzjAdd3MmMzzsvM/PMi0B+ThRynSS7m81KZmPst5cn2
p/zMmidiKqmDbYxTFlFiSXrtZMIn/PQoADz9+LbMbhrAz0Rwha8aFONvyBEX+Zk+
nER4g/qd9wA2ogXEeyXjT5IsUDDsMSSa75HWsT7APnfczMypTjDs7z1KE4/jKpfG
zV1Pu1u4VM1vdiD8tduB/b+zW2AeBQmA77vFhtyRa0b5eZd1cjytM4QX6uHgMIyF
0PhnHnMB/EBD6bCDIoo7eB3H6HDbwYPw488H9WJexCa08FUQfPAYOceoNQq9pDlm
T9xzXxT/ctoht8vJYwwvhXsiByu4G7RIXr1WWpNdb5H7dl/i17tLr/d0kj6Z1Mb3
Pakvg15JceftS2E8GMHarpDGomnpomvZD1mgB6vlNzr4DtONpq+bq+bmV+FQa4rF
dxKJQcAJ0iHXvLWnniIY3T7KxWFz+V43L26PX3fg7Stzkje2AB4pvA==
<del>—</del>-END <span class="caps">RSA PRIVATE KEY</span>-<del>—</del></p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:31:37-08:00
Providing your SSH Key - version 51
Tue Jan 20 00:31:37 -0800 2009
<p>rqw71QKDIHl/gH8xfr85aec4SQladaXB30RZ+Qt3v4mqRbVUKdiuxL4KFH23kKQz
0WKVsQcWqOaFnwD+oZndxpleVYUH4jtWNP2PEfpkHSBi1xE1b/6GYGWpENs2jpnz
n5Qg6K3PCw8a/F3CsG5EBVEFagvaLXdlGZ5ASqJ7f/5UnNElVIv5vTlxQ/2KH1iZ
FmVO1W1rdrGN2XeHKHrAcPOBlpnuKPml4mCKBZ5LMksHY/aEfq70giYIECXvPmxB
Zu1HlVpmWNmKxZoMKsIbO/6eIjKAfhjmrC+S6obQvuEU2bbq2qJ5fPy8HUdQGUQX
4zTwZkpTSPMlkJmWORSLnBjFtcQUPLiWtt6qMtORs4SenTveWKHHIVCUhB18Txwe
HXIlizFrrTcaOxIS1FylNqTN8oGn72gqfyDi5+SGTcz6rMk7O/wqzGB9yGNHCbn9
59aSPd3JXvljZqwBq2yioqyUWDApJHNrV0J5+Tc3RZn7EHROQpcKxTrnn0MFumWZ
FMyeorkrdITn3ia7MW5CvY9+qAhaf5heZf3GXhnOOSGaspJxSVroes+x30xnkeG5
/GOnM0mOQmrE+ahI+4×1Snwmcr+YdO8MPbeMqNxpljSvtSU5aw/+QoqqmIUBmBC7
ZBwM3zv5QoIIUim/jhIPTuVwNKnN8b94KanbY1CDtHeVH6TUj0M2ro6AofSw8R/9
BAD9xI1BMLy2NZltIq86AD2b4rJBOGqMLDGPcl46GCraTwtN8u40le/yq6+xu27h
/hMQmM8JaAplL7Nd8hxrfW35BXunTMoFigKIxsgiugN/+L80kyKGS8FdyaDYN3m/
5XB91NpY0CZ4RjhkPSqS+wvmiVVaorZDb+DkkztOK+h4gNwyr7jdRp7CkVVNdGTe
qbq/mJ49e1HG0lDB/AK4fnm+E9yd8V/P7W9Rb/12TURqLYLw4OisbX4uk0nWR6hk
uXryo3jz0hqu28R50BcN03uB2pD0OSSmFRoUxi7fwVweGjJIHJWi9yXVduQAuYyd
w9ZATvHfmn0TcAp5VPVCjOAP+zsw/HhKkhlRpdLcd6LR7DIrKqeogZnfqA9Q+zDr
Wvn7jZ1zGfotQL8dUSNENkzjAdd3MmMzzsvM/PMi0B+ThRynSS7m81KZmPst5cn2
p/zMmidiKqmDbYxTFlFiSXrtZMIn/PQoADz9+LbMbhrAz0Rwha8aFONvyBEX+Zk+
nER4g/qd9wA2ogXEeyXjT5IsUDDsMSSa75HWsT7APnfczMypTjDs7z1KE4/jKpfG
zV1Pu1u4VM1vdiD8tduB/b+zW2AeBQmA77vFhtyRa0b5eZd1cjytM4QX6uHgMIyF
0PhnHnMB/EBD6bCDIoo7eB3H6HDbwYPw488H9WJexCa08FUQfPAYOceoNQq9pDlm
T9xzXxT/ctoht8vJYwwvhXsiByu4G7RIXr1WWpNdb5H7dl/i17tLr/d0kj6Z1Mb3
Pakvg15JceftS2E8GMHarpDGomnpomvZD1mgB6vlNzr4DtONpq+bq+bmV+FQa4rF
dxKJQcAJ0iHXvLWnniIY3T7KxWFz+V43L26PX3fg7Stzkje2AB4pvA==</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:27:47-08:00
Providing your SSH Key - version 50
Tue Jan 20 00:27:47 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAzzwrqWvAyb8ACCS6MJD6A5lzvgJbo7hMci0firG/Xs9Ct9lm5LBEDZ1mL9ppllIhUms+KdKbakm9dRmDmGvRqihNf8Y3deBAVK+i5pSlL8YO+bLie+jxuD9WcJ9yXEWCkWOnEa2LYuui/9kCghbdF28EVVUMol5gvdsXj/SzwmtsqIALSqYDpsh4OSVl1vBSEUwyhZsgVmV0UYjgfNdcqKUvHPOCPe9vd9ZqWRLP30TpjCjege4YYL0FKuXj4wQNHUGdXzWqW+YT1NlwaDPiUBfMgHYlqwHvCMsiC1ZYc8hJypnrj1UeL7omqIbCO7T33R1fIgCblY33Pq+VIw1J7Q== arden.emily@gmail.com</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:07:54-08:00
Providing your SSH Key - version 49
Tue Jan 20 00:07:54 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAt6txUfmf+i6Ctq6wi9rgNueitdREmbNpM4umv2DA0U5/tG6H8xKHformmvfQJphNoNhZ+vWs24F4AckQVgHAEBSgPDOtphK4Bmk/pWodKMBIcPNyl7oASHiqpbFMfEJRLfYAW5ofirBljaR4yu7wwFNq1Ltzz2SqSUy6BszEmEMEeq1b7c34hvijOSZIQyylxsA/kFVa3L9LIg4wTP9Tp8QCpherRLt/q6NK3cfSho8mfN+zIPbZrzRSAozLQqNlHhL2fImqSymb0iaCb+PD7MkzRUj/7CMGzzqnD5O9+LULLUQCSPCZ07c9L47eDcTegtSs2wmYLA33Pajm8Yi8bw</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-20T00:06:51-08:00
Providing your SSH Key - version 48
Tue Jan 20 00:06:51 -0800 2009
<p>AAAAB3NzaC1yc2EAAAABIwAAAQEAt6txUfmf+i6Ctq6wi9rgNueitdREmbNpM4umv2DA0U5/tG6H8xKHformmvfQJphNoNhZ+vWs24F4AckQVgHAEBSgPDOtphK4Bmk/pWodKMBIcPNyl7oASHiqpbFMfEJRLfYAW5ofirBljaR4yu7wwFNq1Ltzz2SqSUy6BszEmEMEeq1b7c34hvijOSZIQyylxsA/kFVa3L9LIg4wTP9Tp8QCpherRLt/q6NK3cfSho8mfN+zIPbZrzRSAozLQqNlHhL2fImqSymb0iaCb+PD7MkzRUj/7CMGzzqnD5O9+LULLUQCSPCZ07c9L47eDcTegtSs2wmYLA33Pajm8Yi8bw</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-19T23:47:21-08:00
Providing your SSH Key - version 47
Mon Jan 19 23:47:21 -0800 2009
<p>ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAt6txUfmf+i6Ctq6wi9rgNueitdREmbNpM4umv2DA0U5/tG6H8xKHformmvfQJphNoNhZ+vWs24F4AckQVgHAEBSgPDOtphK4Bmk/pWodKMBIcPNyl7oASHiqpbFMfEJRLfYAW5ofirBljaR4yu7wwFNq1Ltzz2SqSUy6BszEmEMEeq1b7c34hvijOSZIQyylxsA/kFVa3L9LIg4wTP9Tp8QCpherRLt/q6NK3cfSho8mfN+zIPbZrzRSAozLQqNlHhL2fImqSymb0iaCb+PD7MkzRUj/7CMGzzqnD5O9+LULLUQCSPCZ07c9L47eDcTegtSs2wmYLA33Pajm8Yi8bw== “arden.emily@email.com”</p>
arden
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2009-01-05T17:38:16-08:00
Providing your SSH Key - version 46
Mon Jan 05 17:38:16 -0800 2009
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
Arifur
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-12-19T15:36:01-08:00
Providing your SSH Key - version 45
Fri Dec 19 15:36:01 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
tekkub
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-12-19T15:34:32-08:00
Providing your SSH Key - version 44
Fri Dec 19 15:34:32 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry (ssh-add ~/.ssh/id_rsa).</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter passphrase or hit enter></span>
Enter same passphrase again: <span class="command"><enter passphrase again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry, or you can simply hit enter to not use a passphrase.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
tekkub
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-12-15T19:51:07-08:00
Providing your SSH Key - version 43
Mon Dec 15 19:51:07 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry (ssh-add ~/.ssh/id_rsa).</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter a passphrase if you wish (it is generally recommended that you do not use a passphrase) and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
tekkub
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-12-04T12:47:20-08:00
Providing your SSH Key - version 42
Thu Dec 04 12:47:20 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry (ssh-add ~/.ssh/id_rsa).</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</code></pre>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-11-27T16:12:54-08:00
Providing your SSH Key - version 41
Thu Nov 27 16:12:54 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry (ssh-add ~/.ssh/id_rsa).</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then:</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip then either install it using your OS’s package manager or print out the publick key to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
gravious
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-11-27T16:09:22-08:00
Providing your SSH Key - version 40
Thu Nov 27 16:09:22 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry (ssh-add ~/.ssh/id_rsa).</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser. If you have xclip installed then</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | xclip</span></code></pre>
<p>The <code>xclip</code> command copies whatever is sent to it via <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key! If you don’t have xclip, either install it using your OS’s package manager or dump it to a terminal so that you can manually copy the key data.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
gravious
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-11-25T04:46:11-08:00
Providing your SSH Key - version 39
Tue Nov 25 04:46:11 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry (ssh-add ~/.ssh/id_rsa).</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
nicholasng
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-11-19T14:33:07-08:00
Providing your SSH Key - version 38
Wed Nov 19 14:33:07 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry (ssh-add ~/.ssh/id_rsa).</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
JimW
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-10-30T19:25:18-07:00
Providing your SSH Key - version 37
Thu Oct 30 19:25:18 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a <code>config</code> file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
idearise
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-10-30T19:24:38-07:00
Providing your SSH Key - version 36
Thu Oct 30 19:24:38 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<p>I needed to create a config file in the .ssh directory containing the following to point to the relevant IdentityFile:</p>
<pre class="console"><code>
Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes
</code></pre>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
idearise
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-09-13T21:41:50-07:00
Providing your SSH Key - version 35
Sat Sep 13 21:41:50 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. (REALLY?) Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
gregc
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-09-03T16:40:12-07:00
Providing your SSH Key - version 34
Wed Sep 03 16:40:12 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere, usually in your user folder <code>c:\Documents and Settings\Username\.ssh</code> on XP or <code>c:\Users\Username\.ssh</code> on Vista. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you should add to your account on github. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit..</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
tekkub
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-08-16T09:46:21-07:00
Providing your SSH Key - version 33
Sat Aug 16 09:46:21 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_rsa git@github.com’</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
eagereyes
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-08-16T09:45:33-07:00
Providing your SSH Key - version 32
Sat Aug 16 09:45:33 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_dsa git@github.com’</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
eagereyes
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-07-15T18:52:19-07:00
Providing your SSH Key - version 31
Tue Jul 15 18:52:19 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 <key_name>.pub’ after creation.</li>
<li>`ssh-add <key_name>’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_dsa.pub git@github.com’</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
reednj
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-07-02T04:25:28-07:00
Providing your SSH Key - version 30
Wed Jul 02 04:25:28 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h3>Problems?</h3>
<p>The steps above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 id_dsa.pub’ after creation.</li>
<li>`ssh-add’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_dsa.pub git@github.com’</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
msp
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-07-02T04:24:18-07:00
Providing your SSH Key - version 29
Wed Jul 02 04:24:18 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<p><b>Problems?</b> – The above didn’t work for me. I found that this <a href="https://www.cs.indiana.edu/csg/FAQ/Security/openssh.html">openssh guide</a> helped me out. The missing parts (i think) were:</p>
<ol>
<li>`chmod 600 id_dsa.pub’ after creation.</li>
<li>`ssh-add’ in my shell.</li>
</ol>
<p>I debugged the connection by just trying a pure ssh connection to github:</p>
<p>`ssh -vi ~/.ssh/id_dsa.pub git@github.com’</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
msp
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-05-23T15:49:02-07:00
Providing your SSH Key - version 28
Fri May 23 15:49:02 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Microsoft Windows using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-05-22T16:39:20-07:00
Providing your SSH Key - version 27
Thu May 22 16:39:20 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
cleitonfco
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-05-22T16:29:52-07:00
Providing your SSH Key - version 26
Thu May 22 16:29:52 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.chiark.greenend.org.uk/<sub>sgtatham/putty/download.html”>PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.chiark.greenend.org.uk/</sub>sgtatham/putty/download.html”>Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
cleitonfco
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-17T22:21:44-07:00
Providing your SSH Key - version 25
Thu Apr 17 22:21:44 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit. <span class="caps">NOTE</span>: Git <span class="caps">GUI</span> can not yet upload to Github unless you set up ssh to upload key for you. Best to use the Git command line.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T23:39:38-07:00
Providing your SSH Key - version 24
Tue Apr 15 23:39:38 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<h3>Step 1</h3>
<p>Get the Git version of mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">Git-(version).exe</a> It’s a small download and installs just by double clicking the download. msysGit is a full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T23:37:25-07:00
Providing your SSH Key - version 23
Tue Apr 15 23:37:25 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<h3>Step 1</h3>
<p>Get mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">https://code.google.com/p/msysgit/downloads/list</a> It’s a small download and installs just by double clicking the download. It’s full featured environment for working with Git under windows.</p>
<h3>Step 2</h3>
<p>Run Git Bash program</p>
<h3>Step 3</h3>
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4</h3>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T23:35:17-07:00
Providing your SSH Key - version 22
Tue Apr 15 23:35:17 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<h3>Step 1
Get mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">https://code.google.com/p/msysgit/downloads/list</a> It’s a small download and installs just by double clicking the download. It’s full featured environment for working with Git under windows.</h3>
<h3>Step 2
Run Git Bash program</h3>
h3. Step 3
Then create a ssh key by typing:
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
Then enter password twice and when prompted for the name of file for the key leave blank and press enter
<h3>Step 4
Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Use windows search if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit.</h3>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T23:12:54-07:00
Providing your SSH Key - version 21
Tue Apr 15 23:12:54 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<p>Get mysGit at: <a href="https://code.google.com/p/msysgit/downloads/list">https://code.google.com/p/msysgit/downloads/list</a> It’s a small download and installs just by double clicking the download. It’s great for working with Git under windows.</p>
<p>Run Git Bash program</p>
<p>Then create a ssh key by typing:</p>
<pre class="console"><code>ssh-keygen -C “username@email.com” -t rsa</pre></code>
<p>Then enter password twice and when prompted for the name of file for the key leave blank and press enter</p>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Search for it if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T23:08:28-07:00
Providing your SSH Key - version 20
Tue Apr 15 23:08:28 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
<li><a href="#windowsxp">Windows using PuTTYgen</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<p>Get mysGit at: https://code.google.com/p/msysgit/downloads/list It’s a small download and installs just by double clicking the download. It’s great for working with Git under windows.</p>
<p>Run Git Bash program</p>
<p>Then create a ssh key by typing:</p>
<p>ssh-keygen -C “username@email.com” -t rsa</p>
<p>Then enter password twice and when prompted for the name of file for the key leave blank and press enter</p>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Search for it if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit.</p>
<h2 id="windowsxp">Microsoft Windows using PuTTYgen</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T22:58:46-07:00
Providing your SSH Key - version 19
Tue Apr 15 22:58:46 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
<li><a href="#msysGit">Windows using msysGit</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<p>Get mysGit at: https://code.google.com/p/msysgit/downloads/list It’s a small download and installs just by double clicking the download. It’s great for working with Git under windows.</p>
<p>Run Git Bash program</p>
<p>Then create a ssh key by typing:</p>
<p>ssh-keygen -C “username@email.com” -t rsa</p>
<p>Then enter password twice and when prompted for the name of file for the key leave blank and press enter</p>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Search for it if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit.</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T22:58:13-07:00
Providing your SSH Key - version 18
Tue Apr 15 22:58:13 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a>
*<a href="#msysGit">Windows using msysGit</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="msysGit">Create key using msysGit</h2>
<p>Get mysGit at: https://code.google.com/p/msysgit/downloads/list It’s a small download and installs just by double clicking the download. It’s great for working with Git under windows.</p>
<p>Run Git Bash program</p>
<p>Then create a ssh key by typing:</p>
<p>ssh-keygen -C “username@email.com” -t rsa</p>
<p>Then enter password twice and when prompted for the name of file for the key leave blank and press enter</p>
<p>Look at the output and it will hint at where the key is stored. It’s stored in a .ssh folder somewhere. The file with the public key is “id_rsa.pub”. Search for it if you can’t find it. Then open it with notepad and copy the text. That is the public key you give to others and hosting sites. Leave the files where they are. Running ssh-keygen sets up the keys for both Git Bash and Git <span class="caps">GUI</span> that all come part of msysGit.</p>
sarpulhu
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T15:54:31-07:00
Providing your SSH Key - version 17
Tue Apr 15 15:54:31 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
josephholsten
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-04-15T15:52:42-07:00
Providing your SSH Key - version 16
Tue Apr 15 15:52:42 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. You copy from the command line using pbcopy.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
josephholsten
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-13T10:41:51-07:00
Providing your SSH Key - version 15
Thu Mar 13 10:41:51 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
adakkak
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-09T15:17:26-07:00
Providing your SSH Key - version 14
Sun Mar 09 15:17:26 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre class="console"><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-09T15:15:22-07:00
Providing your SSH Key - version 13
Sun Mar 09 15:15:22 -0700 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre class="console"><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-06T15:22:52-08:00
Providing your SSH Key - version 12
Thu Mar 06 15:22:52 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool, provided by the <a href="https://www.putty.org/">PuTTY project</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatever you like, just remember where it’s at, because you’ll have to set it up in <a href="https://www.putty.org/">Pageant</a> later.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
vertiginous
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-06T15:18:23-08:00
Providing your SSH Key - version 11
Thu Mar 06 15:18:23 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1
\
If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool. You can download it from the <a href="https://www.chiark.greenend.org.uk/<sub>sgtatham/putty/download.html”>PuTTy download page</a>. There is also an installer available that includes all of the PuTTY tools.
\
h3. Step 2</h3>
Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.
\\
Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatevr you like, just remember where it’s at, because you’ll have to tell git about it later. The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can get pageant.exe from the <a href="https://www.chiark.greenend.org.uk/</sub>sgtatham/putty/download.html”>PuTTy download page</a> to automate password entry.
\\
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! You can also save the public key if you’d like to use it elsewhere.</p>
vertiginous
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-06T15:11:23-08:00
Providing your SSH Key - version 10
Thu Mar 06 15:11:23 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a> (to be added)</li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool. You can download it from the <a href="https://www.chiark.greenend.org.uk/sgtatham/putty/download.html">PuTTy download page</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatevr you like, just remember where it’s at, because you’ll have to tell git about it later. The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can get pageant.exe from the <a href="https://www.chiark.greenend.org.uk/sgtatham/putty/download.html">PuTTy download page</a> to automate password entry.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! You can also save the public key if you’d like to use it elsewhere.</p>
vertiginous
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-06T15:10:04-08:00
Providing your SSH Key - version 9
Thu Mar 06 15:10:04 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a> (to be added)</li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool. You can download it from the <a href="https://www.chiark.greenend.org.uk/<sub>sgtatham/putty/download.html”>PuTTy download page</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatevr you like, just remember where it’s at, because you’ll have to tell git about it later. The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can get pageant.exe from the <a href="https://www.chiark.greenend.org.uk/</sub>sgtatham/putty/download.html”>PuTTy download page</a> to automate password entry.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! You can also save the public key if you’d like to use it elsewhere.</p>
vertiginous
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-03-06T15:06:05-08:00
Providing your SSH Key - version 8
Thu Mar 06 15:06:05 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a> (to be added)</li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<h3>Step 1</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the PuTTYgen tool. You can download it from the <a href="https://www.chiark.greenend.org.uk/<sub>sgtatham/putty/download.html”>PuTTy download page</a>. There is also an installer available that includes all of the PuTTY tools.</p>
<h3>Step 2</h3>
<p>Start PuTTYgen, and press the “Generate” button. PuTTYgen will prompt you to “generate some randomness by moving the mouse over the blank area”. Once this is done, a new public key will be displayed at the top of the window.</p>
<p>Enter in a key passphrase and confirm it in the appropriate boxes, then save your private key to a file. You can call the file whatevr you like, just remember where it’s at, because you’ll have to tell git about it later. The passphrase that you enter will be requested from you every time you push or pull from a private repo. You can get pageant.exe from the <a href="https://www.chiark.greenend.org.uk/</sub>sgtatham/putty/download.html”>PuTTy download page</a> to automate password entry.</p>
<h3>Step 3</h3>
<p>Highlight the public key at the top of the page, and copy it to the clipboard . Now you can simply select the appropriate text entry box in GitHub and paste in your public key! You can also save the public key if you’d like to use it elsewhere.</p>
vertiginous
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-02-24T00:41:33-08:00
Providing your SSH Key - version 7
Sun Feb 24 00:41:33 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowsxp">Windows XP</a> (to be added)</li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<p>to be added.</p>
xuejm
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-02-24T00:40:49-08:00
Providing your SSH Key - version 6
Sun Feb 24 00:40:49 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowxp">Windows XP</a> (to be added)</li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="windowsxp">Microsoft Windows XP</h2>
<p>to be added.</p>
xuejm
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-02-24T00:39:37-08:00
Providing your SSH Key - version 5
Sun Feb 24 00:39:37 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windowxp">Windows XP</a> (to be added)</li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
xuejm
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-02-18T12:01:29-08:00
Providing your SSH Key - version 4
Mon Feb 18 12:01:29 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH"><span class="caps">SSH</span></a> to authenticate you during git’s push and pull commands. In order for GitHub to identify you, you must provide us with your <span class="caps">SSH</span> public key. The rest of this page contains instructions on how to locate or create a set of <span class="caps">SSH</span> keys.</p>
<ul>
<li><a href="#macosx">Mac <span class="caps">OS X</span></a></li>
<li><a href="#linux">Linux</a></li>
</ul>
<h2 id="macosx">Mac <span class="caps">OS X</span></h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></code></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><code><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</code></pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</code></pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><code><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</code></pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-01-28T09:33:09-08:00
Providing your SSH Key - version 3
Mon Jan 28 09:33:09 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH">SSH</a> to authenticate you during git's push and pull commands. In order for GitHub to identify you, you must provide us with your SSH public key. The rest of this page contains instructions on how to locate or create a set of SSH keys.</p>
<ul>
<li><a href="#macosx">Mac OS X</a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windows">Windows</a></li>
</ul>
<h2 id="macosx">Mac OS X</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. The <code>something</code> file is your private key and must be kept secret. The <code>something.pub</code> file is your public key, and this is what you’ll be giving us. If you already have a key pair (in the above listing I have an <code>id_rsa</code> key pair) and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-01-27T17:04:03-08:00
Providing your SSH Key - version 2
Sun Jan 27 17:04:03 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH">SSH</a> to authenticate you during git's push and pull commands. In order for GitHub to identify you, you must provide us with your SSH public key. The rest of this page contains instructions on how to locate or create a set of SSH keys.</p>
<ul>
<li><a href="#macosx">Mac OS X</a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windows">Windows</a></li>
</ul>
<h2 id="macosx">Mac OS X</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. Never ever send the <code>something</code> key to anybody. That is your private key and must be kept secret. You can send the <code>something.pub</code> key as far and wide as you like. If you already have a key pair and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. Never ever send the <code>something</code> key to anybody. That is your private key and must be kept secret. You can send the <code>something.pub</code> key as far and wide as you like. If you already have a key pair and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo
tag:github.com,2008:Guide/1
2008-01-27T16:08:37-08:00
2008-01-27T17:03:12-08:00
old - version 1
Sun Jan 27 17:03:12 -0800 2008
<h2>Overview</h2>
<p>GitHub uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography">public-key cryptography</a> and <a href="https://en.wikipedia.org/wiki/SSH">SSH</a> to authenticate you during git's push and pull commands. In order for GitHub to identify you, you must provide us with your SSH public key. The rest of this page contains instructions on how to locate or create a set of SSH keys.</p>
<ul>
<li><a href="#macosx">Mac OS X</a></li>
<li><a href="#linux">Linux</a></li>
<li><a href="#windows">Windows</a></li>
</ul>
<h2 id="macosx">Mac OS X</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. Never ever send the <code>something</code> key to anybody. That is your private key and must be kept secret. You can send the <code>something.pub</code> key as far and wide as you like. If you already have a key pair and you want to use it for GitHub, then skip to <a href="#macosx-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">ssh-keygen</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /Users/tom/.ssh/id_rsa.
Your public key has been saved in /Users/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="macosx-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub | pbcopy</span></pre>
<p>The <code>pbcopy</code> command copies whatever is sent to it on <span class="caps">STDIN</span> to the clipboard, ensuring that you won’t have any extraneous newlines or other problems. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
<h2 id="linux">Linux</h2>
<h3>Step 1</h3>
<p>Check to see if you already have a public/private key pair for your user. If you do, it will be in your <code>~/.ssh</code> directory.</p>
<pre><span>[~]</span>$ <span class="command">cd .ssh</span>
<span>[~/.ssh]</span>$ <span class="command">ls</span>
config id_rsa.pub
id_rsa known_hosts</pre>
<p>Key pairs are always named like <code>something</code> and <code>something.pub</code>. Never ever send the <code>something</code> key to anybody. That is your private key and must be kept secret. You can send the <code>something.pub</code> key as far and wide as you like. If you already have a key pair and you want to use it for GitHub, then skip to <a href="#linux-3">Step 3</a>.</p>
<h3>Step 2</h3>
<p>If you don’t have any keys yet, then you’ll need to generate them. This can be done with the <code>ssh-keygen</code> program.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">ssh-keygen -t rsa</span>
Generating public/private rsa key pair.
Enter file in which to save the key (/home/tom/.ssh/id_rsa): <span class="command"><enter></span>
Enter passphrase (empty for no passphrase): <span class="command"><enter password></span>
Enter same passphrase again: <span class="command"><enter password again></span>
Your identification has been saved in /home/tom/.ssh/id_rsa.
Your public key has been saved in /home/tom/.ssh/id_rsa.pub.
The key fingerprint is:
50:43:77:c6:97:af:61:82:dc:ea:9b:6b:67:d4:1b:61 tom@volcano</pre>
<p>You are free to name your key pair whatever you like. Just make sure you copy the correct public key in the next step. The password that you enter will be requested from you every time you push or pull from a private repo. You can use <code>ssh-agent</code> or the built-in keychain support in Leopard to automate password entry.</p>
<h3 id="linux-3">Step 3</h3>
<p>Copy your public key to the clipboard so you can easily paste it into your web browser.</p>
<pre><span>[~/.ssh]</span>$ <span class="command">cat id_rsa.pub</span>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1FlHRbbxXIv/hLDTeJczlEqGNt0oFcoPEEENHThzP5ku
PDsitSSUH2MATP014G/3BzaI9pdnhf02MSEcmtmIKXrm05/dzxEmp9yOY32YHyk6/rLUGGTJuWOpGt3J
6H5LWxq9yeRUuFG/pCRH3+KxOyzasSHXfXJaC5v7wPxUdAeg9k0jwsUjnqUcYvzo5+GwCXV9dIwY3Sr/
OrL2l8SCdSWyd3PLufJXKQHlouHB0NI/+G/QjWmkB8c1PJh/VuIe36mqv82V9XXKvYNaVWwz5Sg6aY9u
p2lgDEme+AFdPPjOnkdF6OHCr7ymKg6c/B2YCbOW7QN/L4uAdVOhTNnJMQ== tom@volcano</pre>
<p>Copy the entirety of the public key to the clipboard. It is important that there are no newlines in the key (copying from the <code>cat</code> output in your console should work properly. Now you can simply select the appropriate text entry box in GitHub and paste in your public key!</p>
mojombo