summaryrefslogtreecommitdiff
path: root/_posts/2010-01-19-multiple-keys.markdown
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2010-07-15 19:21:46 -0600
committertekkub <tekkub@gmail.com>2010-07-15 19:21:46 -0600
commitfc0e28b11afd5c41dea40e35eab2260f59d87e8b (patch)
treeaa3733a480ed7ec35040ea3dcc37917d4809836f /_posts/2010-01-19-multiple-keys.markdown
parent8bb4333a5ea527cc9b53edf509bb9f7c25e42350 (diff)
Space saves the day!
Diffstat (limited to '_posts/2010-01-19-multiple-keys.markdown')
-rw-r--r--_posts/2010-01-19-multiple-keys.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2010-01-19-multiple-keys.markdown b/_posts/2010-01-19-multiple-keys.markdown
index 52c5c6e..fc82d5f 100644
--- a/_posts/2010-01-19-multiple-keys.markdown
+++ b/_posts/2010-01-19-multiple-keys.markdown
@@ -21,7 +21,7 @@ Configuring SSH
Once SSH has access to both keys, you need to tell it which key to use for which server. In most cases you can assume that SSH will fall back to `~/.ssh/id_rsa` by default, but we're going to force it anyway. To begin, open `~/.ssh/config` in your favorite editor.
-<script src="http://gist.github.com/281414.js?file=config"></script>
+<script src="http://gist.github.com/281414.js?file=config"> </script>
In short what this does is tells SSH to use the client key when connecting to the server github-client, which is really github.com.