[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#321162: marked as done (Trouble interfacing KGPG with The PGP Global Directory.)

Your message dated Fri, 27 Jul 2007 13:12:27 +0200
with message-id <E1IENkB-0000E2-A8@book.localnet>
and subject line Closing bug 321162
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: KGPG Version: 1.2

Trouble interfacing KGPG with The PGP Global Directory.

Example: When I search via the Global Directory *Web Site* for a key for
gpg@cacert.org I get the correct key.  However, when I do the exact same
search via ldap://keyserver.pgp.com, an incorrect key for a different
email address is offered (lowgpg@cacert.org).

Reason: The PGP Global Directory only returns one key to prevent
harvesting, so if your search criteria is not precise, you may not get
the right key.  Kgpg does not offer the choice of "is" or "contains" for
the search parameter,  The first key that the Global Directory finds
that "contains" the term is returned.  Therefore when I enter
gpg@caert.org KGPG receives the key for lowGPG@CACERT.ORG because that
address "contains" the term gpg@cacert.org even though it does not
"equal" gpg@cacert.org.

See thread http://forums.pgpsupport.com/viewtopic.php?t=3845

Suggestion:  Beat some sense into PGP Inc. so that their server looks
for a match before settling for a near-miss.  Or, add a "is" /
"contains" parameter to the keyserver search.

I am using SimplyMEPIS 3.3.1-1 Debian GNU/Linux 2.6.x


-- 
 


Thanks!

Lance W. Haverkamp
Lance@TheHaverkamps.net
Contact & encryption info:
http://TheHaverkamps.net/
 ><> ><> ><> ><> ><> ><>

--- End Message ---
--- Begin Message --- 
Hi,

a while ago you reported bug
"#321162 Trouble interfacing KGPG with The PGP GlobGlobal Directory".
I can not quite reproduce your problem of getting the wrong key but I still
see that using ldap:// will only return ONE key. This seems to be a general
problem of gpg and not caused by the kgpg frontend.

On the other hand using the default hkp:// protocol with the default keyservers
gives multiple results for searches, e.g. for 'dog'.

Further the mentioned forum thread is no longer reachable.


Given all that I'm closing this bug and recommend you use the hkp:// protocol
and maybe one of the default keyservers. If you think this issue is still a
problem and know of a new testcase then please open a new bug against gpg
so the bug can be fixed at the root.

Yours,
	Goswin von Brederlow

--- End Message ---
Reply to: