--passphrase-file option is broken with gpg version >= 2.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg-sig (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After gpg v2.1, the --pinentry-
lsb_release -rd:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
apt-cache policy dpkg-sig:
dpkg-sig:
Installed: 0.13.1+nmu4
Candidate: 0.13.1+nmu4
Version table:
*** 0.13.1+nmu4 500
500 http://
100 /var/lib/
What I expected:
dpkg-sig to use the provided passphrase file to sign the package
What happened instead:
$ dpkg-sig -v -k GPG_KEY --passphrase-file passphrase.txt --sign builder PACKAGE.deb
Processing PACKAGE.deb...
Default key: GPG_KEY
Using passphrase from passphrase.txt
Signing /tmp/debsigs-
gpg: Fatal: passphrase-fd is invalid: Bad file descriptor
E: Signing failed. Error code: 512
The attachment "patch for perl script to fix --passphrase-file option" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]