Deal with incompatability in gpg2, which caused prompts for encryption passphrases rather than using the supplied --passphrase-fd.
This commit is contained in:
parent
264bc5354e
commit
88df952243
4 changed files with 18 additions and 1 deletions
|
@ -15,3 +15,7 @@ So I create a new passphrase (two times) for each file I tried to upload. The pr
|
|||
What's this new passphrase for?
|
||||
|
||||
BTW: git-annex version: 3.20130102 same precompiled binary on Arch Linux.
|
||||
|
||||
> 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]]
|
||||
|
|
|
@ -36,3 +36,11 @@ What version of git-annex are you using? On what operating system?
|
|||
|
||||
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]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue