diff options
author | Joey Hess <joey@kitenet.net> | 2011-05-06 14:43:40 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2011-05-06 14:43:40 -0400 |
commit | f1fbe33cfeba70123a702b3cdd1139361b75b875 (patch) | |
tree | 75a1d1dc07f7cc6c5c533c0b70e02fbe6ae28c16 /doc | |
parent | 33041e4afb66984a56e646ff4c8240adc8c5e01d (diff) |
response
Diffstat (limited to 'doc')
-rw-r--r-- | doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn b/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn index 6c12b1d15..6d1552fe4 100644 --- a/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn +++ b/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn @@ -1 +1,8 @@ Simple, when performing various git annex command over ssh, in particular a multi-file get, and using password authentication, git annex will prompt more than once for a user password. This makes batch updates very inconvenient. + +> I'd suggest using ssh-agent, or a passwordless ssh key. Possibly in +> combination with [[git-annex-shell]] if you want to lock down a +> particular ssh key to only being able to use git-annex and git-daemon. +> +> Combining multiple operations into a single ssh is on the todo list, but +> very far down it. --[[Joey]] |