use-agent doesn't work with gpg2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If use-agent is specified and gpg2 is installed and being used by duplicity, the gpg binary fails to get the password from gpg-agent. This appears to be caused by the --passphrase-fd option, which forces gpg to get the passphrase from duplicity instead of from the agent. This is in contrast to GnuPG 1.x behavior, when use-agent took priority over passphrase-fd. I've submitted a proposed fix in a related branch.
Duplicity 0.6.15
Python 2.7.2
Mac OS X 10.7.1
Log output:
GPG error detail: Traceback (most recent call last):
File "/opt/local/
with_
File "/opt/local/
fn()
File "/opt/local/
full_
File "/opt/local/
globals.
File "/opt/local/
globals.
File "/opt/local/
file.
File "/opt/local/
self.
File "/opt/local/
raise GPGError, msg
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: no default secret key: Bad passphrase
gpg: [stdin]: sign+encrypt failed: Bad passphrase
===== End GnuPG log =====
Removing still remembered temporary file /Users/
Removing still remembered temporary file /Users/
13:09:58.000 Task 'FULL' failed with exit code '31'.
--- Finished state FAILED 'code 31' at 13:09:58.000 - Runtime 00:00:00.000 ---
Related branches
- duplicity-team: Pending requested
-
Diff: 47 lines (+18/-6)1 file modifiedduplicity/gpg.py (+18/-6)
Changed in duplicity: | |
status: | New → Fix Released |