[Bug 214216] mail/claws-mail-pgp: signature and encryption failure with multiple keys in keyring

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214216

            Bug ID: 214216
           Summary: mail/claws-mail-pgp: signature and encryption failure
                    with multiple keys in keyring
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: pawel at FreeBSD.org
          Reporter: ohartmann at walstatt.org
          Assignee: pawel at FreeBSD.org
             Flags: maintainer-feedback?(pawel at FreeBSD.org)

Using ports/claws-mail with its plugin mail/calws-mail-pgp in cunjucntion with
security/gnupg results in trouble if someone has amongs the recent active
secret keys older, revoked or expired keys!

Some keys expired and some has been revoked, so new keys has been created.
After this procedure, I wasn't able to even sign a message, claws-mail quits
with the error message: 

Error: could not queue message for sending. 
Signature failed: Data signing failed, invalid IPC repsonse

My keys are valid and I can also sign and encrypt manually with gpg2. The gpg2
client seems to pick up the non-expired and non-revoked keys from the
public/secret keyring correctly. But obviosly, this fails with the
claws-mail-pgp plugin.

The problem can only be solved by deleting the revoked/xpired keys from the
secret keyring leaving only the recent valid keys - which results in
undechipherable messages in the postbox encrypted/signed with the outdated
keys. This is a very annoying situation.

It might also be possible that I did something wrong, but as far as I can test
for now, Thunderbird seems not to suffer from this problem anyhow.

-- 
You are receiving this mail because:
You are the assignee for the bug.