From 35109c48fd823a3045937be99e8c2ee74657d58d Mon Sep 17 00:00:00 2001
From: tekkub <tekkub@gmail.com>
Date: Sat, 5 Feb 2011 17:14:48 -0700
Subject: Fix a stale link

---
 _posts/2009-06-17-troubleshooting-ssh.textile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to '_posts/2009-06-17-troubleshooting-ssh.textile')

diff --git a/_posts/2009-06-17-troubleshooting-ssh.textile b/_posts/2009-06-17-troubleshooting-ssh.textile
index fc05789..dcad159 100644
--- a/_posts/2009-06-17-troubleshooting-ssh.textile
+++ b/_posts/2009-06-17-troubleshooting-ssh.textile
@@ -20,7 +20,7 @@ This error occurs when you attach your key as a deploy key on repo1.  You can pu
 
 h2. Permission denied (publickey)
 
-This is usually caused when ssh cannot find your keys.  Make sure your key is in the default location, @~/.ssh@. If you run @ssh-keygen@ again and just press enter at all 3 prompts it will be placed here automatically. Then you can add the contents of id_rsa.pub to "my github keys":https://github.com/account. If id_rsa.pub doesn't work try id_dsa.pub. You might need to generate a new dsa key with @ssh-keygen -t dsa@ if you just have an rsa key.
+This is usually caused when ssh cannot find your keys.  Make sure your key is in the default location, @~/.ssh@. If you run @ssh-keygen@ again and just press enter at all 3 prompts it will be placed here automatically. Then you can add the contents of id_rsa.pub to "your account":https://github.com/account#ssh_bucket. If id_rsa.pub doesn't work try id_dsa.pub. You might need to generate a new dsa key with @ssh-keygen -t dsa@ if you just have an rsa key.
 
 h3. Finding out what keys ssh is using
 
-- 
cgit v1.3.1

