Experimental HKP Interface

[Brian M. Carlson]

--jho1yZJdad60DJr+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Before you start, I know the interface is experimental, and I shouldn't
be complaining, but here I go anyway.

bmc@stonewall:~$ gpg --keyserver pgp.mit.edu --recv-keys c7a966dd
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: Warning: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: unable to execute program "gpgkeys_x-hkp": No such file or directory
gpg: no handler for keyserver scheme "x-hkp"

It works with hkp://foo or hkp://foo:11371.

I'm almost positive this is because the old way of referring to
keyservers was x-hkp, not hkp. Anyway, the quick and dirty way to
solve it is symlink gpgkeys_x-hkp to gpgkeys_hkp. You could also replace
x-hkp with hkp internally, but not supporting x-hkp would break backwards
compatibility and external programs like keylookup.

--=20
Brian M. Carlson <karlsson@hal-pc.org> <http://decoy.wox.org/~bmc> 0x560553=
E7
Always store beer in a dark place.
		-- Lazarus Long

--jho1yZJdad60DJr+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7a-cvs (GNU/Linux)
Comment: Ubi libertas, ibi patria.

iQEVAwUBPP/qV+WR/8lWBVPnAQO1pQgApCt5wVaqidrpns/QZ/7W+sESEohyLu7L
bpld1MAkaH9sWKgUyDMcHksSwSHGcBk/UYtwHOmL7nNO8jO/+C7MZBMwVdTQ8hc4
5CXostdCBS8vzjxrO6zKVyflxWleHbQsr7BpVacUZPWHxNsS/XbyXHAWiwUa0luJ
uOLBgrl1KFjLllLUDdb4DMfeOAUHpQNP6qPE4Eg8Nnxx2WVykjG55G7lpNBKoUNr
C2Xaj3tLuQxYhA/Ehgjva1bSwYvK5druLfcdVO5lkdfKmYhxcg8gDCygFj9zQ++1
+zlsOb40q3sWHoVe170jrA230qEKDt+/xnuUzbwZb7JBRrrShyBaiw==
=Xk5j
-----END PGP SIGNATURE-----

--jho1yZJdad60DJr+--