Description of problem: I'm trying to use pius to sign gpg keys after a key-signing party; but it failed on the first address Version-Release number of selected component (if applicable): pius-2.2.4-1.fc26.noarch How reproducible: 100% Steps to Reproduce: 1. # Redacted to protect ids... 2. $ pius -H $host -e -m eblake -O -s $mykey b90bc7abe7c41e65 3. Actual results: Welcome to PIUS, the PGP Individual UID Signer. pub rsa2048/B90BC7ABE7C41E65 2015-02-10 [SCE] [expires: 2019-02-11] Key fingerprint = F3AE DF83 C53A D5E2 124C 7929 B90B C7AB E7C4 1E65 uid [ full ] Alistair Francis <alistair.francis> Have you verified this user/key, and if so, what level do you want to sign at? 0-3, Show again, Next, Help, or Quit? [0|1|2|3|s|n|h|q] (default: n) 3 Signing all UIDs on key b90bc7abe7c41e65 There is 1 UID on this key to sign UID 1 (alistair.francis): signedTraceback (most recent call last): File "/usr/bin/pius", line 342, in <module> main() File "/usr/bin/pius", line 326, in main if signer.sign_all_uids(key, retval): File "/usr/lib/python2.7/site-packages/libpius/signer.py", line 788, in sign_all_uids self.encrypt_signed_uid(key, uid['file']) File "/usr/lib/python2.7/site-packages/libpius/signer.py", line 444, in encrypt_signed_uid raise EncryptionUnknownError(line) libpius.exceptions.EncryptionUnknownError: [GNUPG:] ENCRYPTION_COMPLIANCE_MODE 23 Expected results: gpg should ask for my signature, encrypt the results, and send the mail to Alistair (and to the other keyids I'm trying to sign from my key-signing party) Additional info:
Same in f27 pius-2.2.4-2.fc27.noarch signing a different key. I guess this is due to : https://dev.gnupg.org/rGf31dc2540acf7cd7f09fd94658e815822222bfcb and pius not expecting it
Issue filed upstream: https://github.com/jaymzh/pius/issues/95 PR proposed upstream: https://github.com/jaymzh/pius/pull/96 What's weird, though, is that we have two machines here with identical versions of pius and gnupg and it works on one and fails on the other. Not sure where else to look.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still happening on F29, and what's worse, -4 has a packaging issue, bug 1685701
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.