Searching keys for the full fingerprint returns an empty set

Issue #5 resolved
Anonymous created an issue

Consider the following pastebin: http://ae7.st/p/5k4. As per that pastebin, searching for the entire fingerprint returns the empty set, yet searching for the key ID, which is the last 16 digits of the fingerprint turns the correct key.

However, this is only partially. As you can see, I have two keys imported. Both have fingerprints, key IDs and other information. Yet, calling gpg.search_keys() on one key returns the key, while on another returns the empty set.

This might be two separate bugs. If so, I don't mind creating a second bug for returning one public key, but not the other.

Comments (5)

  1. Vinay Sajip repo owner

    Please write a short script which shows the problem with DEBUG logging enabled for gnupg, and post the script, the output and the log here. The log should show what is being passed to gpg and what is coming back, which should help to identify the problem.

  2. Aaron Toponce

    I understand that search_keys() is searching pgp.mit.edu by default, unless a keyserver is specified. Here's the full output for my key: http://ae7.st/p/7go. However, I can search for fingerprints on the MTI page just fine: http://pgp.mit.edu/pks/lookup?search=0xE0413539273A6534A3E1925922EEE0488086060F&op=index. Thus, the bug.

    Re: not finding the other key, which does not exist on a keyserver. In reality, it should work offline, searching the local keyring, rather than going out to a keyserver. That's why I suggested opening a second bug.

  3. Log in to comment