diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-04-14 15:34:59 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-04-14 15:34:59 -0400 |
| commit | a6167fdc86c7431cf48e32dbf851132a21cf3bd3 (patch) | |
| tree | 968dfe825936798a1bf2e73dab4404d7a80cc833 /doc/bugs | |
| parent | 7a1165bc3ac8c9069ed6fd5043227d284dc6b83b (diff) | |
random ssh keys (╯°□°）╯︵ ┻━┻ gnome-keyring
assistant: Work around horrible, terrible, very bad behavior of
gnome-keyring, by not storing special-purpose ssh keys in ~/.ssh/*.pub.
Apparently gnome-keyring apparently will load and indiscriminately use such
keys in some cases, even if they are not using any of the standard ssh key
names. Instead store the keys in ~/.ssh/annex/, which gnome-keyring will
not check.
Note that neither I nor #debian-devel were able to quite reproduce this
problem, but I believe it exists, and that this fixes it. And it certianly
won't hurt anything..
Diffstat (limited to 'doc/bugs')
| -rw-r--r-- | doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn index aba111a26..b98e09b32 100644 --- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn +++ b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn @@ -18,4 +18,12 @@ git-annex version: 4.20130324, Ubuntu 11.04 **Please provide any additional information below.** - +> [[done]]. Although I have not 100% reproduced this, I have seen +> enough of the source code to gnome-keyring to be pretty sure it's at +> fault, and that my fix works. +> +> If this is happening to you, you can fix it by making a `~/.ssh/annex/` +> directory and moving `~/.ssh/key.annex*` to it. Then you'll need to edit +> `~/.ssh/config` to use the new path to the key. And you'll need to run +> `ssh-add -D` to clear out the bogus keys from the ssh agent (or log out +> and back in). --[[Joey]] |