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://pool.sks-keyservers.net:11371/pks/lookup?op=vindex&search=seth.arnold http://pool.sks-keyservers.net:11371/pks/lookup?op=vindex&search=seth.arnold&fingerprint=on 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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1257939 Title: Does not show fingerprint in key import dialog Status in “seahorse” package in Ubuntu: New Bug description: Using the seahorse option to find and import remote public keys, the properties dialog does not show the correct fingerprint but the key ID instead. to reproduce: go to remote, find remote keys, enter a valid search term, select a key from the results and select properties in the context menu of the selected key. bug was confirmed using the following versions: 3.10.1 (using ArchLinux) 3.2.2 (Using Ubuntu 12.04.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1257939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
