diff options
author | 2014-10-30 14:33:46 +0000 | |
---|---|---|
committer | 2014-10-30 14:33:46 +0000 | |
commit | 0a0d10f2cbd5f8b1ca14ce3d26af0605db4bfb9d (patch) | |
tree | fbb0713ec7377c0b9a1b4aa3c8c714f5b97dd0b8 | |
parent | 28cdd079c5cca867815dc09c7190da7d22f591cb (diff) |
add more information
-rw-r--r-- | doc/bugs/flooding_me_with_ssh_password_prompts.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/flooding_me_with_ssh_password_prompts.mdwn b/doc/bugs/flooding_me_with_ssh_password_prompts.mdwn index 6e6be0790..191ad0250 100644 --- a/doc/bugs/flooding_me_with_ssh_password_prompts.mdwn +++ b/doc/bugs/flooding_me_with_ssh_password_prompts.mdwn @@ -25,6 +25,14 @@ Still, when a situation like this occurs, it seems to me that it should generate Doesn't git-annex deploy its own ssh keys once it has established a connexion with an SSH remote? +> After more investigation, it turns out this peculiar git-annex daemon was some left-overs from a previous session i had logged out of. It is unclear why git-annex was still running, but there were also pulseaudio and redshift programs lying around so I suspect it wasn't git-annex specific. +> +> However, this problem remains on login. When I start a new session, there's a race condition between git-annex asking passwords and ssh-add asking me to unlock my private key. It's a nice festival of password prompts as I struggle to type in my ssh key faster than git-annex asks me for the remote host's password. +> +> In general, I think git-annex should set `PasswordAuthentication=no` (or allow me to configure it as such), especially if it knows it was able to login without a password at some point. It should especially do that if there's no UI attached informing the user it will be prompting for a password. `NumberOfPasswordPrompts=1` would also be a welcome improvement, but I really don't think I should be seeing those password prompts, especially since I *can* login to the server with my existing SSH key. +> +> Also note that I use Monkeysphere to input my private key into the SSH agent so it could explain why this doesn't usually happen to other people: Monkeysphere doesn't automatically get started from `ssh` if the key is missing, and instead `ssh` will revert to a regular password-based authentication which competes with the Monkeysphere password prompt. + ### What steps will reproduce the problem? It's unclear - i guess you need to setup git-annex to autostart and sync with remote ssh annexes. You may also need to have to use XFCE with Awesome to reproduce the problem. I can provide more details on my session setup on request. --[[anarcat]] |