Tickets :: [#6343] fetch keyserver fails because of exact=on

Summary	fetch keyserver fails because of exact=on
Queue	Horde Groupware Webmail Edition
Queue Version	1.0.3
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de
Created	2/28/08 (6616 days ago)
Due
Updated	3/6/08 (6609 days ago)
Assigned
Resolved	3/6/08 (6609 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/06/2008 12:37:13 AM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
This has already been fixed in the latest Horde version, aka Groupware 1.1-RC2.

02/28/2008 01:25:42 PM	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ fetch keyserver fails because of exact=on Queue ⇒ Horde Groupware Webmail Edition	Reply to this comment
Usually I use the hkp server pgpkeys.pca.dfn.de as keyserver. GnuPG handles it well, but Horde does not find no keys on the server. The culprit is: +++ b/var/www/horde/lib/Horde/Crypt/pgp.php Thu Feb 28 13:59:49 2008 +0100 @@ -711,7 +711,7 @@ $fprint = '0x' . $fprint; /* Connect to the public keyserver. */ - $cmd = 'GET /pks/lookup?op=get&exact=on&search=' . $fprint . ' HTTP/1.0'; + $cmd = 'GET /pks/lookup?op=get&search=' . $fprint . ' HTTP/1.0'; $output = $this->_connectKeyserver($cmd, $server, $timeout); if (is_a($output, 'PEAR_Error')) { return $output; The implementor defined "exact=on" variables let the request fail. Without it, it works.