https://bugs.kde.org/show_bug.cgi?id=316353
Bug ID: 316353 Summary: kleopatra (and kmail) create empty signatures if the private key is stored on a gnupg smartcard Classification: Unclassified Product: kleopatra Version: 2.1.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: resch....@gmail.com CC: m...@kde.org kleopatra creates empty detached signature files, although the correct key is selected in the sign-wizard, and the wizard returns successfully. The private signing key is stored on a gnupg smartcard. A look into the gpg-agent log reviles that kleopatra communicates successfully with gpg-agent (the pin entry and everything works) but in the end the wrong key for signing is requested (gpg card hold a signing and an authentication key and the requested key is for some reason the authentication key) If you use the gpg commandline tool the same happens unless you use the --local-user switch or a key with an exclamation mark in the end. Probably for the same reason kmail is not able to create a signature (the signature part of the email empty) Reproducible: Always Steps to Reproduce: 1. Insert the smartcard 2. Select file -> sign 3. Use the wizard, it runs correctly but the detached signature file is empty (0 Bytes) Actual Results: An empty (0 Byte) file is created instead of the expected gnupg detached signature file. Expected Results: I expected a detached signature file to be created: As if I had run $ gpg -s -d -u "key-id!" file If this is a gnupg configuration error on my side it would be nice if the signing process fails. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs