From 2828c913d3bd41b6da0e282f3411dd28284d7ddf Mon Sep 17 00:00:00 2001 From: Richard Hartmann Date: Mon, 15 Apr 2013 02:09:59 +0200 Subject: [PATCH] Update blog to reflect 21f93de --- .../blog/day_237__gnome-keyring_craziness.mdwn | 10 +++++----- 1 file 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 bde1e59d1f..7a528573ba 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 `~/.ssh/annex/` +`~/.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