From c3877a436174f315a5529bf028bd577ca7b8e795 Mon Sep 17 00:00:00 2001 From: tekkub Date: Sat, 30 Oct 2010 16:21:55 -0600 Subject: Embed code directly (plus highlighting!) instead of using gists --- _posts/2010-01-19-multiple-keys.markdown | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) (limited to '_posts/2010-01-19-multiple-keys.markdown') diff --git a/_posts/2010-01-19-multiple-keys.markdown b/_posts/2010-01-19-multiple-keys.markdown index fc82d5f..bea4b6b 100644 --- a/_posts/2010-01-19-multiple-keys.markdown +++ b/_posts/2010-01-19-multiple-keys.markdown @@ -21,7 +21,19 @@ 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. - +{% highlight bash %} +# Default GitHub user (joe) +Host github.com + HostName github.com + User git + IdentityFile /Users/joe/.ssh/id_rsa + +# Client user (client) +Host github-client + HostName github.com + User git + IdentityFile /Users/joe/.ssh/id_rsa_client +{% endhighlight %} 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. -- cgit v1.3.1