|
I have recently started experimenting with email encryption and signing. I have X.509 identity certificate from StartSSL and also a PGP certificate and public/secret key pair. GPG, GPG2, gpgsm, gpg-agent, and Kleopatra are all installed and appear to be working fine. I successfully imported my X.509 certificate and my PGP keys.
I'm encountering a problem when I receive PGP-signed email from others. As expected, KMail indicates that it has no public key to verify a signature: When I click the key number in the yellow header, Kleopatra successfully finds the related in the PGP key server (default keys.gnupg.net): However, Kleopatra fails to import: Importing works properly using the command line:
The Kleopatra window immediately updates showing the new certificate, and KMail show what I'd expect for a key that hasn't been validated: Why is Kleopatra unable to import the certificate? |
Administrator
|
Just for reference, can you check whether using other tools like Kgpg works as well?
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
I can confirm this issue on my setup (openSUSE 13.2 with Kontact 4.14.3).
Importing with KGPG seems to work. |
Administrator
|
Looks like a bug in Kleopatra to me. If anyone sees this problem, running Kleopatra from the command line and checking console output when importing would be helpful.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
No output is provided when ran from cli.
I also couldn't find a --debug argument or suchlike. Could you perhaps tell me how to get more output? |
Administrator
|
You may want to check "kdebugdialog" and see if there is an entry for Kleopatra. If so, uncheck "Disable all debug output", then click on "Unselect All", the search for kleopatra and tick next to its entry. Then start kleopatra from a terminal.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
Thanks for your effort. Unfortunately, after several tries, while not seeing any debug output, one key was imported.
However, subsequential attempts were unsuccessful again... Any possibility of getting the debug output in a different way? |
|
Following up here (apologies for the delay). Yes, Kgpg works. I am also unable to obtain debug output. Perhaps it's time to file a bug report -- too bad we can't seem to get some output that's helpful, though.
|
Administrator
|
Try to file in all the information you can, at least - it will be a good start for having this tracked down.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
Hi all,
I am having the same issue on Fedora 21, importing keys does nothing (it used to work when I was on Ubuntu 14.04). |
Registered Member
|
There already is a bug opened for this, however, it seems no progress has been made on that either.
https://bugs.kde.org/show_bug.cgi?id=336916 |
Registered Member
|
Good morning,
I have the same issue. In Kleopatra, I can "Lookup on server" and find a certificate in the server. I select the certificate and press "IMPORT". After that a pop up appears but with the message "Total number processed:0 " and "Imported: 0". I noticed that nothing was imported to the Kleopatra. But if I use the command line (gpg --keyserver keys.gnupg.net --search-keys XXXX XXXX XXXX XXXX XXXX ...) is possible to import the certificate. How can I import certificates from the server with the Kleopatra? Thank you for your help. Fabio |
Registered Member
|
In the menu settings:
directory services in the field "OpenPGP keyserver" put "hkp://servername/"; In GnuPGSystem -> separator OpenPGP -> "Use keyserver at" put "hkp://servername/";. In GnuPGSystem -> separator Network -> "Use keyserver at URL" put "hkps://servername:11371";. Should work. |
Registered users: Bing [Bot], claydoh, gfielding, Google [Bot], markhm, sethaaaa, Sogou [Bot], Yahoo [Bot]