From e8dfed79866a4e16bbd5675c463a95e1e0e0ab6f Mon Sep 17 00:00:00 2001
From: tekkub <tekkub@gmail.com>
Date: Thu, 3 Sep 2009 18:22:13 -0600
Subject: New guide for ssh-agent, don't tell people to make passphrase-less
 keys

---
 _posts/2009-06-15-mac-key-setup.textile | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

(limited to '_posts/2009-06-15-mac-key-setup.textile')

diff --git a/_posts/2009-06-15-mac-key-setup.textile b/_posts/2009-06-15-mac-key-setup.textile
index 68bae5d..ad19636 100644
--- a/_posts/2009-06-15-mac-key-setup.textile
+++ b/_posts/2009-06-15-mac-key-setup.textile
@@ -52,7 +52,9 @@ The key's randomart image is:
 |                 |
 +-----------------+</pre>
 
-At each prompt we just hit enter.  This will generate the key with the default name and no passphrase.  If you want to add a passphrase to your key you can do so later.  You will be prompted for the passphrase every time you push or pull from GitHub, so you might not want to use one unless you are using a shared computer.
+At the first prompt you can just hit enter to generate the key with the default name.  *You should use a good passphrase with your key.*  See "Working with SSH key passphrases":/working-with-key-passphrases for more details on why you should use a passphrase and how to avoid re-entering it every time you use your key.
+
+p(. *Note:* If you don't use the default key names, or store your keys in a different path, you will need to run @ssh-add path/to/my_key@ so that ssh knows where to find your key.
 
 h2. Adding the key to your GitHub account
 
-- 
cgit v1.3.1

