Summary: | kgpg key server search does not show last result | ||
---|---|---|---|
Product: | [Applications] kgpg | Reporter: | Klaus Layer <klaus.layer+kde> |
Component: | general | Assignee: | Rolf Eike Beer <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 2.7.x | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kgpg/4999235f1f923993143131384369863c30e03222 | Version Fixed In: | 4.8.5 |
Sentry Crash Report: |
Description
Klaus Layer
2012-07-15 10:30:11 UTC
I can't find the key using GnuPG from the commandline: gpg --keyserver hkp://keys.gnupg.net --search-key B973BA7B gpg: searching for "B973BA7B" from hkp server keys.gnupg.net gpg: key "B973BA7B" not found on keyserver Hmm, same works for me: gpg --keyserver hkp://keys.gnupg.net --search-key B973BA7B gpg: searching for "B973BA7B" from hkp server keys.gnupg.net (1) NetBank AG <pgp@netbank.de> 1024 bit DSA key B973BA7B, created: 2000-09-27 keys.gnupg.net resolves to a key server pool, maybe you got a bad one. To ensure that we test with the same server please use 109.230.243.87. For this server I get gpg --keyserver hkp://109.230.243.87 --search-key B973BA7B gpg: searching for "B973BA7B" from hkp server 109.230.243.87 (1) NetBank AG <pgp@netbank.de> 1024 bit DSA key B973BA7B, created: 2000-09-27 Does this work for your? Nope, still returns error. GnuPG 2.0.18 here. Well it seems to depend on the gpg version: gpg2 --version gpg (GnuPG) 2.0.17 libgcrypt 1.5.0 gpg2 --keyserver hkp://109.230.243.87 --search-key B973BA7B gpg: searching for "B973BA7B" from hkp server 109.230.243.87 gpg: key "B973BA7B" not found on keyserver ----- gpg --version gpg (GnuPG) 1.4.11 gpg --keyserver hkp://109.230.243.87 --search-key B973BA7B gpg: searching for "B973BA7B" from hkp server 109.230.243.87 (1) NetBank AG <pgp@netbank.de> 1024 bit DSA key B973BA7B, created: 2000-09-27 can you please test with gpg. I observe the error when using gpg. If I tell my GnuPG to use gpg1 it finds that key. Are you sure your KGpg uses gpg1? And please ask the GnuPG people why this doesn't work anymore with gpg2. Yes I am sure that I use gpg. I have set /usr/bin/gpg in the kgpg settings. Where does kgpg store this setting? Can I do anything more to track down this issue? I have sent a mail to gpg-users for the different search behavior of gpg/gpg2 regarding B973BA7B. The guys from gpg-users told me that gpg2 wants the 0x before the key id. Regarding kgpg that does not change anything. Independent of if have set /usr/bin/gpg or /usr/bin/gpg2, it does not find 0xB973BA7B. This is not limited to that key 0xB973BA7B. Searching for the string pgp@netbank.de also does not work with kgpg. Other examples are 0xDD9B3E3F, 0x46778C6B or 0x1C6CDA58 Git commit 4999235f1f923993143131384369863c30e03222 by Rolf Eike Beer. Committed on 12/03/2012 at 20:23. Pushed by dakon into branch 'KDE/4.8'. fix keyserver search not showing the last result (cherry picked from commit 1ad41e005c5759bf5f636f095f549bf3a6d92d0f) FIXED-IN:4.8.5 This has been sitting on master for a while and is already part of what will become SC 4.9. Fix it also for 4.8.5. M +9 -0 transactions/kgpgkeyserversearchtransaction.cpp M +1 -0 transactions/kgpgkeyserversearchtransaction.h http://commits.kde.org/kgpg/4999235f1f923993143131384369863c30e03222 Thanks for the fix and for providing this nice piece of software. |