summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Richard Hartmann <richih.mailinglist@gmail.com>2013-04-15 02:09:59 +0200
committerGravatar Richard Hartmann <richih.mailinglist@gmail.com>2013-04-15 02:09:59 +0200
commit63c6d7abfc087427f2e55897648b4c0dfca7447f (patch)
tree7e59f2b099d54f1d60926106a977f104858f88f1
parent79a5475b54295d5b44b93b888bb823015ede8756 (diff)
Update blog to reflect 79a5475
-rw-r--r--doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn b/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn
index bde1e59d1..7a528573b 100644
--- a/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn
+++ b/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn
@@ -8,11 +8,11 @@ that watches for `~/.ssh/*.pub` to appear, and automatically adds all such
keys to the keyring. In at least some cases, probably when it has no other
key, it then tells ssh to go ahead and use that key. Astounding.
-To avoid this, the assistant will store its keys in `~/.ssh/annex/`
-instead. gnome-keyring does not look there (verified in the source).
-If you use gnome-keyring and have set up a repository on a remote server
-with the assistant, I'd recommend moving the keys it set up and editing
-`~/.ssh/config` to point to their new location.
+To avoid this, the assistant will store its keys in <s>`~/.ssh/annex/`</s>
+`~/.ssh/git-annex/` instead. gnome-keyring does not look there (verified in
+the source). If you use gnome-keyring and have set up a repository on a
+remote server with the assistant, I'd recommend moving the keys it set up
+and editing `~/.ssh/config` to point to their new location.
gnome-keyring is not the only peice of software that has a bad
interaction with git-annex. I've been working on a bug that makes git-annex