sign-key with passphrase needs extra gpg options

Bug #1643136 reported by az
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned

Bug Description

this is a forward of debian bug #842552, which lives over there: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842552

the issue is that with gpg 2.1, duplicity's method of providing passphrases does no longer work:
--passphrase-fd 0 is not supported UNLESS you also feed it --batch (check, duplicity does that already), AND if you also add --pinentry-mode=loopback, which duplicity does not.

this is discussed in greater detail with gpg's upstream in https://bugs.g10code.com/gnupg/issue1772

workaround for now: add --gpg-options="--pinentry-mode=loopback" to your duplicity invocation,
iff you're using gpg2. gpg(1) doesn't support that option.

long-term fix: ideally duplicity should handle both gpg 1 and 2 automatically.
until then this problem should get at least a line or two in the documentation.

Changed in duplicity:
assignee: nobody → Kenneth Loafman (kenneth-loafman)
importance: Undecided → Medium
milestone: none → 0.7.11
status: New → In Progress
Changed in duplicity:
milestone: 0.7.11 → 0.7.12
Changed in duplicity:
milestone: 0.7.12 → 0.7.13
Changed in duplicity:
milestone: 0.7.13 → 0.7.14
Changed in duplicity:
milestone: 0.7.13.1 → 0.7.14
Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

This was fixed in 0.7.13, so closing this bug report.

Changed in duplicity:
assignee: Kenneth Loafman (kenneth-loafman) → nobody
status: In Progress → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.