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 Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1257939 Title: Does not show fingerprint in key import dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1257939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
