On 03/22/2009 09:02 AM, Kim Minh Kaplan wrote: > Daniel Kahn Gillmor: > >> gpg generates an HTTP request like this: >> >> http://$foo:11371/pks/lookup?op=index&options=mr&search=0xD21739E9&exact=on > [...] >> What is the right way to handle this? > > The simplest solution would be to remove the "exact=on" parameter.
That may work, but:
* it's gpg generating that query, not me by hand, so i can't easily
change it (and i certainly can't change it for everyone who i want to
support).
* the exact same query (with exact=on) *works* against SKS 1.1.0, and
also against pgp.mit.edu, which reports itself as "pks_www/0.9.6"
This makes me think that what we're seeing is a bug in older versions of
SKS that could cause serious incompatibilities. The reason i found it
was a report from a user who was having difficulty searching for keys
from the keyservers by keyid.
--dkg
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
