git-annex/doc/bugs/annex-rsync-transport_ignored.mdwn

### Please describe the problem.
I have an rsync remote with the following option in config:
annex-rsync-transport = ssh -i /path/to/private/key

and git annex copy --to <remote> still asks for the remote's password. I've checked and I can ssh into the remote using that key with no problems, here's the --debug output:

    copy SHA256E-s152396--56bcf5e3f72daa1a194b16e42330fe82806cc1dbc6f3bb52888ff5e5c57b8d08.log (gpg) (checking <remote>...) [2014-09-05 13:12:41 CEST] read: rsync ["<user>@<remote>:<remote path>/81c/b5e/'GPGHMACSHA1--7d9470e207a5669e2d9120538b68815274dbf16d/GPGHMACSHA1--7d9470e207a5669e2d9120538b68815274dbf16d'"]
    <user>@<remote>'s password: 


Once it has asked for the password twice, it starts using the rsync options correctly to copy and the password is no longer needed, until the next "checking remote…". Maybe the "checking remote…" part ignores the configuration?

### What steps will reproduce the problem?
Use an rsync remote with annex-rsync-transport config set.

### What version of git-annex are you using? On what operating system?
git annex version gives:

    git-annex version: 5.20140814-g9b89b5c
    build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash
    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
    remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external
    local repository version: 5
    supported repository version: 5
    upgrade supported from repository versions: 0 1 2 4

which is the latest available linux-armel version.

> Also removing didn't use the configured transport. Both [[fixed|done]]
> --[[Joey]]
2014-09-05 11:24:50 +00:00			`### Please describe the problem.`
			`I have an rsync remote with the following option in config:`
			`annex-rsync-transport = ssh -i /path/to/private/key`

			`and git annex copy --to <remote> still asks for the remote's password. I've checked and I can ssh into the remote using that key with no problems, here's the --debug output:`

			`copy SHA256E-s152396--56bcf5e3f72daa1a194b16e42330fe82806cc1dbc6f3bb52888ff5e5c57b8d08.log (gpg) (checking <remote>...) [2014-09-05 13:12:41 CEST] read: rsync ["<user>@<remote>:<remote path>/81c/b5e/'GPGHMACSHA1--7d9470e207a5669e2d9120538b68815274dbf16d/GPGHMACSHA1--7d9470e207a5669e2d9120538b68815274dbf16d'"]`
			`<user>@<remote>'s password:`


			`Once it has asked for the password twice, it starts using the rsync options correctly to copy and the password is no longer needed, until the next "checking remote…". Maybe the "checking remote…" part ignores the configuration?`

			`### What steps will reproduce the problem?`
			`Use an rsync remote with annex-rsync-transport config set.`

			`### What version of git-annex are you using? On what operating system?`
			`git annex version gives:`

			`git-annex version: 5.20140814-g9b89b5c`
			`build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash`
			`key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL`
			`remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external`
			`local repository version: 5`
			`supported repository version: 5`
			`upgrade supported from repository versions: 0 1 2 4`

			`which is the latest available linux-armel version.`
The annex-rsync-transport configuration is now also used when checking if a key is present on a rsync remote, and when dropping a key from the remote. 2014-09-11 17:21:35 +00:00
			`> Also removing didn't use the configured transport. Both [[fixed\|done]]`
			`> --[[Joey]]`