The change should be backported to 2.2 to fix key lookups by gnupg-vs-desktop-126.96.36.199-x86_64.AppImage on the default key server.
Revisions and Commits
|Resolved||ikloecker||T5741 dirmngr does not ask keyservers for fingerprints|
|Duplicate||ikloecker||T6042 Cannot search on keyserver from kleopatra 3.1.22 inside an AppImage of GnuPG Desktop or GnuPG VS Desktop|
|Resolved||werner||T6067 dirmngr 2.2 does not ask keyservers for fingerprints|
thanx for fixing this issue ...
Where do i will find the fixed version in order to build an udated AppImage ?
Will this be fixed in gpg 2.2.36 (maybe a reloaded version like gnupg-w32-2.2.35_20220502) or 2.2.37 ?
Best regards ...
What i don't understand is ...
When this should be an issue in dirmngr, why does the search on mentioned keyservers work with kleopatra 3.1.16 and an updated backend gpg-2.2.36:
Ah .. Ok, i missed the thread:
Kleopatra: Certificate lookup shows only one result even if there are 100s matches
This also explains the small list of results in contrary to the list that you get from the web frontend ...
Due to https://dev.gnupg.org/T5725#153224 ("The fingerprints are needed by Kleopatra as unique identifier for keys."), is this still implemented in that way ?
Yes. There is no other way to uniquely identify keys. Even the long key ID that's returned by key servers can be forged nowadays.