© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
I presume this is due to some limitation in the key search protocol that is being used. Compare the following two sks keyserver searches:
http://
http://
Perhaps 'fingerprint=on' isn't an option on all keyservers? Or perhaps they are using a more meager search mechanism that doesn't expose this information cheaply.
Once the key _has_ been imported, the fingerprint is then available.
This might also be a failing at the GPGME interface level; I understand gpg --recv-key, when given a fingerprint, will download a key matching only the keyid, and it does not verify that the fingerprint matches before saving the key into the keyring. I'm having trouble tracking down a reference for this behavior though.