[kmail2] [Bug 457058] Keyserver not functioning
https://bugs.kde.org/show_bug.cgi?id=457058 --- Comment #6 from Justin --- (In reply to Ingo Klöcker from comment #5) > You have to enable the option auto-key-retrieve for GnuPG. If you do not > want to edit the GnuPG configuration files manually, then you can find this > setting in the configuration dialog of Kleopatra under GnuPG > System->OpenPGP->Options controlling key import and export. > > The option auto-key-locate controls automatic retrieval of keys needed for > encryption. > > The option "Automatically import keys and certificate" most likely applies > to keys attached to email messages, but I haven't really verified this. > > I'll close the report because this is very likely a setup issue on your > side. "auto-key-retrieve" is disabled by default (in the GnuPG backend) > because automatic lookup of keys obviously leaks information about your > communication partners. Thanks Ingo. I do have (under -configuration for Keyservers) 'auto-key-retrieve' ticked on already. This makes no difference. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kmail2] [Bug 457058] Keyserver not functioning
https://bugs.kde.org/show_bug.cgi?id=457058 Ingo Klöcker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from Ingo Klöcker --- You have to enable the option auto-key-retrieve for GnuPG. If you do not want to edit the GnuPG configuration files manually, then you can find this setting in the configuration dialog of Kleopatra under GnuPG System->OpenPGP->Options controlling key import and export. The option auto-key-locate controls automatic retrieval of keys needed for encryption. The option "Automatically import keys and certificate" most likely applies to keys attached to email messages, but I haven't really verified this. I'll close the report because this is very likely a setup issue on your side. "auto-key-retrieve" is disabled by default (in the GnuPG backend) because automatic lookup of keys obviously leaks information about your communication partners. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kmail2] [Bug 457058] Keyserver not functioning
https://bugs.kde.org/show_bug.cgi?id=457058 Ingo Klöcker changed: What|Removed |Added Assignee|aheine...@gnupg.org |kdepim-bugs@kde.org Version|3.1.21.220403 |unspecified Product|kleopatra |kmail2 CC||kloec...@kde.org Component|general |crypto --- Comment #4 from Ingo Klöcker --- Moving to KMail because the original issue seems to be that the key that a message was signed with is not fetched automatically. This has nothing to do with Kleopatra (except that Kleopatra can be used to configure the GnuPG backend that is used by KMail). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
