diff options
author | Joey Hess <joey@kitenet.net> | 2014-01-01 15:53:02 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2014-01-01 15:53:02 -0400 |
commit | cd015ab0f9acb299ecf55f3ae9dd2a2c8c227bf6 (patch) | |
tree | c94a84d9b25a3d423aa707f76c64bfb16910c761 /doc | |
parent | 299484c0baf7a34e1e5e4c2046fd4e1f1998a78b (diff) |
retitle for remaining problem
Diffstat (limited to 'doc')
-rw-r--r-- | doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn b/doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn index e97945653..494e4fb58 100644 --- a/doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn +++ b/doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn @@ -1,3 +1,5 @@ +[[!meta title="windows assistant fails to set up rsync.net authorized keys"]] + ### Please describe the problem. Having set up a key pair, the assistant is unable to use it to log in. The console only shows a single attempt to log in, when it's adding the key to the remote machine's authorized_keys file. This is evidently failing, as the key is not actually added to authorized_keys, possibly because the shell script it tries to execute is malformed (crazy quoting, I can't untangle it), or possibly because it failed to ask for a password (I expected it to, but it didn't prompt for one). Also, once I do add the key to authorized_keys, I can ssh in using it but asking the assistant to retry still fails. |