Kmail can't automatically get the key from certificate, I have to use kleopatra to do it. Reproducible: Always Steps to Reproduce: 1. Receive a mail with a PGP signature you don't have the key for 2. Click "Show details", click the key ID: e.g. "Message was signed on 2014-06-30 23:47 with unknown key 0x16EF3F64CB201D9C." 3. Kleopatra pop-up with the key list 4. Select the (only) key 5. Press "Import" Actual Results: """Detailed results of importing OpenPGP Certificate Server: Total number processed: 0 Imported: 0""" Mail still can't be verified Expected Results: """Detailed results of importing OpenPGP Certificate Server: Total number processed: 1 Imported: 1""" Mail is verified I can send you signed mails to test, just email me at <echo "bW92aXVybytrZGVAZ21haWwuY29tCg==" | base64 -d> Workaround: use kleopatra to import the key and then go back to kmail. (Don't know if KMail or Kleopatra bug, though)
Well, I don't know what changed since June, 30th, but now it seems to work. Weird...
Back to the bug: I rebooted the machine and now, it is (once again) broken.
Same here. "Perfectly" configured Kleopatra, all configuration tests run and are green, but either from Kmail or manually searching for the hex key is always a zero imported certificates. Both Seahorse and "gpg --recv-keys 0x..." work fine. $ kleopatra --version Qt: 4.8.6 KDE Development Platform: 4.14.1 Kleopatra: 2.2.0 $ gpg --version gpg (GnuPG) 1.4.16 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: ~/.gnupg Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2 $ gpg2 --version gpg (GnuPG) 2.0.24 libgcrypt 1.5.4 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: ~/.gnupg Supported algorithms: Pubkey: RSA, ELG, DSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2
i can bump this bug. $ kleopatra --version Qt: 4.8.6 KDE: 4.14.3 Kleopatra: 2.2.0 $ gpg --version gpg (GnuPG) 2.1.0 libgcrypt 1.6.2 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: ~/.gnupg Unterstützte Verfahren: Öff. Schlüssel: RSA, ELG, DSA, ECDH, ECDSA, EDDSA Verschlü.: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Komprimierung: nicht komprimiert, ZIP, ZLIB, BZIP2 i've observed something that may help: when looking at the details of a certificate in kleopatra's search on server dialog, then the name and mail aliases show up, but the key id and the fingerprint fields are empty. when searching using cli gpg --search-keys, then the key id is showing and can be imported
I can also confirm this (KMail Version 4.14.4 and Kleopatra Version 2.2.0). When opening the details of the certificate on some certs the key id and fingerprint are missing, these won't be imported. If these are present (and after the user has opened the details), the cert is imported correctly.
*** Bug 344368 has been marked as a duplicate of this bug. ***
As I mentioned in Bug 344368 (marked as duplicate of this bug), I think, the problem is the reimport. When a signed message is received by KMail, the information on the public key is stored on the local machine. I think, this causes Kleopatra not to reimport the full public key from the key server Anybody can confirm this?
Sorry for the long wait, but I'd be very happy to test and try to confirm this, if anyone could point me to the steps I need to take to actually monitor/log what's happening so I can try this some more?
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.