What steps will reproduce the problem? % > git annex initremote glacier type=glacier encryption=E9053BDA -- SNIP -- initremote glacier [2013-01-10 14:50:12 PST] read: gpg ["--quiet","--trust-model","always","--with-colons","--list-public-keys","E9053BDA"] [2013-01-10 14:50:12 PST] chat: gpg ["--quiet","--trust-model","always","--decrypt"] You need a passphrase to unlock the secret key for user: "Andrew Mark Kraut " 4096-bit ELG key, ID 353E49B9, created 2008-11-11 (main key ID E9053BDA) [2013-01-10 14:50:13 PST] chat: gpg ["--quiet","--trust-model","always","--encrypt","--no-encrypt-to","--no-default-recipient","--recipient","B608B8F6E9053BDA"] (encryption updated with gpg key B608B8F6E9053BDA) [2013-01-10 14:50:13 PST] call: glacier ["--region=us-west-1","vault","create","glacier-06D927EC-5761-447B-86AC-CA66040BAC25"] [2013-01-10 14:50:13 PST] call: git ["--git-dir=/Users/akraut/Desktop/annex/.git","--work-tree=/Users/akraut/Desktop/annex","config","remote.glacier.annex-glacier","true"] [2013-01-10 14:50:13 PST] call: git ["--git-dir=/Users/akraut/Desktop/annex/.git","--work-tree=/Users/akraut/Desktop/annex","config","remote.glacier.annex-uuid","06D927EC-5761-447B-86AC-CA66040BAC25"] (gpg) [2013-01-10 14:50:13 PST] chat: gpg ["--quiet","--trust-model","always","--decrypt"] You need a passphrase to unlock the secret key for user: "Andrew Mark Kraut " 4096-bit ELG key, ID 353E49B9, created 2008-11-11 (main key ID E9053BDA) [2013-01-10 14:50:14 PST] chat: gpg ["--quiet","--trust-model","always","--passphrase-fd","8","--symmetric","--force-mdc"] ok What is the expected output? What do you see instead? > I expect any transfers to this remote (glacier) to use the given gpg key, but instead it uses --symmetric, as you can see above. What version of git-annex are you using? On what operating system? git-annex version: 3.20130107 local repository version: 3 default repository version: 3 supported repository versions: 3 upgrade supported from repository versions: 0 1 2 Please provide any additional information below. > Symmetric encryption is used as described in [[design/encryption]], > with the symmetric key stored encrypted using your gpg key. > > The extra prompting described in the comments in the bug. > > I've reproduced this with gpg 2.0.19. It is a documented incompatability > between gpg 1.x and 2.x; the latter needs --batch included in its > parameters. I've put in a fix. [[done]]