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.
Needs a test with smartcard and a current Kleopatra.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!