What steps will reproduce the problem?
- Create a new repository with a directory
- Add files
- Select "Store your data in the cloud" with the "Remote server" option
- Enter host, user, directory
- Select "Use an encrypted rsync repository on the server" (Will there be an option for unencrypted later?)
- GPG Passphrase prompt comes up for every file
What is the expected output? What do you see instead?
I expect to enter a passphase once and then it will sync all files with the remote server.
Instead, it begins syncing the files to the server but prompts for a GPG passphase for every single file.
What version of git-annex are you using? On what operating system?
3.20121017 precompiled binary on Arch Linux
Please provide any additional information below.
Not sure if I'm just missing a setting for GPG, but I would think I should only need to use the web app to configure the remote server.
A gpg agent will cache your passphrase. It is beyond the scope of the git-annex package to provide one (though it does bundle gpg), but it should be easy to install gpg-agent on your distribution.
That's all that's needed for normal git-annex use, but the assistant does seem to have a larger problem in this area, since it can need to unlock a remote's key at any time to sync files from it. Since a separate process is spawned for each transfer, this defeats git-annex's normal in-process caching of encryption keys of remotes. So I think it needs to unlock any encrypted special remotes at startup, or when first accessing them, and pass the cached keys to the transfer processes it spawns. This is now on my todo list.
However, none of the special remotes set up by the assistant will use password protected gpg keys, even when it's using encryption it's using a non-password protected shared key. So only encrypted special remotes set up at the command line cause this problem.